A complaint is addressed to you. A review is addressed to everyone considering you next month, and the person who wrote it may want nothing from you at all.
That difference is why complaint templates read so badly under a one-star review. A complaint reply satisfies one reader. A review reply also has to satisfy a stranger who arrives later, compares three vendors, and reads the negative reviews first.
When the feedback did arrive as a direct request to fix something, use the four-step method for complaint responses instead. Everything below assumes a third party is watching.
iShort answer
A review reply addresses the reviewer and is written for future customers reading along. Answer the specific point, concede what is true, say what changed, and move the resolution to a private route. Answer unfair reviews once and stop, thank positive reviewers specifically, and fix the help content behind recurring confusion.
The same words that resolve a complaint can read as defensive under a review, because the audience, the goal, and the definition of success are all different.
Different audience
A complaint has one reader. A review has hundreds, most of whom arrive months later, already comparing vendors, and reading the negative ones first.
Different ask
A complaint requests a remedy. A review delivers a verdict and frequently expects no reply, so a reply that only offers a refund misses what it was for.
Different success test
A complaint reply succeeds when the customer is satisfied. A review reply succeeds when a stranger reads the exchange and decides the company is worth the risk.
Different failure mode
A complaint fails by being slow. A review fails by being generic, because a reply that fits any review proves nobody read this one.
Bad experiences travel further than good ones. In a Harvard Business Review study of more than 75,000 customers, 65% were likely to speak negatively about a service experience, against 25% likely to say something positive. 48% of customers with a negative experience told 10 or more people, compared with 23% after a positive one. A public review reply is your one chance to answer that story where others can see it.
Who is a review reply written for?
A review reply addresses the reviewer, but future customers are the real audience. Every difference between a good review reply and a good complaint reply comes from writing for both at once.
| Because the real audience is future customers | The reply changes like this |
|---|---|
| They skim | Keep it to three or four sentences. Nobody finishes a thorough paragraph |
| They judge how you behave under criticism more than who is right | A measured tone outperforms a correct rebuttal |
| They want to know whether feedback goes anywhere | Name the specific change, or say honestly that there will not be one |
| They will see whatever you disclose | Never mention account details, order history, plan, or spend |
| They discount anything that sounds automated | Specific beats polished, every time |
The last row matters most. A reply that opens "We're sorry to hear about your experience and have passed this to the relevant team" is grammatically fine and reads, to anyone comparing vendors, as confirmation that nothing happened.
Should you respond to every negative review?
Respond to every review that names something specific and to every one-star or two-star review. Leave bare star ratings with no text.
Does the feedback name something specific?
- If yes→Answer it, whatever the rating
- If no, a bare star rating with no text→Leave it. There is nothing to answer, and a generic reply advertises generic replies
How many stars?
- If one or two→Always answer, even where the text is thin
- If three, with detail→Answer first. It reads as the most credible review and it is usually the one left unanswered
- If four or five→Answer specifically, and ask for a case study
Where did it appear?
- If review site or app store→Days is fine. These are read for months
- If social media→Within the hour. It runs on the complaint clock, not the review clock
- If private survey or NPS field→Reply personally by email, and never publish it without asking
Give the detailed three-star review extra attention. It reads as measured and credible, and it often sits unanswered while the team debates the one-star.
How do you respond to negative reviews on each platform?
Keep the reply short and specific everywhere, and adjust for how each platform is read. Square brackets mark what has to be replaced, and a published reply with an unedited bracket is worse than no reply.
Google review, one or two stars
Public, permanent, and frequently the first thing a local search shows. Keep it short and route it.
[Name], thank you for writing this. [The specific problem, named plainly] should not have happened, and it did. What changed since: [specific action, with a month if possible]. [If nothing has changed yet: We are fixing [x] and I would rather say that than claim it is already done.] I would like to sort out your side of it directly. [Name] at [email] reaches me, and you will not have to explain it again. [First name], [role]
Google review, three stars with real detail
Thank you for a useful review, and particularly for separating what worked from what did not. You are right that [the specific weakness]. [One sentence of context only where it adds something the reader could not guess.] [What changed, or what will, with honest timing.] Glad [the part that worked] landed. If [the weak part] gets fixed properly, I would be interested to know whether it changes your view. [Email]. [First name], [role]
G2, Capterra, or another software review site
The audience is a buyer mid-evaluation, often with a shortlist and a spreadsheet, so specifics beat warmth.
Thanks for the detail. It is more useful than most reviews we get. On [limitation]: that is accurate. [Current state in plain terms, including what it does not do.] [Roadmap position with honest timing, or a plain statement that it is not planned and why.] On [second point]: [specific answer, or an acknowledgement that it is a real gap]. For anyone reading this while evaluating: [the one thing a buyer should actually check before choosing, stated straight]. Happy to answer questions directly at [email]. [First name], [role]
App store review
Keep it short and name the version. On Google Play, the reviewer gets a push notification and an email when you reply, according to Play Console Help.
Sorry about [specific issue]. Fixed in [version], released [date]. If it persists after updating, [support email] and send your device model, and we will chase it directly rather than asking you to reinstall.
NPS detractor verbatim
NPS comments are private and usually attached to a score. Answer them by email from a person, and use the five-part email structure for the reply.
Hi [Name], You scored us [number] and wrote: "[their words, quoted exactly]". Thank you for writing something as well as scoring. The comment is the useful part of a survey. I do not want to guess at the rest. [One specific question, not a request for a call.] If it is easier to say it in one line, that is plenty. If you would rather not spend more time on us, that is completely fair too, and I will work from what you have already written. [Your name], [role]
Two rules on NPS. Answer from a person, because a reply from the survey platform reads as an automated loop. Never publish a verbatim as a testimonial without asking, however good it is.
Email or in-product survey, low score
Hi [Name], You rated [interaction] on [date] as [rating]. I have read the conversation. [What went wrong, named specifically.] That is a fair rating. [What has changed as a result, or the honest position: I cannot promise a change I do not control. I have raised it with [team] with your example attached.] If [the underlying problem] is still open, reply here and it comes straight to me. [Your name]
Social media
Social media runs on the complaint clock. Reply publicly within the hour and resolve privately.
That is a fair criticism and [the specific thing] is on us. DM sent with a direct line to me. [First name], [role].
For threads carrying real anger instead of considered criticism, use the de-escalation scripts for angry customers.
How do you respond to an unfair or untrue review?
Answer once, calmly, for the future reader, and then stop.
Thank you for the feedback, and I want to give the full picture for anyone reading. [Neutral sequence of what happened, with dates. No adjectives, no defensiveness.] Where you are right: [anything true, however small]. [What changed because of it.] [Name] at [email] if you would like to go through it directly. [First name], [role]
Three rules keep the reply from costing more than the review did.
Do not reply twice. A single measured reply reads as confidence. A second reply reads as an argument, and readers side with whoever appears less invested in winning.
Concede something real. A reply that disputes every point and concedes nothing reads as defensive even when every word of it is accurate. There is almost always a true part: the page was ambiguous, the confirmation email never arrived, or the wait was long.
Report policy breaches through the platform, not in the thread. Reviews containing false factual claims, competitor content, or personal abuse usually violate the platform's own rules. Use the reporting route. Arguing publicly about a review's legitimacy rarely convinces readers.
In the US, some responses are also illegal. The FTC's Consumer Reviews and Testimonials rule, in effect since October 21, 2024, bans suppressing negative reviews through threats or false accusations. It also bans offering incentives conditioned on a positive review.
How should you respond to positive feedback?
Thank the reviewer for the specific thing they named. A copy-pasted thank-you turns real social proof into evidence that the company automates its gratitude, and two extra sentences fix it.
Thank you, [Name], and specifically for mentioning [the thing they praised], which [why it is true: the team that owns it, the decision behind it]. One thing that might be useful: [a related capability or tip they have probably not found yet]. If you ever felt like writing up how you use [product] for [use case], I would be glad to help put it together. Either way, thank you for taking the time. [First name], [role]
Three rules apply:
- Be specific. The identical reply under twenty reviews is visible to anyone who scrolls.
- Do not upsell. A sales line attached to a thank-you cheapens it.
- Ask for something worth more than the star, such as a case study, a referral, or permission to quote them. A customer who just praised you in public is a good person to ask.
How do you turn feedback into content that prevents it?
Route each theme to the surface that would have prevented it. Replies handle the review in front of you, and routing reduces next quarter's volume.
| Scenario | Best pick | Why |
|---|---|---|
| "It doesn't do [x]" and it really does not | Product backlog | Real gap. Log it with the review attached so the theme carries weight, not just the individual request. |
| "It doesn't do [x]" and it actually does | Help content and onboarding | A discoverability failure reported as a capability failure. The fix is a page and a nudge, not a feature. |
| "Nobody replied for days" | First-touch coverage | Most of this builds in the silence before anyone reads the message. Automate that first touch. |
| "Support couldn't answer" | Internal knowledge base | The team answered from memory because the answer was not written down anywhere retrievable. |
| "Confusing to set up" | Documentation and empty states | Confusion is usually a content gap, and it is the cheapest theme on this list to retire. |
The bottom three rows share one fix: written answers that stay current. A service team quotes them, a help page publishes them, and an AI chatbot for customer service retrieves from them. Fixing the page behind a review retires the whole theme.
So train an assistant on your existing content instead of a separate script. SiteGPT trains on 12 or more sources, including help centers, so the answer a customer gets at 2am comes from the same page the team quotes at 2pm.
Auto-sync keeps those answers current, and human escalation is available on every SiteGPT plan when a customer asks for a person. A bot that answers from stale or missing content can also invent an answer, which produces exactly the reviews this page covers. The causes and fixes are in chatbot hallucinations.
For drafting individual replies at volume, the free AI reply generator turns a review into a first draft. Edit it before publishing, because a review reply that reads as generated is worse than no reply.
Frequently asked questions
What is the difference between a complaint and negative feedback?
A complaint is addressed to you and asks for a fix. Feedback is a verdict delivered to a third party, often expecting no reply. A complaint reply succeeds when the customer is satisfied. A review reply succeeds when a stranger reading it later decides you are worth the risk.
Should you respond to every negative review?
Answer every review that names something specific, and every one-star and two-star review regardless. Skip bare ratings with no text. The costliest unanswered review is the detailed three-star one.
How quickly should you respond to a negative review?
Reply within days on review sites and within the hour on social. Reviews are read for months, so a considered reply beats a fast one, but a reply weeks later reads as reputation management.
How do you respond to a negative review that is unfair or untrue?
Answer once, calmly, for the future reader. State the sequence neutrally, concede whatever is true, offer a private route, and do not reply again. Report policy breaches through the platform rather than arguing in the thread.
Should you ask a customer to remove or change their review?
No. Fix it, tell them it is fixed, and leave the request off. Many reviewers update unprompted, several platforms forbid incentivizing a change, and in the US the FTC bans incentives conditioned on positive reviews.
How do you respond to positive customer feedback?
Thank them for the specific thing they named, add one useful tip, and skip the upsell. Then ask for a case study or referral.
What should you do with feedback after replying to it?
Route the theme to whatever would have prevented it. Missing capabilities go to the backlog. Confusion goes to the help content, usually the cheaper and faster fix.
Sources
- Harvard Business Review, Stop Trying to Delight Your Customers, Dixon, Freeman and Toman, July-August 2010, for how far negative and positive service experiences spread
- Google Business Profile Help, Tips to write better review replies, for keeping replies short, polite, and free of customer details
- Play Console Help, View and analyze your app's ratings and reviews, for reply notifications and the developer comment policy
- FTC, Consumer Reviews and Testimonials Rule: Questions and Answers, for the bans on review suppression and sentiment-conditioned incentives