How to Respond to Restaurant Reviews: 25 Examples for Good and Bad Nights

Most restaurant owners write review responses the same way they'd write a birthday card they forgot about: in a hurry, right before it's due, with whatever generic phrase comes to mind first. That's how "we're sorry to hear about your experience" ends up under a review that specifically said the risotto was cold and the server never came back to the table. The reader notices the mismatch immediately.

A good response does one simple thing: it proves a human read the actual review and is responding to the actual problem. That's it. You don't need to be clever, and you definitely don't need to win the argument. Once you can reply to every review in your voice across Google, Yelp, and TripAdvisor instead of drafting each one from scratch, this gets a lot faster to do consistently.

Below are 25 example replies, organized by the situation that triggered the review. Each one is written for a different scenario on purpose — swap in your restaurant's details, but notice the pattern: name the issue, keep it short, and don't argue.

One more thing before the examples: a diner deciding where to eat tonight is reading your most recent reviews right now, not researching your lifetime average. A well-handled bad review from last month can do more to earn that booking than a dozen five-star reviews with no owner replies at all, because it shows there's a real person running the place who takes complaints seriously instead of ignoring them.

Cold or wrong dish

Food complaints are the most common one-star trigger, and the easiest to respond to badly, because it's tempting to explain why the kitchen was running behind instead of just owning it.

• Good: "The branzino should never leave the kitchen lukewarm — that's on us, not a fluke. I've flagged this with the line tonight. Please email us at [address] with the date of your visit so we can make it right."
• Good: "You ordered the mushroom risotto and got the wrong plate entirely — that's a ticket mix-up on our end, not a small thing to get wrong. We'd like to have you back as our guest; reach out at [address] whenever works for you."
• Avoid: "We were extremely busy that night and the kitchen was slammed, so some dishes didn't go out at the right temperature." This explains the restaurant's problem instead of acknowledging the guest's experience, and it reads as an excuse, not an apology.

Whatever you offer to make it right — a replacement dish, a credit toward a future visit — put the offer in a private follow-up, not the public reply. The public reply's job is to show every future reader that you noticed and cared; the actual fix is a conversation, not a performance for an audience.

Long wait times

Wait complaints usually aren't really about the clock — they're about feeling forgotten. The response should address that feeling, not just the minutes.

• Good: "Forty minutes past your reservation time with no update from us is exactly the kind of thing that ruins an evening, and I'm sorry that's what happened. We're adjusting how we communicate delays at the host stand so guests aren't left guessing."
• Good: "Waiting at the bar for twenty minutes after being told 'five more minutes' twice isn't a small inconvenience — we should have been upfront with you from the start. Thank you for the honest feedback; we're working on it."
• Avoid: "Unfortunately wait times can vary on weekends and we appreciate your patience." This treats a specific complaint as a general policy note and doesn't acknowledge that anything went wrong.

If the wait was genuinely caused by something fixable — a host stand that wasn't tracking tables accurately, a kitchen that was understaffed that night — it's worth saying so in general terms. "We're adjusting how we communicate delays" tells a future guest something concrete changed, which does more work than an apology alone.

Rude or inattentive staff

These reviews are personal, which makes them harder to respond to, and easier to get defensive about. Don't defend the staff member by name in public, and don't dismiss the guest's read on the interaction.

• Good: "A server rolling their eyes at a question about the menu is not how we want any guest treated, and I'm genuinely sorry that happened to you. I'd like to discuss this directly — please call the restaurant and ask for the manager on duty."
• Good: "Being ignored for fifteen minutes after sitting down is a service failure, full stop. We're using this as a coaching moment with the floor team this week. Thank you for telling us rather than just not coming back."
• Avoid: "Our staff are trained professionals and we're surprised to hear this." Publicly doubting the guest's account almost always backfires — readers side with the guest, not the business defending itself.

You can take corrective action with the staff member privately without ever mentioning it in the public reply. The two things — what happens internally and what the next diner reads — don't need to be the same text.

Lost or mishandled reservation

A reservation that vanishes is uniquely frustrating because the guest did everything right and planned around a commitment the restaurant didn't keep.

• Good: "Showing up for an 8pm reservation for your anniversary and being told there's no table under your name is exactly the kind of mistake we take seriously. That's a gap in how we're confirming bookings, and we're looking into what happened on our end."
• Good: "A party of six holding a confirmed reservation shouldn't be told to wait forty-five minutes for a table — we dropped the ball on seating that night. We'd like to host you again properly; email us at [address]."
• Avoid: "Our reservation system occasionally has sync issues." Blaming software instead of owning the guest experience makes the apology feel hollow, even if it's technically true.

Reservation mix-ups are also one of the few situations where naming a concrete fix in the public reply — a new confirmation process, a double-check step at the host stand — genuinely helps, because the next guest booking a table wants to know this specific failure mode is less likely to happen to them too.

Billing errors

Billing complaints need a response that's specific about fixing the money, not just the feelings, and clear about how to actually get it resolved.

