Every restaurant gets a review that is unfair. The instinct to correct the record in public is completely understandable and almost always the wrong move.
The reply is not a conversation with the reviewer. It is a demonstration, watched by the far larger group of people reading reviews while deciding whether to book.
The reviewer has made up their mind. The audience that matters is the person scrolling reviews at 6pm on a Friday, and what they are assessing is not whether you were right. It is what you are like to deal with when something goes wrong.
A calm, specific, non-defensive reply to a harsh review reassures that reader more than a wall of five-star ratings does.
Short, human, and free of the phrases that signal a template. Most damage comes from length and defensiveness rather than from the words themselves.
Reviews that are abusive, obviously fabricated, or about a visit that clearly did not happen are better reported than answered. Engaging lends them weight and pushes them up the page.
The same applies to a reviewer who replies to your reply looking for a second round. Silence there reads as composure.
It is tempting to explain that a specific member of staff was new, or that the kitchen was short that night. It humanises the situation and it also names someone publicly, which is a staff problem you do not want.
Explain the situation without identifying the person, always.
A recurring complaint is a content brief. If people repeatedly misjudge portion size, wait times or parking, that is a post, not just an operational fix.
Answering it publicly ahead of time removes the complaint at the source, and it reaches the people who would otherwise have booked with the wrong expectation.
Write the reply for the person deciding whether to book, keep it to one exchange, and never name staff in public.
Noian writes, schedules and publishes this kind of content for restaurants, with every post held for your approval first.
See how it works for restaurants