How to reply to a bad review without making it worse
This update was drafted on a schedule by the AI I build with, from real project notes — part of the vibecoding experiment this blog documents.
A while back I wrote that the three-star review is the most useful thing on the internet — that's the reader's side of it. This is the other side: you're the business, a bad review just landed, and there's a little "reply" button under it. What do you type. Most people get this wrong in the same specific way, and it's worth naming.
The mistake is writing the reply to the person who left the review. You're not. They've said their piece, they've picked their stars, and a paragraph from you is not going to move them from two to four. Arguing with them is playing a game that's already over.
Who you're actually writing to
The next person. Someone is going to land on your reviews next week, deciding whether to trust you with their money, and they are going to read that bad review and your reply as a pair. That's the unit. The review tells them something went wrong once; the reply tells them what kind of operation you run when something goes wrong. The second signal is often stronger than the first, and it's entirely in your control.
So the question isn't "how do I win this." It's "what does this exchange look like to a stranger reading it cold."
What that changes
Acknowledge the specific thing. Not "we're sorry to hear about your experience" — that phrase tells the next reader you didn't actually read the review. Name the real complaint. "You waited 40 minutes for a table you'd booked, and nobody told you why." The stranger sees that you're not hiding from it.
Don't get defensive, even when you're right. You might have the receipts. The kitchen was slammed, the customer was an hour late, it wasn't your fault. Doesn't matter. A public back-and-forth where the business is technically correct still reads as this place will argue with me if I complain. Nobody wants to buy from that. Concede the experience even when you wouldn't concede the facts.
Say what you'll do, concretely, then take it offline. "We've changed how the host desk handles booking delays" is useful to the next reader. "Please email us so we can make this right" on its own reads as damage control. Do both: one real change stated in public, one line moving the resolution to private.
Keep it short and match the tone. A calm three-sentence reply under an angry paragraph makes the angry paragraph look like the outlier. A long defensive wall of text makes you look like the problem. Don't escalate the volume.
Don't over-apologize for things that aren't yours. Grovelling at a complaint about parking, or the weather, or a competitor's product, just makes you look like you'll fold under any pressure. A light "that one's outside our control, but here's what is" is fine.
The one time you do correct the record
If the review contains a factual claim that would genuinely mislead the next reader — they're reviewing the wrong business, they never actually bought anything, they're describing a policy you don't have — you correct it. Once. Calmly. "We think this might be meant for another location — we've never operated on that street." State the fact, don't add a lecture, don't do it twice. The next reader can weigh it.
Everything else, let the specific-friction stuff stand. A review page where the business never pushes back on anything reads as fake too.
Where this connects to what I build
Cadence builds a business its website out of its Google reviews, and the replies are part of what the pipeline is reading. A business that answers its two- and three-star reviews like a person — specific, unbothered, useful — is giving off a trust signal that a wall of unanswered five-stars doesn't. The reply is brand voice, whether you meant it to be or not.
And with tab. it's App Store reviews, which have their own version of this: someone writes "crashed when I added a friend," and a reply naming the specific build it broke in, saying it's fixed in the current one, and owning that it shouldn't have shipped, is worth more to the next person browsing the App Store than to the one who wrote it. They may never see it. The 500 people reading reviews before they download will.
I don't have numbers on any of this — no measured lift from replying well versus badly, I just watch how these read. But the frame has held up: the bad review already happened, and the only part still in your hands is what the next person sees when they read what you said back.
This one's auto-drafted from my notes on a schedule. If a number isn't in the notes, it doesn't show up here — I'd rather leave a blank than make something up.