How to respond to a negative Google review (with examples)
A clear response framework and practical examples for acknowledging a complaint, protecting customer privacy, and assigning a real follow-up.
A public reply has two readers: the person who left the review and the next customer deciding whether to visit. A good response cannot settle every dispute in public. It can show that the business understood the concern, checked what it could, and gave someone a real next step.
Check the facts before you write
Read the review twice and identify the claim that needs an answer. Ask the branch contact to check relevant shift notes or speak with the team. Do not ask staff to guess who the reviewer is from a vague detail, and do not delay a simple acknowledgement while waiting for a full investigation.
If the review appears to break Google’s content policies, use the platform’s reporting process and keep your reply measured. A disagreement, a low rating, or a complaint you consider unfair is not by itself proof that the review violates policy.
Use four parts, then stop
A reliable structure is: name the specific concern, acknowledge its impact, say what you can confirm, and give one next step. Most replies need only a few sentences. A long defense tends to introduce details the public cannot verify and can make a small issue look like an argument.
- Specific: refer to the wait, missed call, or service detail the reviewer mentioned.
- Human: acknowledge the inconvenience without sounding like a legal statement.
- Accurate: own a confirmed mistake; do not claim an investigation is complete if it is not.
- Actionable: give a monitored contact route or say what the team will check next.
Examples that leave room for the facts
These are starting points, not copy-and-paste replies. Replace the bracketed detail only after the branch confirms it; if the detail is not known, leave it out.
- Long wait: “Thanks for letting us know about the wait at [location]. We understand that it disrupted your visit. We’re checking how the queue was handled that day. If you’re willing, please contact [monitored email] so our [role] can follow up.”
- Unanswered call: “You should have been able to reach the branch. We’re checking the call coverage for [day/time] and will address any gap with the team. Please write to [monitored email] if you’d like us to look into your specific visit.”
- Issue not yet verified: “We’re sorry to hear this was your experience. We can’t identify the visit from the information here, but we’d like to understand what happened. Please contact [monitored channel] and mention [non-sensitive reference].”
Keep personal information and pressure out of the reply
Never confirm a customer’s booking, order, health, payment, or contact details in public. Move the conversation to a channel that a named team member checks. Avoid threats, personal attacks, arguments about the reviewer’s motives, or offers that ask them to change or remove a review.
Google advises businesses to keep replies professional, relevant, and concise. Its review policy also prohibits incentives in exchange for posting, changing, or removing reviews. A sincere resolution is appropriate; bargaining for a better rating is not.
Make sure the promise happens after you press send
A reply that says “we’ll be in touch” creates work. Put the follow-up in the same queue as the review, assign a person, and set a due date. When the case closes, note the resolution privately. The public response is only one part of service recovery; the internal handoff is what prevents the customer from having to repeat the story.
If the same complaint appears again, review the pattern with the branch instead of writing a more polished version of the same apology. A recurring queue problem, unclear hours, or missed handoff needs an operating fix, not another template.