How to Respond to Good and Bad Reviews
Use short public replies to thank good reviews, acknowledge bad ones, and report policy violations without starting a fight.
Review replies are public. Future customers will read them, and the reviewer gets notified when you reply. Google also reviews replies before they post. That means the reply is not just customer service. It is a trust signal.
The goal is not to win the argument. The goal is to sound calm, specific, and useful enough that the reply helps the next person who reads it.
You do not need to reply to every review. Reply when the public response adds something useful. If the review violates policy, report it instead of turning the comment thread into a fight.
The simple rule
Ask one question first: does this reply add something useful for future readers?
- If yes, reply publicly.
- If no, leave it alone.
- If the review breaks policy, report it.
That keeps the team from replying by reflex.
What a good reply sounds like
Google says replies should be clear, helpful, polite, short, and simple. That is the right bar.
A reply to a positive review
Use three parts:
- thank the reviewer
- mention one real detail
- keep it short
Example:
Thanks for taking the time to leave this review. We’re glad the team could
help and that the job went smoothly. We appreciate you sharing the
experience.
That reply works because it is warm, specific enough to feel real, and short enough to read quickly.
A reply to a negative review
Use four parts:
- acknowledge the experience
- stay calm
- invite offline follow-up if the issue is specific
- do not argue in public
Example:
We’re sorry this experience did not meet expectations. We’d like to
understand what happened and see what next step makes sense. Please contact
our office so we can review the details.
That reply does not pretend the problem did not happen. It also does not turn the review into a back-and-forth in public.
When to report instead of reply
Use a public reply for ordinary praise or criticism.
Report the review when it violates platform policy. Google says disagreement alone is not enough to remove a review.
That means the team should report spam, profanity, fake reviews, extortion, and similar policy violations, but not ordinary bad feelings or criticism the business does not like.
If the issue is really about a private account detail, a specific job history, or anything that would expose the customer, keep the public reply short and move the rest offline.
What not to write
Do not write anything you would not want screenshotted.
That means no:
- defensiveness
- accusations
- threats
- sarcasm
- fake politeness
- discounts for changing the review
- long explanations nobody asked for
- copy-paste replies that sound robotic
- private details about the job or the customer
BrightLocal’s 2026 survey says generic responses are a trust problem, so the reply should be short but still specific enough to feel human.
Replies are read by everyone except the reviewer
The reviewer rarely re-reads the reply. The next homeowner reading the profile does. That is who the reply is written for — the person trying to decide whether to call, watching how the business handles being praised or challenged in public. A defensive reply scares them off. A calm, specific one keeps them on the page.
Before posting any reply, read it back as if you were that next homeowner. If it sounds like the business explaining itself to a stranger, it is fine. If it sounds like the business fighting with one specific person, rewrite it or do not post it.