Restaurant review response examples that actually work
Restaurants get reviewed more than almost any other local business — and reviewed harder. Nobody writes 400 words about their dry cleaner, but a lukewarm burger can produce a paragraph with photos. That's actually good news: it means you get more chances than anyone else to show future diners how you handle a bad night.
Below are the four negative scenarios every restaurant eventually faces, with example replies you can adapt, plus three positive-review templates and the two mistakes that are specific to food businesses. If you want the general theory behind these replies, we covered the full framework in how to respond to negative Google reviews — this guide is the restaurant-specific playbook.
Scenario 1: "The food came out cold"
Cold food is the most common restaurant complaint and the easiest to answer badly. Don't explain the pass, the expo station, or the heat lamps — the reviewer doesn't care, and readers care even less. Own it, name a fix, offer a direct line.
Hi Rachel — a cold entrée is exactly what we're supposed to prevent, and Tuesday we didn't. We've talked it through with the kitchen: plates were sitting too long during the handoff between courses, and we've changed how the pass is run on busy nights. If you'd like to talk it over, email me at maria@thecornertable.com. — Maria, owner
Notice there's no "we're sorry you feel that way." The food was cold or it wasn't; treat it as fact and move to the fix.
Scenario 2: Slow service on a busy night
This one tempts every owner into the same trap: "it was Saturday, we were slammed." True, maybe — but to a reader, that's you saying slow service is the standard price of visiting when you're popular. Acknowledge the wait as real, explain briefly without excusing, and show what changed.
Hi Tom — 50 minutes between ordering and mains is too long no matter how full we are. Saturday we were down a server and it showed. We've since adjusted our weekend staffing and we now tell guests upfront when the kitchen is running behind, so nobody's left guessing. I'd genuinely like another chance to show you a normal night — ask for me when you book. — Dev, manager
The line "no matter how full we are" does the heavy lifting. It kills the excuse before readers can suspect it.
Scenario 3: "Our server was rude"
Rude-staff claims are personal, one-sided, and impossible to verify publicly — which is precisely why you shouldn't try. Never defend or blame the individual server by name, and never throw them under the bus either. Take the claim seriously, keep the reply about standards, and move the detail offline.
Hi Priya — thank you for telling us. That's not the tone we want at any table, and I've discussed your comments with the team, not to assign blame but to make sure everyone knows what we expect. If you're willing, I'd like to hear exactly what happened: (312) 555-0177, ask for Ana. — Ana, owner
If the reviewer named the server, don't repeat the name in your reply. The review may eventually come down; your reply is forever.
Scenario 4: "I got sick after eating here" — handle with care
This is the one review that can genuinely hurt you, and the one where instinct — deny it, hard, publicly — is most dangerous. You cannot prove where someone's illness came from, and neither can they. Arguing food-safety facts in a public thread makes readers wonder, and one defensive sentence can end up quoted in a health-department complaint or a local news story.
The rule: take it seriously, never confirm or deny causation, show your process, go offline immediately.
Hi Jordan — I'm sorry to hear you were unwell, and I want to look into this properly. We take food safety extremely seriously: we log temperatures daily and our last health inspection was clean. So we can review everything from your visit — what you ordered, when, and how it was prepared — please contact me directly at (415) 555-0163 today. — Sam, owner
What this reply does not do: it doesn't say "our food didn't make you sick" (unprovable, dismissive) and it doesn't say "we're so sorry our food made you sick" (an admission you can't take back). It shows a serious operation and moves fast. If you receive multiple similar reports in a short window, stop replying and call your local health authority yourself — being first matters.
Three positive review templates
Positive reviews deserve replies too — they're free marketing, and a reply doubles their shelf life. Keep them short, specific, and never identical.
The regular:
Thanks, Mike — after this many Friday nights you're basically part of the furniture, and we mean that as the highest compliment. See you next week.
The special occasion:
Thank you, Elena! Anniversaries are the nights we sweat the most, so it means a lot that yours went perfectly. We've passed your note to Carlos — he says the candles were his idea, which is technically true.
The dish shout-out:
Glad the short rib landed! Chef has been tweaking that braise for months, and reviews like this are why. Come back before the menu changes for spring — it won't be on forever.
The pattern: name something from their review, add one human detail, keep it under four sentences. A specific reply to praise reads as authentic; "Thank you for your kind words!" fifty times in a row reads as a bot.
Two restaurant-specific pitfalls
Never argue health or hygiene claims publicly. This goes beyond the "got sick" scenario — it covers "I saw a bug," "the bathroom was filthy," "staff weren't wearing gloves." Correct nothing in public. Show your standards, take it offline, document everything internally. The public record should show a restaurant that investigates, not one that debates.
Don't offer free meals in replies. "Come back and dinner's on us" feels generous, but posted publicly it's a bounty: it teaches everyone reading that a one-star review is worth a free entrée, and it can violate Google's policies against incentivizing reviews. If you want to make it right — and often you should — do it by phone or email, after they contact you.
One more habit worth building: reply to ratings with no text too. A silent 1-star still drags your average, and there's a right way to answer it — we wrote a separate guide with templates for no-comment reviews.
Keep up with it without living in your dashboard
A busy restaurant can pull in a dozen reviews a week, and every one of the replies above took thought — the wrong tone on a "got sick" review is worse than silence. Replyfox drafts a reply in your restaurant's voice for every new review, flags the sensitive ones, and posts only after your approval. You stay the owner; you just stop being the typist.