PRACTICAL GUIDE · 7 MIN READ
How to respond to negative Google reviews: examples and a workflow
The practical answer
Respond to a negative Google review by acknowledging the specific concern, explaining only what you can verify and offering a practical next step. Keep the reply calm and concise, protect private information and move account-specific details into a private conversation.
Read the complaint before drafting the reply
A customer who waited without an update needs a different response from someone who misunderstood a quotation. Before writing, identify what happened, how it affected the customer and whether you can verify the details. Check with the location or team involved instead of filling gaps with assumptions.
A public reply has two audiences: the reviewer and people deciding whether to choose your business. A specific, reasonable answer helps both understand how your team handles problems. It should not promise an outcome that has not been approved.
A four-part structure that leaves room for a human voice
- Acknowledge the concern. Refer to the issue in the review without repeating private details.
- Take an appropriate level of responsibility. Apologise for a verified service failure; if facts are uncertain, express concern and explain that you want to investigate.
- Give a useful next step. Offer a private contact channel or describe a process change only if it is actually happening.
- Keep it short. Leave out sales language, defensive explanations and requests to delete the review.
The examples below are fictional starting points. Replace the contact channel with your real business details and check every factual statement before publishing.
Example 1: a late arrival with no update
Review: “The team was 45 minutes late. I had to call twice to find out what was happening.”
We’re sorry you were left waiting without a clear update. We’ve checked with the team and should have let you know about the delay sooner. Please contact our service team through the details on our profile so we can follow up on your appointment directly.
Why this works: it addresses the delay and communication failure without making excuses. Use “we’ve checked” only after you have done so. If you have not verified the account, say that you would like to look into the appointment instead.
Example 2: a price that felt unexpected
Review: “The final bill was higher than I expected. The extra charges weren’t clear.”
Thank you for raising the concern about the final price. We’d like to review the estimate and charges with you so we can understand where the explanation fell short. Please contact our team privately using the details on our profile; we’ll look into it with you.
Why this works: it offers a way to resolve the uncertainty without arguing over the invoice in public. Do not publish the customer’s bill, booking details or payment history. If an error is confirmed, handle the correction through the appropriate private channel.
Example 3: a service outcome that did not meet expectations
Review: “Some areas were still dirty after the service. I expected a more thorough job.”
We’re sorry the result did not meet your expectations. We’d like to understand which areas need attention and review the service with you. Please contact our team through the details on our profile so we can discuss an appropriate next step.
Why this works: it focuses on the outcome and gives the customer a route forward. Promise a return visit, refund or replacement only when your team has authorised it and the circumstances support it.
What if you cannot identify the customer?
Do not assume that an unfamiliar name means a review is fake. The reviewer may use a different public name or may have booked through someone else. Explain that you would like to investigate and ask them to contact you privately with enough information to locate the interaction.
If a review appears to violate Google’s content policies, use Google’s reporting process and describe the policy concern accurately. Disagreement or a low rating alone is not a reason for removal. Avoid threats, personal attacks or offering an incentive to change or remove a review.
Build an approval workflow your team can sustain
Assign an owner to monitor new reviews. Routine replies can follow your normal approval process; concerns involving safety, personal data, discrimination or a serious allegation should go to the person responsible for handling that issue before a public response is posted.
- Check the draft against the original review and the verified facts.
- Remove personal, booking and payment details.
- Confirm the contact channel works and someone will follow up.
- Confirm any promised remedy or operational change is authorised.
- Read the reply aloud: does it sound like your team, rather than a generic template?
Google explains that verified businesses can reply to reviews through their Business Profile, and that replies appear publicly. Check its current guidance before designing your publishing process. Automated drafts should still be reviewed for tone, accuracy and privacy.
For complaints that keep returning, turn recurring review themes into a weekly priority. If several teams share responsibility, use a named review owner and backup at each location.
Close the loop after the reply
A well-written answer does not repair the underlying service problem. Log the complaint, assign any follow-up and check whether similar reviews recur. A useful reply workflow connects communication to operations: who will call the customer, who will inspect the work and who will confirm completion?
Track time to first response and unresolved follow-ups alongside ratings. Do not make changing the customer’s review a condition of helping them.
Common questions
Should I reply to every negative review?
Review each one and decide on a proportionate response. Most substantive complaints benefit from acknowledgement and a next step. For abusive or policy-violating content, check the reporting process and avoid escalating the exchange.
Can I use AI to draft a review response?
A drafting tool can help with wording, but a person should check the facts, privacy and proposed remedy. Never let a draft invent a refund, an investigation or a process change.
Official guidance
Written by the Kīrtelo team. Workflows and examples are editorial suggestions, not Google requirements or verified product outcomes.