---
title: 'How to Respond to Google Reviews (50 Templates)'
description: 'How to respond to Google reviews at a restaurant: 50 reply templates by scenario, plus what to do when a review feels unfair or breaks policy.'
url: 'https://www.semperi.com/blog/restaurant-google-review-reply-templates'
---

# How to Respond to Google Reviews (50 Templates)

> How to respond to Google reviews at a restaurant: 50 reply templates by scenario, plus what to do when a review feels unfair or breaks policy.

*May 7, 2026 · 15 min · Marketing · Semperi Team, Restaurant growth research*

Reply templates are scaffolding, not a script. The best replies are specific to the review — they name the dish, the server, or the moment. Templates give you a starting shape when the blank reply box is the last thing you want to see after service. Customize the details; never paste them verbatim.

Below are 50 templates organized by scenario, followed by a decision framework for the harder case: a review that feels unfair or factually wrong. The core reply shape is simple: acknowledge → specific → next step.

## The framework

- Acknowledge: name what they said. "Glad the patio worked for your anniversary" beats "Thanks for the kind words."
- Specific: cite a dish, a person, an ingredient, or a moment. A specific, neutral detail is more useful than generic warmth.
- Next step: invite them back, name a future opportunity, or commit to a fix. "We'd love to have you back for the lobster night" beats "Hope to see you again!"

Sign with a real first name and role when appropriate. "Carlos, GM" makes the accountability clear without turning the reply into a corporate statement.

## Before you reply: unfair, disputed, or removable?

A viral X conversation about travelers reading negative reviews resurfaced a useful hospitality truth: future guests read the complaint and the owner's response together. That does not mean every negative review is false. It means your reply has two audiences — the reviewer and everyone deciding whether to visit later.

- Painful but plausible: the guest describes a real visit and a subjective experience. Reply briefly, own what is fair, and add useful context without arguing.
- Factually disputed: the visit appears real, but your records disagree on timing, price, order, or what staff said. Check the reservation, POS, ticket, and manager notes before replying. Correct only the material fact, calmly.
- Potential policy violation: the review appears fake, off-topic, conflicted, harassing, or exposes personal information. Save the evidence and report it through Google. Disagreement by itself is not a removal reason.

## The 15-minute unfair-review playbook

- Pause: do not answer while angry. Draft somewhere private first.
- Check: match the name, date, reservation, order, refund, and shift notes. Preserve screenshots and records; never post private guest data.
- Classify: choose painful-but-plausible, factually disputed, or policy-violating. Do not call a review fake just because you cannot find the name.
- Report only when the content appears to break policy. Google says it will not remove a review simply because a business dislikes or disagrees with it.
- Reply for the next guest: keep it short, state one useful fact, avoid personal attacks, and offer a private way to continue.
- Escalate safety, discrimination, threats, extortion, or legal claims to the owner or appropriate adviser before any public reply.
- Verify: have the owner or manager check facts, tone, and policy before the reply goes live.

Template — disputed fact, real visit: "Hi [name] — I'm sorry this visit landed badly. I checked our records for [date/time], and they show [one neutral, material fact]. I do not want to argue with your experience here. Please contact me at [email/phone] so I can understand the gap and follow up. — [Name], [Role]"

Template — no matching record: "Hi [name] — I take this seriously, but I have not been able to match the details to a visit or order in our records. Could you contact me at [email/phone] with the date and order name so I can investigate properly? — [Name], [Role]"

Template — reported for a policy concern: "Hi [name] — we have reviewed the details available to us and cannot verify the experience described. We have asked Google to review the post under its content policy. If this relates to a genuine visit, please contact me at [email/phone] so I can investigate directly. — [Name], [Role]"

This is also the standard Semperi is built around: write the reply from restaurant context and keep each factual claim traceable. The legacy guide at /blog/ai-review-replies-with-human-approval explains how context changes reply quality.

## Positive review templates (10)

1. "Hi [name] — so glad the [specific dish] worked for you. [Chef/cook name] makes that one personally with [specific ingredient/technique]. Hope to see you on [day-specific event]. — [Your name]"

2. "Thanks [name] — [server name] said you were a great table. The [dish] is one we're proud of, and we appreciate you noticing the [specific detail like presentation, sourcing, technique]. — [Your name]"

3. "Hi [name], we're really glad the [occasion — birthday, date, anniversary] worked. [Detail from the review you can build on]. Come back for [upcoming menu change or event]. — [Your name]"

4. "Thanks [name] — your point about [specific dish] being [adjective] means a lot, since we [process detail like "make it daily" or "source from a local farm"]. — [Your name]"

5. "Hi [name] — really appreciate the kind words about [server name]. They've been with us [time] and we're lucky to have them on the floor. — [Your name]"

6. "Hi [name], glad the [specific dish] hit the mark. We've been refining it since [time/season detail]. Try the [companion dish] next time — same energy. — [Your name]"

