StarReply watches the public reviews on every location you own, reads each new one overnight, and drafts a reply in your voice. In the morning you get one queue instead of five review dashboards — approve, edit, or kill each one.

Only if you switch it on, and never on a bad review. Copilot is the default and holds every reply for your tap. Autopilot lets the agent post 3 to 5 star replies on its own, up to 20 a day per location — and a 2-star or lower review still waits for you, in every mode, because that branch runs before the mode is read.

You get 30 seconds. An approved reply is staged, not sent: the publisher will not pick it up before the window has elapsed, and undo inside it flips the row to cancelled. So a killed reply was never published — not published and then deleted.

It is for any business with more than one address and public reviews on it — dental groups, veterinary practices, gyms, salons, dealerships, self-storage, urgent care. The thing they share is that reviews arrive at several places and one person answers them.

One OAuth connect. Google Business Profile hands over every location on the account, StarReply pulls their recent reviews, and the first overnight pass runs that night. There is nothing to import and no listing to move.

$39 a month for up to three locations and $99 a month for up to twenty-five — priced per business, not per location. The free tier watches one location and shows you what the agent would have drafted.

A voice profile: your business name, your sign-off, a baseline tone and three dials — formality, warmth, directness. Two switches are off by default and are the ones that matter on a public reply: whether the agent may apologise on the record, and whether it may offer a refund, discount or replacement.

A check that runs after the draft is written, not a line in the prompt. If the reply names a remedy or an apology your voice profile does not license, it is held with the offending words quoted back at you. It is never quietly rewritten — a model deciding on its own to drop the sentence it thought was right is a worse outcome than you reading it.

It still drafts the reply — so the hard one is already written when you open the queue — and then it holds it. A 2-star or lower review is approval-only in every autonomy mode. That is the first branch in the routing code, it runs before the mode is read, and the database rejects any update that clears the flag on the row.

Then it does not answer it. Every review gets a classification and a confidence, and below 70% the reply is held whatever the rating. The classification is on the card, so you can see what it thought before you approve anything.

A bare rating with no words is common and it is still a review. The agent drafts something short and specific to the rating rather than pretending to answer content that is not there — and on a one- or two-star bare rating, it holds it for you like any other.

Two per review — one to read it, one to draft the reply — under a ceiling of 200 a day. Past the ceiling reviews are still pulled in and still land in your queue; they arrive undrafted, which cannot post.

Google Business Profile first, because that is where a local business's reviews already are, and Trustpilot as the second source. Both ride the same interface, so both land in one queue rather than two consoles.

Your business's. On Google the reply is posted publicly under the customer's review and appears as your business, with no personal name shown. On Trustpilot it is published as a named business user, which is Trustpilot's own requirement.

Yes — both rails let a published reply be deleted, and StarReply keeps the handle it needs to do it. But the kill window exists so you rarely have to: inside it, nothing was ever published.

The scope needed to read reviews and post a reply, and nothing else. Tokens are stored server-side and are never readable from the browser — the table they live in has no read policy at all. Disconnecting revokes the grant provider-side before dropping the token.

It cannot. One reply per review, enforced as a unique constraint — which is also the rails' own rule: Google stores a single reply per review and a second post overwrites what the public already read.

That location's watermark does not move, the failure is written to the ledger, and the pass carries on to the next location. Nothing is skipped — the next night re-reads from where it got to.