Negative reviews have a structure that works, and we have set it out elsewhere. Four-star reviews have no established form, which is why most of them get either a generic "thanks for the kind words!" or an apology for something the guest was not complaining about.
Both are worse than they look. The generic reply wastes a guest who was paying attention. The apology takes a mild aside — "a bit loud" — and converts it, in front of every future reader, into an admission that the room is a problem.
What the reader of your reply is actually assessing
Assume two audiences. The guest, who will read it once, and the next fifty people scrolling your profile, who will read it as evidence of what kind of place this is.
For the second audience, a four-star review with a good reply is worth more than a five-star with none. It is the only place on your profile where you can be seen taking a small, non-urgent piece of feedback seriously — which is a much stronger signal of competence than handling a crisis well.
The reply therefore has one job: acknowledge the specific thing without inflating it.
The two openings to avoid
"We're so sorry to hear that..." No. Nothing sorry happened. The guest gave you four stars. Apologising reframes their evening as a disappointment and tells the next reader that a caveat about noise is a failure this venue accepts.
"Thanks for the kind words!" Also no, particularly at volume. Forty identical versions of this on one profile actively damages credibility — a reader spots the repetition instantly, and it undoes the trust that replying was supposed to earn. The same logic that makes reply rate worth more than star rating depends on the replies not being interchangeable.
Four openings that work
Confirm and locate. "Glad it was a good one. You're right that the room carries on a Friday — the tables along the back wall are noticeably quieter if you're booking again."
This is the strongest form. It agrees, adds information the guest could not have had, and gives them a reason to return that is specific enough to act on. It also tells the next reader that you know your own room.
Confirm and date. "Thank you — and noted on the wait between courses. We've added a runner on Friday evenings since your visit, so it should feel different."
Only usable if it is true. But when a caveat matches something you have actually changed, saying so publicly is the highest-value reply available to you.
Name the specific praise back. "Really pleased the shortrib landed — it's Danny's and he'll be glad. Fair point on the menu being a lot; we're trimming the mains section next month."
Guests notice being read properly. So does everyone else.
Straightforwardly disagree, politely. "Thanks for this. We do keep the music up in the evenings — it's deliberate, and it's not for everyone. Weekday lunches are much calmer if that suits you better."
Underused and often the right answer. Not every caveat is a fault. A venue that knows what it is and says so reads as more confident than one apologising for its own character, and it pre-qualifies future guests, which reduces the same complaint arriving again.
The shape underneath all four
One line agreeing with the good part, specifically. One line addressing the caveat with either information, a change, or an honest position. No apology unless something actually went wrong. No invitation to contact you privately — that belongs in replies to real complaints and looks strange here.
Two sentences. Occasionally three. A five-line reply to a four-star review reads as anxious.
Which ones to reply to
Not all of them, if volume makes that unrealistic. In priority order:
- Any that name a member of staff. Naming a server back publicly is the cheapest retention you will ever do.
- Any where the caveat matches something you have changed. These are free proof.
- Any where the caveat is repeated across several reviews. Your reply is read by people who have seen the same point made elsewhere, and answering it once well addresses all of them.
- A rotating sample of the rest, with genuinely different wording.
What this is not
It is not review management as a way of improving the caveat. Replying well to nine reviews about noise does not make the room quieter, and the temptation is to treat the reply as the response. The caveat still needs extracting and counting so the largest one gets fixed.
The reply is for the next reader. The count is for you. They are separate jobs and only one of them is visible.
Doing the visible one consistently, in a voice that does not degrade into "thanks for the kind words" by the fortieth reply, is the part that fails on a busy month. That is what OMMU handles: everyday replies drafted in your voice with the specific detail carried through, and a text to you the moment something lands that you should answer yourself.