Playbook
Guest replies that still sound like you
The fastest way to make a restaurant sound like a chain is to automate its review replies badly. What to hand over, what never to, and the test that catches a reply before it goes out sounding like nobody.
Review replies are the first thing people automate and the first thing they regret automating.
The reason is simple. The reply is not for the person who complained. They are gone, and they are not coming back because of a paragraph. It is for the next person, reading twelve reviews before they book, deciding what kind of place this is.
Which means the reply is your voice in public, and there is nothing cheaper to get wrong.
What bad automation actually sounds like
You know it when you read it. We are so sorry to hear about your experience. We strive to provide excellent service and will share this with our team.
Nobody wrote that. Everybody can tell.
Three tells, and they are the same three every time:
It apologises without naming the thing. It uses a word no one in your building has ever said out loud — "strive", "valued patron", "reach out". And it promises a process instead of an action: we will share this with our team means nothing happened.
A reply with those three in it is worse than no reply, because it tells the next reader that the complaint was received by a machine.
What is genuinely safe to hand over
The first draft. Not the send.
Give it the review, your actual voice, and the facts a manager already knows — that the Tuesday closer was new, that the patio heater was out, that the wait was ninety minutes because a party of thirty walked in. Then a person reads it, fixes the one line that is wrong, and sends it.
That gets you from twelve minutes a reply to two, which across a group is the difference between replies happening and not happening.
The sorting. Which reviews need a manager today and which need a sentence.
A three-star that says the food was great but they waited is not the same job as a one-star naming a member of staff. Triage is a genuinely good use of a machine and it involves no writing at all.
The pattern. Twenty reviews across four stores, read at once, will tell you the same thing three of your GMs already suspect but have not compared notes on.
What never goes out unread
Anything about a named person. Anything about illness. Anything mentioning a refund, a lawyer, or a health inspection.
That is not a tone problem. Those replies have consequences beyond the review, and every one of them should be read by somebody who can be held to it.
The test
Read the draft out loud in the voice of whoever is going to sign it.
If it sounds like a person who works there, send it. If it sounds like a brand, delete a sentence and try again. Usually the offending sentence is the second one, and usually it is the one that says "strive."
The other test: could this reply have been written without reading the review? If yes, it is not a reply. It is a receipt.
How to give it your voice
Do not describe your voice. Show it.
Take your last ten replies — the good ones, the ones a manager wrote on a decent day — and use those as the example. A description of a voice ("warm but professional") produces the exact paragraph at the top of this page. Ten real examples produce something that sounds like your restaurant, because it is built out of your restaurant.
If you cannot find ten good ones, that is the more useful finding, and it is not a software problem.
Start with one store, one week
One GM, one week of replies, drafted then edited. Keep both versions.
At the end of the week read the drafts and the sent versions side by side. The edits are the specification — they are the difference between what a machine assumed about your restaurant and what is true.
Write those down. That is the thing worth keeping, and it is the thing that makes the second week take five minutes instead of twenty.
Wondering whether guest comms is even where your hours go? Take the free check — eight questions, no email. Sometimes it is the reviews. More often it is not.