How to Respond to Restaurant Reviews: The Complete Reply Guide

Quick answer: Acknowledge the specific thing the guest complained about, skip defensive language, offer something concrete instead of just an apology, and keep it short enough that a stranger scrolling past would finish reading it. Do it within a day or two, on the same platform, using the guest's name if the review shows one.

A one-star review lands on a Tuesday afternoon, usually right in the middle of prep. Your first instinct is to defend the kitchen. Your second is to ignore it and get back to work. Neither one helps you.

Your reply is not written for the guest who complained. It is written for the next person reading that review while they decide where to eat tonight. That is the whole reason this work pays off: a calm, specific, human reply turns a bad review into proof that you run a serious house.

This guide is the full method. It covers who your reply is really for, the framework, the pause that saves you from bad replies, templates for the situations that actually come up in restaurants, and what to do when the review is unfair.

Who your reply is actually for

Three audiences read a review reply, in this order of importance:

Future guests. They are scanning for a pattern and for how the owner handles problems. Your reply is a public sample of your judgment.

The guest who wrote it. Some come back. Most do not. Write as if they might.

Your team. Staff read the replies you write about their shifts. Never name or blame anyone in public.

Diners tend to read the negative reviews first. A restaurant with a 4.2 rating and thoughtful owner replies reads better than a 4.5 with silence, because silence looks like nobody is home.

There is a discovery angle too, though it deserves care. Restaurants that reply to every review see about 16% more calls, direction requests, and website clicks. That is the pattern in the data. The exact mechanism is not something anyone outside Google can confirm, so treat replying as reputation work that appears to correlate with engagement, not as a lever you can pull for guaranteed ranking. We look at the evidence in detail in whether review replies help local SEO.

Pause before you reply

The single most useful habit in this whole guide: write the reply, then do not post it.

Set it aside for an hour, or until after service. Read it again cold. Nearly every reply you would regret gets caught in that gap, because the emotion that produced it has drained out and what is left reads as defensive, sarcastic, or over-apologetic.

If a review made your face hot, that is the signal to wait longer, not to reply faster. A calm reply two days later beats a sharp one in twenty minutes. There is a narrower version of this problem in how to respond to a one-star review, where the temptation to argue is strongest.

The four-part framework

Every strong reply does four things, in order:

Acknowledge the specific detail. Name the dish, the wait, the mix-up. Specificity is the whole difference between a reply that lands and one that reads as automated.

Address it honestly. If it was a kitchen error, say so plainly. One clean sentence. No paragraphs of apology, no explaining the rush.

Act. Offer something concrete rather than just an apology: a look at ticket times, a conversation with the team, a direct contact, a plan for their next visit.

Invite them back, briefly. One line, not a hard sell.

Three or four sentences total. Long replies look defensive.

For positive reviews, the same shape applies with less weight: name what they praised, thank them without gushing, and add one specific detail only an actual human at that restaurant would know.

What to avoid

Arguing the facts, even when you are right. You will win the argument and lose the table.

Copy-and-paste apologies. Several identical replies in a row tell everyone you are not really reading.

Discount offers in public. Do that in the offline follow-up, or you train people to complain for vouchers.

Replying while angry.

Naming or blaming staff in public.

Corporate hedging. "We strive to provide excellent guest experiences" says nothing.

Templates by scenario

Adapt the bracketed parts. Never send one of these unchanged across several reviews.

1. Service complaint (slow, inattentive, or rude staff)

Thanks for taking the time to write this, [Name]. Being left waiting at your table on a [Friday night] is not the experience we want anyone to have, and I am sorry it happened. I have gone through the service that evening with the floor team so we can tighten up during our busiest stretch. If you are open to it, email me at [email] and I would like to look after your next visit personally.

2. Food quality (cold, undercooked, bland, or wrong)

I appreciate you flagging this, [Name]. A [steak] arriving cold is on us, and I am sorry that was your first impression of the kitchen. We have reviewed the pass and ticket timings for that service so plates go out at the right temperature. Please reach out at [email], I would genuinely like the chance to cook for you again.

3. Long wait times

Thank you for the honest feedback, [Name]. A [50 minute] wait between courses is too long, and I understand why that soured the evening. We were short two on the line that night, which explains it but does not excuse it, and we have adjusted staffing for weekend services since. I would like to make it right, you can reach me at [email].

