The worst moment to decide how you handle bad reviews is the moment you get one. Something about seeing your business described unfairly in public makes everyone a slightly worse writer, and the reply that feels satisfying at the time is almost always the one you would want back a week later.
So decide now, while nothing is on fire. This guide is a structure you can use in five minutes, a short list of things never to write, and the practical reality of what you can and cannot do about a review once it exists.
Start from what is actually possible
Three facts shape everything else, and two of them surprise people.
You cannot remove a review. Not with any tool. A Google review cannot be hidden or deleted through any interface a third party can reach, and the only route is to flag it by hand in your own Business Profile and let Google decide whether it breaks their policies. Most reviews do not, so most stay. Our guide to comment moderation by network sets out what each network does and does not allow.
You can always reply. Replying is supported, and the reply appears under the review as the business owner’s response. It is permanent and public, which is the whole point.
The review will outlive the argument. A comment under a post is read for two days. A review is read for years, by people choosing between you and someone else, at the exact moment they are deciding. That makes it the highest-leverage writing most small businesses ever do.
The four-part reply
Nearly every good reply has the same four parts, in the same order, in under a hundred words.
1. Thank them, plainly. One short sentence. Not “we value your feedback”, which is a phrase that means nothing and signals a template. “Thank you for telling us” is enough.
2. Acknowledge the specific thing. This is the part that proves a person read it. Name what went wrong in their words: the wait, the cold food, the missed appointment, the delivery that arrived on the wrong day. A generic apology for “your experience” tells the next reader that nobody actually read the review.
3. Say what you are doing about it. Concrete and small is better than large and vague. “We have changed how we handle Saturday bookings” is credible. “We are committed to continuous improvement” is not. If you have not done anything yet, say what you are checking and by when.
4. Offer a private route. A name and a way to reach it. “If you email me at the address below I will sort the refund out, Sam.” This is where the resolution happens, and the next reader does not need to see it, only to see that it was offered.
That is it. No defense, no context, no explanation of your policies, no mention of how busy you were. Every one of those reads as an excuse, even when it is true.
| Part | What to write | What to avoid |
|---|---|---|
| Thank them | One plain sentence of thanks for telling you | “We value your feedback”, which signals a template |
| Acknowledge | The specific problem, in their own words | “Sorry about your experience”, which reads as unread |
| Act | One concrete thing you have changed or are checking | Promises of commitment, excellence or improvement |
| Offer a route | A name and a way to reach it | “Please contact customer services”, with no person in it |
The five things never to write
Each of these is a reply that makes the situation worse, and each one is written every day by someone who was right on the facts.
Never dispute the facts in public. Even when the reviewer has the date wrong, the dish wrong and the staff member wrong. Correcting them reads as arguing with a customer, and nobody reading is keeping score for you. Say you cannot find the booking and offer to look, privately.
Never imply they are lying. “We have no record of this visit” is fine; “this did not happen” is not. The difference is one word of certainty and it changes who the reader sides with.
Never cite a policy. Terms, clauses and “as stated on our website” turn a complaint into a dispute. If the policy matters, explain the outcome in human words.
Never offer money in public. A discount or refund in the reply looks like paying for a rating, teaches everyone reading that complaining pays, and invites exactly that. Offer it privately.
Never write anything you would not say out loud to the person. Sarcasm, passive aggression and “as we explained at the time” all survive forever in a screenshot.
Angry comments are the same problem, faster
A furious comment under a post works the same way, with two differences.
It is faster-moving, so other people are commenting while you decide. One calm reply early stops a thread forming. Three hours of silence does not.
And it is more likely to be about something other than you. Comments catch people mid-day, mid-argument, mid-bad-mood. A reply that is short, warm and unbothered defuses most of it, and the ones it does not defuse were never going to be defused.
Reply once, properly. Then stop. A second and third reply in the same thread is where it stops being customer service and becomes an argument with an audience. If it turns abusive, that is a moderation decision rather than a reply, and the same guide covers which actions each network gives you.
Three worked examples
The structure is easier to trust once you have seen it applied. All three reviews below are invented, and all three are the kinds you will actually get.
“Waited 40 minutes for a table we had booked”
A reply that makes it worse: “We are sorry you had to wait. Saturday evenings are our busiest service and bookings are held for 15 minutes as stated in our confirmation email.”
Everything in that is true and all of it reads as a defense. The policy reference turns a complaint into a dispute, and “our busiest service” says the problem was the reader’s choice of evening.
A reply that works: “Thank you for telling us. Forty minutes with a booking is not acceptable and I am sorry. We have changed how we hold Saturday tables so this does not happen again. If you email me I would like to put it right, Sam.”
Short, specific, one concrete change, a named person.
“Ordered three items, one was missing, nobody answered the phone”
A reply that works: “Thank you for flagging this, and I am sorry twice over: for the missing item and for not picking up. The phone is covered until 5 and that call came after, which we have now fixed by diverting it. Email me your order number and I will get the item or a refund to you today, Priya.”
Two problems acknowledged separately, the cause explained in one plain clause rather than excused, a specific remedy with a timeframe.
“Rude staff. Will not be back.”
No detail, no way to investigate, and genuinely stings.
A reply that works: “Thank you for telling us, and I am sorry. I would like to understand what happened so I can deal with it properly. If you can tell me roughly when you came in, you can reach me at the address below, Marco.”
You cannot fix what you cannot identify, and you should not guess in public. What this reply does is show the next reader a business that asks rather than argues.
Make it routine instead of dramatic
The businesses that handle this well are not better writers. They have made it boring.
Have one place where reviews arrive
A review nobody saw is the only kind that genuinely damages you. Gather reviews and comments into a single queue with the rest of your conversations, so a one-star review cannot sit for a fortnight because it landed in a notification nobody opened.
Name an owner and a deadline
One person replies to reviews, within two working days. Written down. Two people sharing it is how a review waits a week.
Write three reply skeletons in advance
One for a service failure, one for a product problem, one for something that was not your fault. Not templates to paste, skeletons to fill in. Having the shape ready is what makes a calm reply possible on a bad day.
Decide what you escalate, and to whom
Anything involving a safety issue, a legal threat, an accusation of discrimination or a named member of staff should go to one person before it is answered. Decide who that is now.
Ask for good reviews, consistently
The real defense against a bad review is a steady stream of honest ones, which is a routine rather than a campaign. Ask at the moment someone is happy, in person or in the message where they said thanks, and make it one click.
Read them monthly as data
Reviews are the clearest feedback you get and the least likely to be read in aggregate. Once a month, read the last month’s reviews together and look for a repeated word. That word is a to-do list.
When the review is fake
It happens, and it is genuinely infuriating. Two actions, in this order.
Flag it with the platform, with whatever evidence you have, and expect nothing. On Google this is a manual step in your own Business Profile, and the outcome is Google’s call.
Reply once, neutrally. Something like: you cannot find a record of this visit, you would like to understand what happened, and here is how to reach you. That reply is written entirely for other readers, and it does the job perfectly: a reasonable business, responding reasonably, to something that does not add up.
Do not accuse anyone in public, even when you are sure. Certainty reads as defensiveness, and the one thing a reader cannot verify is who is telling the truth. What they can verify is which of the two sounded calmer.
What good looks like, over a year
You will not get your rating back to perfect, and you should not want to. A business with nothing but five-star reviews reads as suspicious to anyone who has spent time on the internet. What you want is a visible pattern: things occasionally go wrong, and when they do, someone from the business turns up, acknowledges it specifically and fixes it.
That pattern is built one reply at a time, mostly on days when nothing dramatic is happening. If you are putting the surrounding habits in place, our guide to running a social media inbox covers the daily routine, and social media response time covers how to measure whether anything is actually waiting.