7. "Thanks [name] — [room detail like "the corner booth" or "the patio"] is a favorite spot for a lot of our regulars. Glad you found it. — [Your name]"

8. "Hi [name], thanks for noticing the [specific touch — wine pairing, garnish, plate]. Our [team member name] put real thought into that. — [Your name]"

9. "Hi [name] — really glad the [meal type — brunch, lunch, dinner] worked. We just added [new item or detail], you'd probably like it. — [Your name]"

10. "Thanks [name] — your review made [server/cook name]'s shift. Hope to see you back for [specific upcoming thing]. — [Your name]"

## Negative review — food (10)

1. "Hi [name] — I'm sorry the [dish] arrived [issue — cold, undercooked, oversalted]. That's not what we want from that dish. I've talked with [chef/kitchen lead name] and we're tightening our [specific fix]. If you'd come back, please ask for me — I'd like to make it right. — [Your name]"

2. "Hi [name], I'm sorry the [dish] wasn't right. We change suppliers on [ingredient] seasonally and the spring crop has been inconsistent — we should have caught that on the pass. Your meal is on us next time, please ask for me. — [Your name]"

3. "Hi [name] — thank you for telling us about the [issue]. The fact that it happened on a [specific day/occasion] makes it worse. I've shared this with [team member] and we're [specific fix]. — [Your name]"

4. "Hi [name], the [dish] should never arrive [issue]. I want to understand what happened — could you email me at [email]? I'd like to follow up properly. — [Your name]"

5. "Hi [name] — sorry the [dish] missed. We just changed [specific element — recipe, technique, supplier] and we're still calibrating. Please give us another shot. — [Your name]"

6. "Hi [name], you're right — the [dish] at $[price] should deliver more than it did that night. I've shared your note with [chef]. — [Your name]"

7. "Hi [name] — I'm sorry the [dish] wasn't to your taste. We make it [traditional/regional style] which can be a surprise if you're expecting [the more common version]. Next time I'd recommend the [alternative dish] — I think it'd be more your speed. — [Your name]"

8. "Hi [name], the portion question is fair — we [recently changed/have always done] it that way because [genuine reason]. I hear you that it didn't read as good value. — [Your name]"

9. "Hi [name] — the [issue with dish] is on us. We have a checklist for the pass and clearly missed it that night. I've spoken with the team. — [Your name]"

10. "Hi [name], I'm sorry. The [dish] is one we feel strongly about and what you described isn't the version we want to send out. Please come back — your meal is on me. — [Your name]"

## Negative review — service (8)

1. "Hi [name] — I'm sorry about the experience with [the moment — greeting, server attention, check timing]. That's not the floor we run. [Specific fix — "I've already spoken with the team" or "we're retraining on this exact moment"]. — [Your name]"

2. "Hi [name], that's not the welcome we want for any guest. Could you tell me the day/time you came in? I want to figure out what went wrong with [specific staff role]. — [Your name]"

3. "Hi [name] — being ignored at the table is one of the worst things we can do. I'm sorry. We're tight on [specific section — bar, host stand, patio] on weekends and it shouldn't show. — [Your name]"

4. "Hi [name], I'm sorry [server name or "your server"] missed the moment. They're [new/usually great] and [specific accountability — "we've reviewed the night" or "we're working on attentiveness"]. — [Your name]"

5. "Hi [name] — paying attention to [specific need — dietary, kids, accessibility] is exactly what we should be doing. Sorry we missed it. — [Your name]"

6. "Hi [name], you waited too long for [specific moment — water, check, bread]. That's a basic miss. — [Your name]"

7. "Hi [name] — I hear you on the tone. Service should never feel like that, regardless of how busy we are. — [Your name]"

8. "Hi [name], I'm sorry — and I want to learn more. Could you email me at [email]? The detail you described isn't something I can fix from this review alone. — [Your name]"

## Negative review — wait time (5)

1. "Hi [name] — [length] is too long for [specific moment — the bar, a confirmed reservation, takeout]. That's on us. We've [specific fix — "added a host on Friday nights" or "shifted our seating cadence"]. — [Your name]"

2. "Hi [name], a confirmed reservation should not wait [length]. I'm sorry. We had [genuine reason — a large party that ran over, a no-show seating issue] and we should have communicated. — [Your name]"

3. "Hi [name] — kitchen times that night were running long because of [genuine reason]. We should have warned you when you ordered. — [Your name]"

4. "Hi [name], the wait at the bar was excessive — sorry. We're rethinking how we hold reservations on Saturdays. — [Your name]"

5. "Hi [name] — the takeout window was too long. We're shifting our [specific fix — "prep schedule" or "order routing"]. — [Your name]"

## Negative review — cleanliness (4)

1. "Hi [name] — the [bathroom/table/area] should never look like that. We've added [specific fix — "a bi-hourly check" or "a new cleaning rotation"]. — [Your name]"

