Automation and approvals

Automation lives in Preferences, and it is two toggles that are deliberately separate.

AI Drafts writes a reply for every review that comes in. Nothing is posted. This is the safe one, and it is where everybody should start.

Auto Send lets a draft post itself when it clears your rules. It cannot be turned on unless AI Drafts is already on, and turning it on asks you to confirm, because from that point replies go out in public without anyone reading them first.

Turning Auto Send off stops sending immediately. Drafts keep being written.

A draft is only sent automatically if it clears all four rules. Any one of them failing sends it to your inbox instead.

Minimum star rating. Reviews at or above this rating qualify. Everything below it is held for a human, always.

Reply to. Which sentiments may auto-send: positive, neutral, negative. Most teams start with positive only.

AI confidence. How sure the classifier has to be before a draft is trusted to post itself. Looser lets more through; stricter holds more back for you.

Daily limit. The most replies that may auto-send in a day. Presets, a custom number, or unlimited.

There is no hidden fifth rule and no override. If a review is below your star threshold, nothing else about it matters. It waits.

Automation is set per app, not once for the whole account. Search your apps, tick the ones you trust it on, leave the rest on drafts.

This is how most teams roll it out: one well-behaved app on auto-send for a couple of weeks, everything else held, then widen it once they have read enough of the output.

The daily limit is a blast radius control, not a billing feature.

Suppose a connector has been down for a day and comes back with four hundred reviews. Without a cap, four hundred replies post in one burst, which looks exactly like a bot and is unpleasant to undo one platform at a time.

The account-wide cap covers everything. Any app can also carry its own cap, which is useful when one busy app should not eat the whole day's allowance.

When a cap is reached, sending stops and drafting carries on. Nothing is lost; the replies are in your inbox in the morning.

Some things never auto-send, whatever the rules say:

• reviews below your minimum star rating
• anything flagged as spam or abusive
• drafts that fail validation

Suspected spam still shows in the inbox with a flag on it, rather than disappearing into a folder you never open. You decide whether to report it.

The daily digest email lands each morning with what came in, what went out, and what is still waiting. Weekly digests go out on Mondays.

The account owner and every active team member gets them, with one exception: developers do not, because the review queue is not their job.

If you would rather see it in the product, the inbox filters by reply state (held, sent, failed) and analytics tracks reply rate over time.