A restaurant review response is read by far more people than the guest who wrote the review. That’s the thing most operators forget when they’re typing at eleven at night, still annoyed. The one-star reviewer has already had their experience. Everyone else scrolling the profile is deciding whether to book — and what they’re really evaluating is how the restaurant behaves when something goes wrong.
This guide covers how to structure a restaurant review response, templates for the situations that actually recur, what the law now requires, and where response stops being the right tool.
Key takeaways
- Write for the next reader, not the reviewer. Your restaurant review response is public-facing brand copy seen by everyone considering a booking.
- Respond to everything, within 48 hours. Positive and negative. Response rate and speed both matter.
- Never argue the facts publicly. Acknowledge, take it offline, resolve privately. A defensive restaurant review response does more damage than the review did.
- Review suppression is illegal. The FTC’s Consumer Review Rule, in force since October 2024, bans suppressing negative reviews and incentivising positive ones, with civil penalties per violation.
- Never condition anything on a review. Give the comp unconditionally, complete that interaction, then ask separately.
- Templates are a starting structure, not a script. Identical responses across twenty reviews read as automated and undo the point.
Get Free Consultation
Read more about our Restaurant Marketing Solutions!
What a restaurant review response is actually for
Three audiences, in order of importance.
Prospective guests. The overwhelming majority of people reading your restaurant review response will never have met you. They’re scanning for pattern: is this a place that takes problems seriously, or one that argues with customers?
The reviewer. Sometimes recoverable, often not. Worth trying, but not the primary purpose.
Your own team. Reviews are unfiltered operational feedback. A pattern in the reviews is usually a pattern on the floor, and the response process is how it surfaces.
That ordering explains why the instinct to correct the record is almost always wrong. You may well be right that the wait was twenty minutes and not the forty-five they claimed. Saying so publicly makes you look like the kind of restaurant that keeps receipts on its guests.
The structure that works
Every effective restaurant review response follows roughly the same five moves.
- Thank them, briefly. One line. Not effusive.
- Acknowledge the specific issue. Name it. Generic sympathy reads as automated.
- Take responsibility without over-apologising. One genuine apology beats three.
- Say what happens next — internally, concretely, without over-promising.
- Move it offline. A direct email address or phone number, ideally to a named person.
What to leave out: excuses, explanations of how busy you were, corrections of their version of events, defensive framing, and any suggestion they misunderstood something. Also leave out discount offers made publicly — that invites complaints from people looking for a free meal, and depending on how it’s phrased it can stray into territory the FTC now regulates.
Keep it to three or four sentences. Long responses read as defensive even when they aren’t.
Templates by situation
Adapt these. Sending the same restaurant review response to twenty different people is visible and counterproductive.
Food quality
Thank you for telling us — a dish arriving underseasoned isn’t the standard we hold ourselves to, and I’m sorry that was your experience. I’ve shared this directly with our kitchen team. If you’d be willing to give us another go, I’d like to look after it personally: [name], [email].
Long wait or service pace
Thank you for the feedback, and I’m sorry the pace of service fell short on Saturday. A wait that long between courses isn’t acceptable and we’re reviewing how we staffed that shift. I’d welcome the chance to talk it through — [name], [email].
Rude or inattentive staff
I’m sorry — that’s not how our team should make anyone feel, and I take it seriously. I’m following up with the team directly. I’d appreciate the opportunity to hear more about what happened: [name], [email].
Wrong order or an ignored modification
Thank you for flagging this. Getting an order wrong is frustrating and we should have caught it. I’ve raised it with the floor team so the check process is tighter. Please reach out directly and I’ll make it right — [name], [email].
Noise, temperature, or atmosphere
Thanks for the honest feedback. The room does carry a lot of energy on weekend nights, and I’m sorry it wasn’t the right setting for your evening. For a quieter table we’d suggest booking earlier in the service, and I’m happy to arrange that personally: [name], [email].
Note what that one does: it acknowledges without pretending a design choice was a mistake. Not every complaint is an error to fix.
Price complaint
Thank you for taking the time to share this. We price to reflect the ingredients we source and the way we cook, and I understand that won’t be right for every occasion. I’m sorry the value didn’t land for you, and I’d be glad to hear more: [name], [email].
An allergen, hygiene, or safety issue
Stop and escalate. This is not a templating situation. Respond publicly with a short acknowledgement and an immediate offline contact, then handle it through your actual incident process.
Thank you for raising this — we’re taking it seriously and are looking into it now. Please contact me directly at [email] so I can follow up with you personally.
A review you believe is fake or from a non-guest
Thank you for the feedback. We don’t have a record of this visit, so we’d like to understand more — please get in touch at [email] and we’ll look into it.
Then flag it through the platform’s reporting process. Do not accuse anyone publicly of lying, however confident you are.
Triage: what to prioritise
Not every review needs the same urgency or the same person writing it.
| Review type | Response time | Who responds | Approach |
|---|---|---|---|
| Safety, allergen, or hygiene | Same day | Owner or GM, then incident process | Short public acknowledgement, immediate offline escalation |
| 1–2 stars, specific and credible | Within 24 hours | GM or owner | Full five-step structure, named contact |
| 1–2 stars, vague or non-specific | Within 48 hours | GM | Brief acknowledgement, invitation to share more |
| 3 stars, mixed | Within 48 hours | GM or marketing | Thank, address the negative half specifically |
| 4–5 stars with a note | Within a week | Anyone trained | Short, specific, mention what they mentioned |
| 4–5 stars, no text | Within a week | Anyone trained | One line. Still worth doing |
| Suspected fake | Within 48 hours | GM | Neutral public reply, report through the platform |
The row people skip is the second-to-last. Responding only to negative reviews produces a response history that reads as damage control. Responding across the board reads as a business that pays attention.
What the law now says
This has changed, and a lot of restaurant review response advice hasn’t caught up.
The FTC’s Rule on the Use of Consumer Reviews and Testimonials took effect on 21 October 2024. The FTC’s own business guidance sets out what’s prohibited, and three provisions matter directly for restaurants:
Incentivised reviews. Businesses cannot provide compensation or other incentives conditioned — expressly or by implication — on a review expressing a particular sentiment. “Free dessert if you leave us a five-star review” is a violation. So is a loyalty offer worded to imply it.
Review suppression. The rule restricts using unfounded legal threats or intimidation to prevent or remove negative reviews, and bars misrepresenting that the reviews shown are all of them when negatives have been withheld.
Insider reviews. Reviews from owners, managers, or staff must disclose the connection. Asking your team to review the restaurant without disclosure is covered.
The FTC began enforcement in December 2025, sending warning letters to companies over potential violations, and civil penalties run to tens of thousands of dollars per violation.
The compliant version of review generation is simple: give the free item unconditionally, complete that interaction, and make the review request separately, with no sentiment attached. Ask for a review — not for a good one.
When responding isn’t the answer
A restaurant review response is a communication tool. It cannot fix an operational problem, and the gap shows publicly.
If three reviews in a month mention the same slow service, a perfectly written restaurant review response to each one is a worse use of your time than a conversation about Saturday staffing. Reviews are a diagnostic. Treating them purely as a PR surface means you’re managing the symptom and paying for it again next month.
The pattern to watch for: recurring specifics. One person calling the room loud is a preference. Six people calling it loud is a fact about your restaurant, and you either change it or start setting expectations at booking.
Reviews also feed your local visibility — review count, velocity, and rating all sit inside the prominence signals Google uses for local ranking, which is covered in our guide to local SEO for restaurants.
Building a process that survives a busy month
Assign it. An unowned responsibility becomes nobody’s. Name a person per location.
Set an SLA. 48 hours for everything, same day for anything urgent.
Write a scenario bank, not a script. Five or six adaptable structures beat one template used verbatim.
Escalation path. Everyone should know which reviews go straight to the GM or owner.
Monthly pattern review. Aggregate the themes and take them to the operations conversation. This is the step that converts reviews from a chore into something useful.
Report per location. At a group, an aggregate rating hides the distribution. One struggling site can sit behind a healthy group average for months.
Let us take review response off your plate
Primi Digital runs reputation and local SEO programmes for restaurant and hospitality groups — review response at scale, compliant review generation, Google Business Profile management, and per-location reporting that shows you which site actually has a problem.
If your reviews are being answered when someone remembers, or your review generation was set up before the FTC rule took effect, those are both worth looking at. Get in touch and we’ll audit your current process.
Frequently asked questions
How should a restaurant respond to a negative review?
Briefly and without defensiveness. Thank the guest, acknowledge the specific issue, take responsibility, say what you’re doing internally, and move the conversation offline to a named contact. Three or four sentences. Never argue the facts publicly, however inaccurate you believe the review to be.
How quickly should you respond to restaurant reviews?
Within 48 hours for most, and the same day for anything involving allergens, hygiene, or safety. Speed is visible to everyone reading the profile later, and a months-old unanswered complaint reads worse than the complaint itself.
Should restaurants respond to positive reviews too?
Yes. Responding only to negatives produces a response history that looks like damage control. A single specific line on a positive review is enough, and the overall response rate is what prospective guests notice.
Can a restaurant offer a discount for a review?
No. The FTC’s Consumer Review Rule prohibits compensation or incentives conditioned, expressly or by implication, on a review expressing a particular sentiment. Give the item unconditionally, complete that interaction, then ask for a review separately without specifying what it should say.
What should you do about a fake restaurant review?
Respond neutrally in public, noting you have no record of the visit and inviting the person to get in touch, then report it through the platform’s process. Never accuse a reviewer of lying publicly. Under the FTC rule, using unfounded legal threats to suppress reviews carries its own liability.
Does responding to reviews help local SEO?
Indirectly. Reviews sit within the prominence signals Google uses for local ranking, and response rate contributes to an active, maintained profile. The clearer benefit is conversion: how you respond changes whether someone scrolling your profile decides to book.
Should each location handle its own review responses?
Responses should be specific to the location and ideally signed by someone there, but the process, SLA, and escalation path should be consistent across the group. Reporting should stay per location, since a group average hides the site that actually needs attention.