2. "Hi [name], that's not acceptable and I'm sorry. [Specific role — manager, dish lead] is owning this. — [Your name]"

3. "Hi [name] — I want to understand exactly what you saw. Could you email me at [email]? — [Your name]"

4. "Hi [name], I'm sorry. [Specific fix already in motion]. — [Your name]"

## Allergy and dietary (5)

These need extra care. Never minimize. Always offer a direct contact.

1. "Hi [name] — I'm taking this seriously. An allergen mistake is a safety issue. Please email me directly at [email] — I want to understand exactly what happened so we can fix it. — [Your name], [Title]"

2. "Hi [name], I'm so sorry. Cross-contact in the kitchen is something we train hard on and clearly missed that night. Please contact me at [email]. — [Your name]"

3. "Hi [name] — guests with dietary needs deserve full confidence in what we serve. We failed that. I'd like to talk directly: [email]. — [Your name]"

4. "Hi [name], being told [specific dish] was [allergen]-free when it wasn't is exactly what should not happen. I'm sorry. Please reach me at [email]. — [Your name]"

5. "Hi [name] — vegetarian/vegan/gluten-free guests should never feel like an afterthought. Sorry that's how it landed. We're updating our [menu, training, signage]. — [Your name]"

## Manager-needs-to-respond (4)

Some reviews need senior visibility — accusations of staff misconduct, safety claims, anything that could escalate. The reply doesn't need to litigate; it needs to take it seriously and move it offline.

1. "Hi [name], thank you for raising this. I'm [Name], [title], and I'd like to address what you described directly. Please contact me at [email or phone]. — [Your name]"

2. "Hi [name] — what you described is serious and not something we'll dismiss. I'd like to speak with you privately: [contact]. — [Your name], [Title]"

3. "Hi [name], I take what you said about [staff member or incident] very seriously. I'd like to follow up properly — please reach me at [contact]. — [Your name]"

4. "Hi [name] — I'm the [owner/GM]. I want to understand and address this directly. [Contact]. — [Your name]"

## Mixed review — both praise and criticism (4)

1. "Hi [name] — really glad the [positive thing] worked. You're right about the [negative thing], and we're [specific fix]. — [Your name]"

2. "Hi [name], thanks for the honest write-up. The [praise detail] is exactly what we're going for, and the [criticism] is fair. — [Your name]"

3. "Hi [name] — appreciate the balance here. We'll hold onto the [praise], and own the [criticism]. — [Your name]"

4. "Hi [name], reviews like this are the most useful we get. Glad about [praise]. Working on [criticism]. — [Your name]"

## Tips for using these well

- Customize every bracket — generic templates get spotted by future readers, who notice patterns across replies
- Keep the reply short enough to scan and long enough to add one useful detail
- Apologize clearly once, then move to the fact, fix, or next step
- Don't promise free food publicly unless you mean it — guests collect screenshots
- Reply promptly, but take enough time to check the facts on a disputed review
- Always sign with a real first name and a real title

Use the scenarios above as a starting point, then edit every reply for the specific guest and visit. If you want replies grounded in your restaurant's own context, Grace is at /reviews.

## FAQ

Can I copy these directly? You can use them as scaffolding, but copy-paste defeats the purpose. Customize the brackets and at least one specific detail per reply.

Should I reply to every review? Prioritize reviews where you can add relevant information, resolve a concern, or recognize a specific detail. Google says you do not need to thank every reviewer publicly.

What if the reviewer is wrong? Check the facts, then correct only the material point in neutral language. Do not litigate the whole visit in public. If the review appears to violate policy, report it; disagreement alone is not enough.

Is it okay to ask them to update the review? Sometimes — only after you've actually fixed the issue and they've confirmed they're happy. Never ask preemptively.

What about reviews with no text, just a star rating? Reply with a 1-2 sentence thank-you for positives. For low-star no-text reviews, a short, generic reply ("Hi [name] — sorry your visit didn't meet expectations. If you'd email me at [email] I'd like to make it right.") signals to future readers that you take all feedback seriously.

## Sources and further reading

Google Business Profile Help: manage customer reviews — https://support.google.com/business/answer/3474050

Google Business Profile Help: report inappropriate reviews — https://support.google.com/business/answer/4596773

Google Maps user-generated content policy — https://support.google.com/contributionpolicy/answer/7400114

FTC: Consumer Reviews and Testimonials Rule Q&A — https://www.ftc.gov/business-guidance/resources/consumer-reviews-testimonials-rule-questions-answers

Conversation that prompted this update — https://x.com/InlandCaGuy/status/2081782481595076729


---

Semperi gives your restaurant a team of AI employees working 24/7 to grow your brand, sales, and profit.

- Full site map for agents: https://www.semperi.com/llms.txt
- Free restaurant visibility scan: https://app.semperi.com/scan
- This page for humans: https://www.semperi.com/blog/restaurant-google-review-reply-templates