Sort each complaint before AI touches it. Anything about illness, allergens, injury, discrimination or a named member of staff goes to the owner, with no AI-drafted reply sent. For routine complaints, give the AI your facts and firm rules: thank them, apologise for the experience, state one specific fact, offer to talk offline, never argue, and have a person edit before posting.
Most escalation isn't caused by the complaint; it's caused by the reply. A defensive correction, a copy-paste apology or a public offer of money turns one unhappy diner into a thread. What follows is a triage table, a reusable reply prompt, three complaints taken from AI draft to posted reply, and a monthly check on whether your replies are calming things down.
Sort before you draft: the red-flag table
Print this and keep it by whoever handles reviews. The right-hand column is the one that matters.
| Complaint type | Who handles it | What AI may do |
|---|---|---|
| Illness after eating | Owner or manager, following your food-safety procedure; record it; speak to your insurer if it may become a claim | Nothing, beyond helping format your incident notes |
| Allergic reaction or an allergen mistake | Owner; incident record | Nothing |
| Injury on the premises | Owner and insurer | Nothing |
| Discrimination, harassment or a named member of staff | Owner, after speaking to the staff member | Nothing |
| Foreign object in food | Manager, after investigating | Draft only once the facts are known |
| Slow service, cold or wrong food, noise, value | Whoever handles reviews | Draft; a person edits |
| Booking lost or table not ready | Whoever handles reviews | Draft; a person edits |
| Delivery-app order problems | The app's refund process first, then a short reply | Draft |
The first four rows aren't about tone. A public reply there can read as an admission, contradict what your insurer needs, or expose a colleague. Those replies are short, human and checked: "We're very sorry to hear this and we take it seriously. Please contact [manager's name] on [email] so we can look into it properly." The owner writes it, even if an AI could have.
Red flags don't always announce themselves. A realistic slip (illustrative): a review read "Lovely evening, but I felt a bit rough the next morning after the mussels." The shift lead filed it as a mild complaint and ran it through the prompt, which produced "We're confident our mussels were fresh that evening, so it may have been something else." That sentence disputes an illness claim in public. Within two days the reviewer had replied with a photo of the receipt and two other diners had added comments. The fix is a keyword list pinned beside the table, so the triage doesn't depend on judgement at the end of a shift:
Send to the owner, no AI draft, if the complaint mentions: unwell, ill, sick, rough, stomach, poisoning, vomiting, reaction, rash, swelling, hospital, doctor, allergy, nuts, gluten, "cut myself", slipped, fell, racist, sexist, rude to me because, or any staff member's name.
What turns a complaint into a row
Before you write the prompt, know what you're telling the AI to avoid. These are the moves that escalate:
- Correcting the diner in public. "Actually, you waited 35 minutes, not 50" may be true and still loses every reader.
- Quoting the booking or bill. Order details, party names and amounts are the diner's business, not the internet's.
- Naming or defending staff. "Sam is one of our best servers" invites a reply about Sam.
- "We've never had a complaint about this before." Readers hear "you're lying".
- The identical apology on every review. Diners scroll. Three replies starting "We're so sorry to hear about your experience" look like nobody read any of them.
- Offering money or a free meal in public. It invites copycat complaints, and any offer linked to changing the review breaks platform rules (more on that below).
- A second round. If the diner replies angrily, don't reply again publicly. Take it offline.
A draft can escalate without a single rude word in it. Review (one star, on a delivery app): "Curry arrived cold and the naan was missing. $38 wasted."
Facts: the order was ready 12 minutes after it was placed; the courier collected it 25 minutes later; the naan was missed at packing.
A first AI draft (sample output, illustrative) opened: "Our records show your order was ready within 12 minutes, but the courier collected it 25 minutes later, which will have affected the temperature." Every word may be true and it still escalates: it blames someone the diner can't see, quotes order details, and turns an apology into an explanation. What got posted was shorter:
Thank you for letting us know, and sorry: a missing naan is our packing mistake, and a curry should never arrive cold. We've added a second check on every bag before it leaves. For a refund on the order, the app's help section is the quickest route. [Name], owner
It owns the part that was theirs, doesn't argue about the part that wasn't, and repeats no amounts. The timing facts still earned their place: they went to the delivery app's merchant support as a complaint about collection times, which is where they could change something.
The complaint-reply prompt
Set this up once in a project or saved prompt, then paste each complaint with your facts underneath:
You draft replies to restaurant reviews for [restaurant name].
Our tone: [e.g. warm, plain, short. We sign as "[first name], owner".]
Rules:
- Under 90 words.
- Thank them for taking the time to write.
- Apologise for the experience, specifically (name the actual issue).
- Include at most ONE fact from the facts I give you, stated calmly.
- Offer a direct contact to talk it through: [name, email].
- Never argue, correct their account, or say "never had a complaint".
- Never mention bill amounts, booking details or staff names.
- Never offer refunds, vouchers or free meals.
- Don't start with "We're so sorry to hear about your experience".
- Give me 2 versions: one more formal, one more personal.
Review: [paste]
Our facts: [what actually happened, from the manager's notes]The "our facts" line is what stops generic replies. Without it the AI has nothing specific to say, so it fills the space with apology. With it, one concrete sentence ("Two of our kitchen team were off sick that night and we should have warned you when you sat down") shows you looked into it.
The same slow-mains review, with two different facts lines (sample outputs, illustrative). With "Our facts: it was a busy night", the draft says: "We're sorry you didn't have the experience you hoped for on what was a very busy evening for us." That reads as an excuse. With "Our facts: mains took 55 minutes after ordering; a new dish on the grill was slowing every ticket; nobody went back to the table to explain", the draft says: "Your mains took far too long, and nobody came back to tell you why, which is the part I'm sorriest about. We've taken the new grill dish off until the kitchen can send it out quickly." The prompt's rules keep the table number and times out of the public reply; the detail just gives the AI something true to say.
Three complaints worked through
1. The long wait on a Saturday
Review (one star): "Waited nearly an hour for mains. Server vanished. Won't be back."
Manager's facts: Saturday, fully booked, two chefs off sick, kitchen running about 30 minutes behind by 8pm. Tables weren't told.
Posted reply, after editing the AI draft:
Thank you for telling us. You're right that the wait was far too long on Saturday. We were two chefs down and should have told you when you sat down instead of leaving you wondering. That's on us, and we've changed how we warn tables when the kitchen is behind. If you'd like to talk it through, I'm on [email]. [Name], owner
What changed from the draft: the AI's version said "we strive to deliver exceptional service", which was cut, and it mentioned "our wonderful team working hard", which sounds like an excuse. The fix ("we've changed how we warn tables") was added by the owner because only the owner knew it was true.
2. The service charge nobody noticed
Review (two stars): "Food fine but they sneak a service charge on the bill. Felt ripped off."
Facts: The charge is printed on the menu and the bill, but not mentioned by staff.
Thanks for the honest feedback. Our service charge is printed on the menu and the bill, but we can see how it's easy to miss, and nobody should feel caught out at the end of a meal. We're asking our team to mention it when they bring the bill. If anything else about the visit wasn't right, I'd like to hear it: [email]. [Name]
One fact, stated once, then a concession. No lecture on where the charge is printed.
3. The private email about a manager
Email: "My steak was overcooked and when I raised it the manager was dismissive."
Because it names a member of staff, the owner handles it and speaks to the manager first. The AI's role is limited to helping structure the reply once the owner knows what happened. Privately, unlike in public, you can offer to put it right:
Thank you for emailing, and I'm sorry: an overcooked steak is disappointing, and it should have been replaced without any fuss. I've spoken to the manager on duty about how it was handled. I'd like to invite you back as our guests so we can do it properly; just reply to this email with a date. [Name], owner
That invitation is fine because it isn't connected to any review. The moment it becomes "and perhaps you could update your review", it isn't.
The 30-second check before anyone presses post
Whoever posts the reply, whether that's you, a manager or a front-of-house lead, runs through five questions. If any answer is "no", it goes back for another edit:
- Read aloud, does it sound like a person at this restaurant rather than a hotel chain?
- Is every fact in it true, and checked with whoever was on shift?
- Is it free of names, bill amounts, booking details and anything about the diner's party?
- Is there no offer of money, vouchers or free food anywhere in it?
- Does it open differently from the last reply you posted?
Thirty seconds is realistic once the habit forms. The fifth question is the one people skip, and it's the one readers notice first.
A before-and-after from one month's replies (illustrative). The first three openings, posted in the same week: "We're sorry to hear about your visit…", "We're so sorry to hear about your experience…", "Sorry to hear you didn't enjoy…". Rewritten so each opens on something from the review itself: "You're right about the noise on Friday…", "Thank you for the detail about the risotto…", "A 40-minute wait for starters isn't acceptable…". Nothing else about the replies changed, and together they now read like three people were listened to.
Holding lines for the red-flag complaints
For the first four rows of the triage table, the owner still needs something to post while the facts are gathered, because silence on a public illness complaint reads badly. Keep a few approved holding lines, written once and checked with your insurer if you have one, rather than asking an AI in the moment:
- Illness: "We're sorry to hear you were unwell and we take this seriously. Please contact [name] on [email] so we can look into it with you."
- Allergen: "Thank you for letting us know. This is serious and we want to understand exactly what happened. Please contact [name] directly on [email]."
- Staff conduct: "We're sorry, and we're looking into this. Please get in touch with me directly on [email]. [Name], owner."
None of these admits fault or disputes it. They show you've heard it and moved it somewhere private, which is all a public reply to a serious complaint can usefully do.
The incentives rule and Google's own AI option
Google's Maps content policy prohibits businesses from offering incentives, such as discounts or free goods and services, in exchange for a review, or for revising or removing a negative one. Breaches can lead to restrictions on your Business Profile. You can find the details in Google's fake engagement policy. Put a line in your prompt and your staff guidance: goodwill is offered privately, unconditionally, and never mentioned alongside the review.
Google's help pages confirm that replies are posted publicly under the business's name, and that you can edit or delete a reply afterwards (see Google's guide to replying to reviews). So a clumsy reply can be fixed, but assume it's been read before you do.
Since March 2026 Google has also been testing a "Reply to reviews with AI" option inside Business Profile for a limited set of accounts. If you see it, treat it as a drafting aid: it doesn't know your facts, so the same edit applies. Whether to let any tool post automatically is a separate decision; should AI auto-post review replies weighs it up, and the short answer for complaints is no.
When the reviewer replies angrily
Sometimes the diner comes back hotter. Don't reply publicly a second time. Send one private message if the platform allows it, or leave your original reply standing with the contact offer in it. The private message can be three sentences: "I'm sorry my reply didn't help. I'd rather sort this out properly than trade messages in public. Could you email me on [email], or tell me a good time to ring you?" Write it yourself; an AI draft at this stage tends to restate your side of the story, which is the opposite of what's needed. If the review turns abusive or makes claims you believe are false, report it through the platform. Handling a fake or unfair review covers that route, and replying to negative reviews with AI has more general examples outside hospitality.
Checking your replies are calming things down
Once a month, spend 20 minutes on three questions:
- Did any reply get a second angry response? Read it again. Usually one sentence corrected or defended something.
- Are the replies distinguishable from each other? Read the last ten in a row. If they blur together, add more facts to the prompt and ban the phrase that keeps recurring.
- What keeps coming up? Five replies about waiting times is an operations problem, not a writing problem. Analysing your reviews with AI shows how to count themes across months so the kitchen and floor can fix the cause.
A filled-in version of that monthly check, for a 50-cover restaurant (illustrative):
| Question | This month | Action |
|---|---|---|
| Second angry responses | 1 of 14 replies. The sentence that caused it: "our kitchen was fully staffed that night" | Added "never mention staffing levels" to the prompt |
| Replies that blur together | "We pride ourselves on…" in 6 of 14 | Phrase banned in the prompt; last six reread |
| Recurring themes | Wait times 5, noise 3, portion size 2 | Wait times to the head chef and floor manager with the five reviews attached |
| Red flags handled by the owner | 1 (possible allergen); holding line posted same day | Incident record completed; no AI involvement |
Twenty minutes, one prompt change, one banned phrase and one operational fix is a good month. If the table comes out empty three months running, check that people are logging the second responses rather than quietly deleting their replies.
Complaint replies: follow-up questions
Should I reply to every negative review?
Reply to every review that describes a real visit, including the unfair ones, because the audience is the next diner reading it, not only the reviewer. Keep it short when the complaint is thin. The exceptions are reviews you believe are fake or that break the platform's rules: report those through the platform first, and reply calmly only if they stay up.
Can I ask a diner to update their review once we've put things right?
You can put things right privately and let the diner decide what to do with their review. What you must not do is offer anything in return for changing or removing it. Google's Maps content policy prohibits incentives such as discounts or free meals in exchange for a review or for revising or removing a negative one, and breaches can lead to restrictions on your profile.
How quickly should we reply?
Within a day or two for routine complaints is a sensible target for a small restaurant, and faster on busy platforms. Speed matters less than getting it right, though: a considered reply the next morning beats a defensive one typed at midnight after service. Red-flag complaints about illness or allergens need a same-day private response, even if the public reply waits.
Further reads
- 7 AI Mistakes Restaurant Owners Make With Bookings and Reviews — The review and booking errors restaurants most often make with AI.
- How to Reply to Hotel Reviews With AI Without Sounding Canned — The hospitality neighbour: hotel review replies that don't sound canned.
- How to Use AI to Respond to Google Reviews — Replying to positive and neutral Google reviews with AI.
- How to Set Up Human Review for AI Work Without Slowing Down — Setting up a quick human check without slowing replies down.
- AI Review Management Tools for Small Businesses (2026) — Tools that pull reviews from several platforms into one place.
- What an AI Implementation Plan Looks Like for a Small Restaurant — One illustrative 48-cover restaurant's AI plan, start to finish: a week of tracking, three jobs chosen, four ruled out, and the day-90 numbers.
- How to Train Front-of-House Staff to Work Alongside AI — Three short sessions, six role-play cards and a one-page counter card for teaching front-of-house teams to work with AI bookings, chat and phone assistants.
- Your First 30 Days of AI in a Restaurant, Week by Week — Four weeks, one owner, 30 minutes a day: what a restaurant should set up with AI each week, what to leave out, and how to judge it at day 30.
- Patient Reviews and AI Replies: Staying Within Confidentiality — How clinics can use AI to reply to online reviews without confirming who is a patient or revealing anything about their care.
- Can AI Handle Customer Complaints Without Making Them Worse? — Where AI speeds up complaint handling, the five ways its replies inflame customers, and one hotel complaint followed from angry email to resolved.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Google Business Profile Help (replying to reviews); Google Maps user-generated content policy (fake engagement and incentivised reviews); Search Engine Land report on Google's test of AI-suggested review replies (March 2026). Checked September 2026.