Most bad reviews are not really about the food. They are about a moment where a guest felt ignored, rushed, or quietly overcharged — and then had nowhere to put that feeling except a review box at eleven at night. Your reply is not an argument you can win. It is a signal to the next hundred people reading it.
Those people are not reading to find out who was right. They are scanning to answer one question: if something goes wrong for me here, will these people handle it like adults?
The four lines that do the work
Almost every effective public reply is the same four moves, in the same order. It takes about ninety seconds once you stop rewriting it in your head.
- Name the thing. "You waited forty minutes for a main on a Friday." Not "we're sorry you feel that way." Repeat the specific complaint back so the reader knows you actually read it.
- Own your half. Whatever genuinely was your fault, say so plainly and without a "but". One sentence.
- Say what changed. "We've added a second runner on Friday service." A concrete, boring operational detail is worth more than any apology, because it is the only part of your reply that cannot be faked.
- Move it offline. Offer a direct line — a name and an email — and stop there. Never negotiate compensation in public.
That is it. No fifth paragraph. Length reads as defensiveness, and every extra sentence is another chance to say something you will regret.
The three moves that reliably backfire
Correcting the facts. You may well be right that they arrived at 21:50 for a 22:00 kitchen close. It does not matter. A reply that opens by disputing the timeline reads to everyone else as an owner who argues with customers, and it is the single fastest way to turn one bad review into a thread.
The copy-paste apology. If your last twelve replies all begin "We're sorry to hear about your experience," a reader scrolling your profile sees a business that is processing complaints rather than reading them. Reviewers notice this faster than owners expect — the identical opening line is the tell.
Silence on the ones that sting. Owners tend to reply to easy reviews and skip the brutal ones. From the outside this pattern is very legible: it looks like you answer when it is flattering and hide when it is not. If you only answer one review this week, answer the worst one.
What about the review that is simply untrue?
Some are. A competitor, a mistaken venue, a guest describing a dish you do not serve. Reply once, briefly and without heat: state that you have no record of the visit, invite them to contact you directly so you can look into it, and leave it. Then report it through the platform's process and move on.
A short, calm reply under a false review does more for you than getting it removed, because it stays visible as evidence of how you handle conflict.
The part most owners get wrong
Speed beats polish. A decent reply within twenty-four hours is worth more than a perfect one next week, because the review is most visible while it is fresh — and because a guest who is still angry on day four is a guest who has told more people.
This is the whole reason OMMU exists. Not because replying is hard, but because doing it consistently, within a day, at eleven at night, after a double shift, is a thing almost nobody manages for long. The structure above is simple. Doing it four hundred times a year is not.
A worked example
⭐ "Waited 40 mins for pasta that came out cold. Server never checked on us. Won't be back."
A reply that works:
"Forty minutes for a main, and cold when it arrived — that's on us, and I'm sorry. We were a runner short on Friday and it showed; we've since added cover for Friday and Saturday service. If you'd give us another go I'd like to sort it out personally — andrew@ommu.ai."
Four lines. Names the problem, owns it, states the fix, moves it offline. The next reader learns everything they need to know about how this restaurant behaves when it slips.