4. A harsh or rude review about a wait

We're sorry about the wait. A 40-minute delay on a reservation isn't the experience we want, and there's no version of that night where it was fine. If you're willing to give us another shot, ask for a manager when you come in and we'll make sure you're seated on time.

5. Wrong order

That's on us. The ticket should have caught that before it left the kitchen, and it didn't. If you come back, mention this review to the host and we'll get it out the way it should have come the first time.

6. A missed dietary request

This one matters to me, [Name]. When a guest tells us about [a nut allergy], that needs to be carried from the table to the pass every single time, and it clearly was not. I have run the allergen process again with the whole team this week. Please email me at [email] so I can follow up with you properly.

7. Cleanliness or a health concern

We're sorry, and we don't take this lightly. Please reach out directly at [phone or email] so we can get details from you and check with the kitchen. Anything you can tell us about the day and time helps us find where this went wrong.

Never argue a cleanliness complaint in public and never imply the guest imagined it. Get it into a direct conversation quickly.

8. Price or value complaint

Thanks for the feedback, [Name]. We price [our tasting menu] around the produce we buy and the size of our kitchen team, but if you left feeling it was not worth it, then we did not deliver on the experience side of that. I would like to hear more about the meal, you can reach me at [email].

9. Delivery or takeout problem

Sorry about this, [Name]. Food arriving [late and cold] through a delivery app is still our name on the bag, so I am not going to pass it off. We have changed how we pack [the pasta dishes] to hold heat better and we are flagging repeat delays with the platform. Email me at [email] and I will sort out your order.

10. A review that seems unfair or false

Thank you for the review, [Name]. I am struggling to match this to a booking or an order on that date, and I want to understand what happened rather than dismiss it. Could you email me at [email] with the day and time? If we got something wrong, I want to fix it.

Stay neutral. Never accuse someone of lying in public. If the review clearly violates Google's policies, reply calmly and then report it, as covered in how to remove fake Google reviews.

11. A complaint about something you cannot change

I appreciate you saying so, [Name]. We know [the room gets loud] on weekend nights, it comes with a small space and a full house. If you would like a quieter table, email me at [email] before you book and we will put you in [the back corner].

A worked example

Review: "Waited 25 minutes for drinks, the risotto was lukewarm and the server never came back to check on us. Really disappointing for the price."

Reply: "Thank you for writing this, Sarah. Twenty five minutes for drinks and a lukewarm risotto is not the standard we hold ourselves to, and I am sorry that was your evening with us. I have gone through the timings from that service with both the bar and the kitchen, and we have added a second server to Friday nights. I would like to put it right, please email me at hello@[restaurant].com."

Notice what it does not do. It does not argue, it does not blame the rush, and it does not offer a free meal in public.

Three voices, one choice

Most replies fall into one of three registers, and only one of them helps you.

Voice

How it reads

What guests conclude

Defensive	Corrects the guest, explains the rush	This owner argues with customers
Doormat	Over-apologizes, offers free everything	Something must be badly wrong here
Confident	Names the issue, owns it, offers one concrete step	This place is run by someone paying attention

Aim for the third one every time, including on five-star reviews.

How often should you reply?

Every review, inside a day or two, positive and negative. Reply rate and recency are what make a profile look alive.

That standard is also where most independent restaurants quietly fall down. Independent restaurants reply to 15% of reviews; chains reply to over 50%. Not because independents care less, but because the person who would write the reply is on the floor. We dug into that gap in why independent restaurants reply to only 15% of reviews.

If you are starting from a backlog, work newest to oldest, cap yourself at a fixed number per sitting, and stop before the replies start sounding identical. A backlog cleared badly is worse than a backlog cleared slowly.

Where Wimi fits

Wimi reads the full text of each review and writes a reply matched to that specific visit, mentioning the dish, the occasion, or the issue raised. It is trained on 400+ restaurants and 1,000+ real review replies, so the tone lands closer to how an owner actually writes than to a template library. Negative reviews get the calm, investigatory tone above, always with an invitation to continue offline, never with a public discount. Replies post automatically, and you can review or override any of them. Restaurants running Wimi save roughly 15+ hours/month.

See what Wimi would draft for your last review, free.