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 single difference is why complaint templates read so badly under a one-star review. The complaint reply is written to satisfy one reader; the review reply has to satisfy a reader who has not arrived yet, is comparing three vendors, and is scanning the negative reviews first because that is what people do.
When the feedback did arrive as a direct request to fix something, use the A.C.T. method for complaint responses instead. Everything below assumes a third party is watching.
iShort answer
Feedback is a verdict delivered to a third party, not a request delivered to you, so the reply is written for future readers while addressing the reviewer. Answer the specific thing rather than the category, concede whatever is true before adding any context, say what actually changed, and move the resolution to a named private route rather than negotiating in public. Answer unfair reviews once, calmly, then stop. Answer positive feedback specifically rather than with a copy-pasted thank-you, and use it to ask for a case study. Then route the theme to the surface that prevents it, which for confusion is almost always the help content rather than the product.
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.
The public-audience principle
Write to the reviewer. Write for the reader who has not arrived yet. Every difference between a good review reply and a good complaint reply follows from holding both at once.
| Because the real audience is future customers | The reply changes like this |
|---|---|
| They are scanning, not reading | Short. Three or four sentences beats a thorough paragraph nobody finishes |
| They are testing behavior under criticism, not adjudicating facts | 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 does the most work. 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.
Which feedback to answer, and which to leave
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. This is the review prospects trust most 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
The detailed three-star review deserves the emphasis. It is measured, it is credible, prospective customers weight it more heavily than either extreme, and it usually sits unanswered while the team debates how to handle the one-star.
Templates by platform
Square brackets mark what has to be replaced. A published reply with an unedited bracket in it is worse than no reply, and it happens.
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 genuinely 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, which 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
Character limits are tight, the reviewer usually cannot be contacted, and version numbers matter.
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
Private, usually attached to a score, and answered by email from a person rather than from a survey tool.
Hi [Name], You scored us [number] and wrote: "[their words, quoted exactly]". Thank you for writing something rather than just scoring, which is the part that makes a survey useful. 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, not from the survey platform, or the response reads as an automated loop. And 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 am not going to promise a change I do not control, but 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
Runs on the complaint clock. Reply publicly within the hour, 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 rather than a considered criticism, the sequencing is different and the de-escalation scripts for angry customers apply instead.
When the feedback is unfair or wrong
Answer once, calmly, for the future reader. 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 genuinely 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 make the difference between a reply that helps and one that costs 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, the wait was genuinely 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 whether a review is legitimate never ends with readers concluding it was not.
Responding to positive feedback without wasting it
Most positive feedback gets a copy-pasted thank-you, which converts real social proof into evidence that the company automates its gratitude. 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 things to hold. Be specific, because the identical reply under twenty reviews is visible to anyone who scrolls. Do not upsell, since a thank-you with a sales line attached retroactively cheapens the thank-you. And ask for something worth more than the star: a case study, a referral, or permission to quote them. A customer who just volunteered praise in public is at the most receptive point they will ever be, and almost nobody asks.
Turning feedback into content that prevents it
Replying is the visible half. The half that reduces next quarter's volume is routing each theme to whichever surface would have prevented it.
| Scenario | Best pick | Why |
|---|---|---|
| "It doesn't do [x]" and it genuinely 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 is generated in the silence before anyone reads it, which is the part worth automating. |
| "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 a content gap far more often than a product one, and it is the cheapest theme on this list to retire. |
The bottom three rows converge on the same asset. Answers written once, kept current, and retrievable are what a service team quotes, what a help page says, and what an AI chatbot for customer service retrieves from. Fixing the page that caused a review retires the theme rather than the review.
That is the practical argument for training an assistant on your existing content rather than 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 it current, which matters because stale answers generate exactly the reviews this page is about, and human escalation stays available on every plan for the moment a customer wants a person instead.
For drafting individual replies at volume, the free AI reply generator turns a review into a first draft. Edit it before publishing. A review reply that reads as generated is worse than no reply, which is the whole argument of this page in one sentence.
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?
Days for review sites, within the hour for 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?
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, and on several platforms incentivizing a change breaches the terms.
How do you respond to positive customer feedback?
Specifically, and without upselling. Name what they named, add one useful thing, and ask for a case study or referral, which is worth more than the star.
What should you do with feedback after replying to it?
Route the theme to whatever would have prevented it. Missing capability goes to the backlog; confusion goes to the help content, which is usually the cheaper and faster fix.