A one-star review lands on your Google Business Profile on a Friday night. Every instinct says defend yourself, explain the context, correct the record. Almost none of that instinct should make it into the reply.
Here's the thing nobody tells you about replying to a bad review: you're not writing for the person who left it. You're writing for the next hundred people who read your profile before deciding whether to book a table or an appointment. That reframe changes everything about what a good reply looks like.
What a public reply is actually for
The customer who left the review has usually moved on by the time you type a response. A public reply exists for the silent majority — the browsers deciding between you and the next search result. They're not looking for a perfect resolution. They're looking for evidence that if something goes wrong, someone here will actually deal with it.
That's a low bar, and most businesses still miss it. A defensive reply, a dismissive reply, or no reply at all all send the same message: complaints go nowhere here.
The three-line structure that works
Acknowledge specifically. Not "we're sorry you had a bad experience" — that reads as a template because it usually is one. Name the actual issue: the wait, the order mix-up, the room temperature. Specificity is the signal that a human read the review.
Take the resolution offline. "Please reach out to us at [contact] so we can make this right" does two things: it shows willingness to fix it, and it keeps the messy back-and-forth out of a thread strangers are reading.
Stop. No excuses, no "however," no explaining why the kitchen was short-staffed that night. Every sentence after the fix-offer reads as litigating the point, and litigating in public rarely looks good on either side.
Three examples
"You're right that a forty-minute wait for a half-empty dining room isn't acceptable — that's on us, not a busy night. Please email us at [contact] with the date and we'll make it right."
"Sorry the order arrived mixed up — that shouldn't happen and we've flagged it with the team. If you're open to it, we'd like to make this right; reach us at [contact]."
"We hear you on the wait time for the report. That's a genuine gap on our end and we're looking at it. If you'd like to discuss, please call the clinic directly."
None of these argue. None of them explain the exception. All three name the specific problem and offer a next step.
What never belongs in a public reply
Never argue the facts in public, even when you're certain the review is unfair — it reads as combative to every future reader regardless of who's right. Never offer a discount or refund explicitly "in exchange for" removing or editing the review; besides reading as transactional, Google's policy on review manipulation treats incentivized editing as exactly that. And never go silent — an unanswered one-star review sitting at the top of a profile for months says more than any single bad review ever could.
The reply is damage control; the real fix is upstream
A good public reply limits how much one bad experience costs you with future customers. It doesn't undo the experience itself, and if the same complaint keeps showing up — slow service, mixed-up orders, long waits — no reply template fixes a pattern.
That's the case for catching dissatisfaction before it reaches Google in the first place. Starboard's counter-side flow lets a customer choose to send feedback privately the moment they're unhappy, which means the same complaint reaches you same-day instead of three weeks later as a public review you now have to manage. Fewer reviews need a damage-control reply when more of the damage gets caught early.