Owners obsess over the number under their venue name. It is the wrong number to obsess over, for a straightforward arithmetic reason: once you have a few hundred reviews, your average barely moves. Two hundred reviews averaging 4.2 need roughly sixty consecutive five-stars to reach 4.4. That is most of a year.
Meanwhile there is a second number, entirely under your control, that a guest can assess in about four seconds of scrolling: whether anyone at the restaurant ever replies.
What a guest is actually doing on your profile
They are not calculating. They are skimming for reassurance, and they make the call fast. In that skim, a wall of unanswered complaints reads as nobody is minding this place. The same complaints, each with a short, human, specific reply underneath, read as things go wrong here and someone deals with it.
The second profile can have a lower average and still win the booking. A 4.1 with replies under every negative outperforms a silent 4.4 more often than owners expect, because the replies answer the question the star rating cannot: what happens if I am the unlucky one tonight?
Why the average is stickier than it looks
Two effects work against you.
Dilution. The more reviews you have, the less any single one moves the mean. This is good news when you slip and frustrating when you improve. Either way it means the average describes your past, sometimes years of it, not your current kitchen.
Recency bias in the reader. Guests read the newest reviews first and weight them far more heavily than the aggregate. Which means the three most recent reviews on your page matter more to tonight's booking than the six hundred underneath — and those three are exactly the ones you can influence, by replying quickly and by fixing what they describe.
Reply rate is a number you can finish
You cannot decide to have a 4.6. You can decide that no review goes unanswered for more than twenty-four hours, and that is a task with an end state. It is also visible: platforms surface response activity, and readers register it immediately.
A workable standard for a busy venue:
- Every negative review, within 24 hours. These are the ones being read.
- Every review that names a person or a dish, positive or not. Naming a server back is the cheapest staff retention you will ever do.
- A sample of the plain five-stars. Not all of them, and not with the same sentence each time.
Skip the identical "Thanks for the kind words!" on forty reviews in a row. A reader scrolling your profile sees the repetition instantly and it undoes the credibility that replying was supposed to buy.
The compounding part
Replying changes what gets written next. Guests who see that the owner responds write more specific reviews — because they expect to be read. Specific reviews are more useful to you operationally, and more persuasive to the next reader than "great food, will come again."
And some of them get amended. A guest who leaves two stars, receives a calm reply naming the problem and offering a direct line, upgrades their review more often than most owners believe. Not usually. But often enough that it is worth the ninety seconds, and it is the only mechanism that improves your average retroactively.
Where this falls apart
It falls apart on the third Friday. The intention is genuine, the first fortnight goes well, and then a bad week happens and the queue builds up to eleven unanswered reviews, at which point it feels too late to reply to any of them.
Consistency is the entire product here, and consistency is exactly what a human running a floor cannot reliably supply. OMMU replies to your everyday reviews in your voice, texts you the moment something serious lands so you can handle that one yourself, and keeps the response rate at a hundred per cent without you opening a dashboard.
Set the standard first. Then decide whether you want to be the one meeting it at midnight.