• Good: "Being charged for two bottles of wine when your table only ordered one is a real error, not a matter of opinion. Please email your receipt to [address] and we'll correct this right away."
• Good: "An automatic gratuity added on top of a tip you already left in cash should never have happened — that's a training gap at the register, and we're sorry. Reach out with your receipt and we'll refund the difference."
• Avoid: "Please note gratuity is automatically added for parties of six or more, as stated on the menu." Even if the policy is correct, leading with the policy instead of looking into the specific complaint reads as dismissive.

Billing complaints are also the easiest ones to actually verify, since there's a receipt behind the claim. Check it before you respond publicly — a reply that promises a refund and then can't deliver because the charge was actually correct is worse than taking a few extra hours to look into it first.

Allergy and food-safety complaints

These are the highest-stakes reviews you'll get, and the rules here are different from every other category above. Handle them carefully:

• Never admit fault publicly. Don't write anything that sounds like confirmation that your kitchen caused an allergic reaction or foodborne illness. That statement becomes evidence, and you don't have the full picture from a review alone.
• Move the conversation private immediately. The public reply should be short and should ask the guest to contact you directly — nothing more.
• Don't offer medical or legal guidance. Don't diagnose, don't speculate about what caused the reaction, and don't promise compensation in writing. If this escalates, consult a lawyer before responding further — not a search engine.

Examples that follow those rules:

• Good: "Thank you for letting us know. A reaction like this is something we take extremely seriously, and we'd like to understand exactly what happened. Please contact us directly at [address] or [phone] as soon as you can."
• Good: "We're sorry to hear you got sick after your visit. We'd like to look into this right away — please reach out to us directly at [address] with the date and time of your visit so we can follow up properly."
• Avoid: "We're so sorry our kitchen made you sick — we've identified the issue and fixed it." This both admits fault before you've actually confirmed the cause and commits you to a specific explanation in writing, which can come back to hurt you if the facts turn out differently.

One more rule for this category specifically: never ask a staff member to argue with a food-safety review, publicly or privately, even if the team is confident the guest is wrong. A defensive back-and-forth under a review about getting sick reads badly to every future diner regardless of who was actually right, and it's not the kind of dispute that gets settled in a comment thread.

If you're regularly unsure what tone to strike on a sensitive complaint before anyone on your team hits "post," running it through the negative review response generator first gives you a draft to edit rather than a blank box to stare at under deadline pressure.

Positive reviews worth a thoughtful reply

"Thanks so much!" is fine, but it's a missed opportunity. A specific reply to a great review does quiet marketing for the next reader scrolling through.

• Good: "So glad the lamb shank hit the mark for your birthday dinner — that's one of our chef's favorites to put out on a Friday night. Hope to see you again soon."
• Good: "Thank you for calling out Maria by name — she's been with us for two years and this is exactly the kind of service we want every table to get. We'll make sure she sees this."
• Good: "Great to hear the patio was the right call for your group on a warm night. We just extended the outdoor hours through the season, so it's worth asking for that section again."
• Good: "A five-course tasting menu review this detailed means a lot — thank you for taking the time to describe each course. We'll pass this along to the kitchen."
• Avoid: "Thank you for your positive review!" copy-pasted under every five-star review in a row. Readers scrolling through can tell when a response is templated, and it undercuts the sincerity of the thoughtful replies sitting right next to it.

It's worth replying to glowing reviews even when there's nothing to fix, because the reply itself is part of what a prospective diner reads before booking. A restaurant that only shows up in the comments to handle complaints looks like a business playing defense, not one that's proud of what it does well.

Reviews from tourists

Visitors from out of town or out of the country leave reviews a little differently — sometimes shorter, sometimes machine-translated, sometimes comparing your restaurant to something back home. A brief, warm reply still works:

• Good: "Thank you for stopping in during your trip — glad the pasta lived up to the recommendation that sent you our way. Safe travels home."
• Good: "Happy you made time for dinner with us while visiting. Come back and see us next time you're in town."

If a review arrives in a language other than English, don't just run it through a translator and paste the result back — see our guide on replying to reviews in another language for how to handle tone and translation without sounding robotic.

A pattern worth repeating

None of the 25 examples above are complicated. They name the specific thing that happened, they don't argue with the guest's version of events, and they give a real next step when one is needed. The hard part isn't knowing what a good response looks like — it's doing it for every review, every week, across every platform, without letting the backlog build up until Friday night's reviews sit unanswered for two weeks.

One last habit matters more than any individual reply: respond to the bad night too. Don't try to keep a one-star review from going public, and don't pick and choose which guests get asked for feedback based on how the visit went. A consistent response record — good nights and bad nights alike — reads as a restaurant that's confident in what it does, not one that's only showing a curated version of itself.

The other common failure mode is simply falling behind. A single owner or manager checking Google, Yelp, TripAdvisor, OpenTable, and Facebook separately, every day, on top of actually running service, is a schedule that doesn't survive a busy weekend. Reviews that sit unanswered for two or three weeks lose most of their value — by the time the reply goes up, the guest has moved on and the next hundred readers have already formed an impression of a restaurant that doesn't respond.

Every Google, Yelp and TripAdvisor review in one inbox → Try Tailwind free