Updated 2026-06-28
Responding to unfair reviews: templates
An unfair review is different from a fake one: the customer is real, the frustration is real, but the blame is misplaced - a posted policy they didn't read, a third party's failure, or a story missing its second half. You usually can't get these removed, so the public reply carries the weight. Your audience is the future reader, not the reviewer. Correct the record once, calmly, with verifiable specifics, and stop. A reply that wins the argument but sounds defensive loses the reader.
The templates
Replace every [BRACKETED_PLACEHOLDER] with your specifics before posting - an unedited template is worse than no response.
Blamed for a clearly posted policy
Hi [CUSTOMER_NAME], I'm sorry the visit ended in frustration. For context for anyone reading: [POLICY, e.g. “we require 24-hour cancellation notice”] is posted [WHERE - booking page, front desk, confirmation email], and it exists because [ONE_SENTENCE_REASON]. I understand it stung in the moment, and I'm glad to walk through what happened on our side: [EMAIL] or [PHONE]. We apply the policy the same way for everyone - that part isn't personal. - [YOUR_NAME], [ROLE], [BUSINESS_NAME]
Blamed for a third party's failure
Hi [CUSTOMER_NAME], you're right to be frustrated - and I want to be straight about what happened. The [DELAY/ERROR/DAMAGE] came from [THIRD_PARTY_TYPE, e.g. “the shipping carrier” / “your insurance provider's processing”], which we don't control. What we do control is how we help afterward, and we should have communicated sooner. That part is on us. We've since [WHAT_YOU_DID, e.g. “filed the claim” / “escalated with the carrier”]. Call [PHONE] and ask for [YOUR_NAME] - I'll personally see this through.
The one-sided story
Hi [CUSTOMER_NAME], thanks for the feedback - though I think readers deserve the fuller picture. It's accurate that [THE_PART_THAT'S_TRUE]. What the review leaves out is [ONE_KEY_MISSING_FACT, stated neutrally - e.g. “that we offered a replacement the same day, which was declined”]. I'm not interested in a back-and-forth here; if you'd like to talk it through, I'm at [EMAIL]. We stand by how the team handled it. - [YOUR_NAME], [ROLE], [BUSINESS_NAME]
Punished for circumstances beyond anyone's control
Hi [CUSTOMER_NAME], I understand the disappointment - [EVENT, e.g. “the storm closure” / “the county-wide outage”] wrecked plans for a lot of people that day, ours included. We made the call to [DECISION] because [SAFETY_OR_PRACTICAL_REASON], and I'd make it again. That said, we could have notified you faster, and we've changed [PROCESS_FIX] so the next disruption comes with more warning. If you'd like to rebook, contact [EMAIL/PHONE] and we'll take care of you.
Do
- Correct the record once, with one or two verifiable facts - then stop.
- Own the sliver that is yours (slow communication, unclear signage); it buys credibility for the rest.
- Write for the future reader deciding whether to trust you, not for the reviewer.
- Keep receipts: timestamps, signed policies, correspondence - you may need them if you escalate to the platform.
Don't
- Don't post the customer's private details (order contents, account history) to win the argument - it can violate platform rules and privacy law.
- Don't reply while angry; unfair reviews are the ones most likely to bait a career-worst response.
- Don't beg for removal in the public thread - ask privately, once.
- Don't say “per our policy” four times. Once, with the reason behind it, is stronger.
Stop copy-pasting
ReviewReaction drafts replies to every review in your voice - matched to the situation, no brackets to fill. $19/mo, 7-day trial.
Try ReviewReaction