THE SHORT ANSWER
Keep a restaurant review reply brief, specific and calm. Acknowledge the concern, avoid publishing private details, explain the appropriate next step and let a person check the facts before posting. The examples below are fictional writing examples, not statements about a STAM customer or a promise to remove a review.
Read the review before drafting the reply
Separate what the guest describes from what the business can verify. A review may mention waiting time, food, an interaction with staff or an expectation that was not met. Address the actual issue without guessing what happened or making a public accusation about the reviewer.
Google recommends professional, relevant responses and protecting the reviewer’s privacy. If a situation needs investigation, invite the person to use an appropriate private contact route. Avoid placing booking records, order details or other private information in a public response.
Example: a long wait
Fictional review
“We waited much longer than expected and struggled to get an update.”
Possible reply
Thank you for telling us. We’re sorry the wait and communication left you disappointed. Please contact our team with the date of your visit so we can look into what happened and respond properly.
The reply acknowledges both parts of the concern without claiming that an investigation has already happened. Before using it, check the correct contact route and whether there is an accurate, helpful update the team can provide.
Example: a dish did not meet expectations
Fictional review
“The dish wasn’t what we expected, and we left disappointed.”
Possible reply
We’re sorry the dish did not meet your expectations. We’d appreciate the chance to understand more. Please get in touch with our team about your visit so we can review the feedback with the kitchen.
Do not add a refund, discount or replacement promise unless the business has authorised it. A draft should leave room for the team’s real policy and the facts of the visit. Avoid inserting a promotion into a conversation about a disappointing experience.
Choose the next action before writing
A reply draft is one part of handling feedback. Confirm which route is appropriate before anyone publishes it.
| Situation | Next action |
|---|---|
| A specific service disappointment | Check the facts, acknowledge the actual concern and give a suitable contact route. |
| A sensitive or serious allegation | Send it to the named human reviewer; avoid assumptions and private details in public. |
| A compensation request | Check the business’s authorised policy before promising any outcome. |
| A review about the wrong business or a policy concern | Check the platform’s rules and reporting route; do not promise that the review will be removed. |
These are writing and workflow examples, not findings about an actual STAM client review.
Read the review text as well as the rating; a high-star review can still contain a concern that needs human attention.
Keep review handling connected to your local business information. The Google Review Replier preview shows the writing approach; the on-page examples are illustrative and the described pilot uses human approval.
How AI can support the workflow
A useful AI workflow takes the review context and agreed brand voice, prepares a draft, and makes the next decision clear. The team checks that the reply is relevant, accurate and within its authority before publication. Someone also needs to know whether the reply was successfully published or needs attention.
STAM’s Google Review Replier has a real human-approved pilot with publication records. Try the clearly labelled English writing preview on that page. Setup depends on the right Business Profile access and agreed approval rules; it is not a guarantee of unattended publishing for every location.
A final check before pressing publish
- Does the reply address what this person actually wrote?
- Have we checked the business facts and removed assumptions?
- Are we avoiding private information and personal attacks?
- Is any promise something the business can deliver?
- Is the next step clear and is the contact route correct?
Review replies are one part of looking after the business’s public information. Our restaurant local SEO checklist covers the connected profile, website and enquiry checks.
Common questions
Can an agency remove a negative Google review for my restaurant?
A negative opinion is not, by itself, a reason for removal. If a review appears to breach Google’s policies, use the appropriate reporting process and provide relevant information. Neither an agency nor a reply workflow can guarantee removal; keep that separate from writing a helpful response.
Should AI publish every Google review reply automatically?
Use the approval rules agreed for the business and its access. A draft should be checked for relevance, facts, privacy and promises before publication, especially where feedback is sensitive or disputed. STAM’s described pilot uses human approval; the writing preview is clearly labelled as illustrative.
Should a public reply promise a refund or include the guest’s booking details?
Only make an outcome promise the business has authorised, and keep private booking or order details out of a public response. Acknowledge the concern and offer the correct private contact route when investigation is needed. The team should confirm facts and policy before publishing the reply.
Sources & context
Updated 24 October 2026 by STAM Agency. External guidance was checked on this date. Real projects, prepared outputs and illustrative examples are identified in the article; guidance can change.