The task
A 1-star review hit your product page 35 minutes ago. The reviewer says the medium shirt arrived two sizes too big, the support email took 6 days to respond, and “I won’t be ordering again.” Your records confirm the sizing was right but the support email did sit unanswered for 4 days. The next 50 prospective buyers will read that review — and your reply, which they treat as the real signal of how you handle problems. You need a public reply in under 100 words that names the specific issue (not “your experience”), accepts the part you got wrong, doesn’t argue the part you didn’t, and moves resolution into a private channel.
Where AI helps — and where it does not
AI is excellent at empathy framing without sounding scripted, naming the specific complaint instead of fluffing it, mirroring the reviewer’s exact phrasing (which signals you read carefully), and closing with a concrete next step. It’s also good at compressing a draft to 100 words so future buyers actually finish reading it. What AI cannot do: fact-check the customer’s claim against your data. Verify with your records before promising anything. Never let AI promise a refund, replacement, or escalation you haven’t approved.
The named failure mode: the scripted apology. AI defaults to “Thank you for your valuable feedback. We are deeply sorry to hear about your experience.” Future buyers read it as canned, and the reply does worse than no reply. Force the prompt: name the specific issue in line one, use the reviewer’s exact words for the problem.
What to feed the AI
- The exact review text — copy-paste, don’t summarize
- What actually happened from your records — order date, what shipped, support history, refund status
- What you can legitimately offer (refund / replacement / store credit / apology only) — be honest
- The platform — Amazon, Etsy, Google Maps, App Store — each has a different audience norm
- 2-3 similar prior replies that worked for you (so AI matches your house tone)
- Whether you’ve already been in contact with this customer privately
- The two parts you got wrong vs. the parts the reviewer got wrong — be honest in your input
- The single sentence you want a future buyer to take away from reading the reply
Copy-ready prompt
Write a reply to a negative review.
Review text (exact, do not summarize):
{paste verbatim}
What actually happened from my records: {order date, what shipped, support response timeline, refund status}
What I can legitimately offer: {refund / replacement / store credit / apology only — be honest about what I've approved}
Platform: {Amazon / Etsy / Google Maps / App Store / Shopify}
House tone (paste 1-2 prior replies that worked): {paste}
Already in private contact with this customer: {yes / no}
What I got wrong: {list}
What the reviewer got wrong (don't argue in public): {list}
One sentence I want a future buyer to take away: {paste}
Structure:
1) Open by naming the specific issue. Not "thanks for the feedback" or "sorry to hear." Use the reviewer's own word for the problem.
2) Acknowledge the real frustration — but in one line, not three.
3) State what actually happened from our side, factually, only on points the reviewer got wrong. Do NOT relitigate points where the reviewer is right; just own them.
4) State the offer concretely. If you've approved a refund, say so. If you're inviting them to DM, say where.
5) Invite to a private channel for resolution — give the specific email or DM path.
Rules:
- Under 100 words.
- No "however", "we believe", "kindly", "we strive to". Each of these signals scripted.
- Mirror the reviewer's exact phrasing for the problem. If they said "way too big", don't translate it to "sizing issue."
- Do not promise anything I did not list in "what I can offer."
- Audience: the next 50 buyers, not just this reviewer.Shorter variant — Amazon-style 60-word reply
60-word Amazon reply to this 1-star review.
Review: {paste}
What I can offer: {paste}
One sentence I want future buyers to take from this: {paste}
Open by naming the specific issue in the reviewer's words. Own what's owed. State the offer. Give a contact path. No "thanks for your valuable feedback."Sample output
A strong opener: “Hi Mark — you ordered the medium, we shipped a large, and our support email sat for 4 days. That’s on us.” That beats “Thank you for your valuable feedback. We are deeply sorry to hear about your experience.”
A strong middle: “We’ve issued a full refund this morning (you should see it in 3-5 days) and the replacement medium is in the post with tracking sent to your order email. The 4-day support gap was due to staffing change last month and we’ve added coverage — you should see <24-hour replies going forward.”
A strong close: “If anything else looks off when the replacement arrives, reply to the order email or DM us here and we’ll handle it same day. Sorry for the friction, Mark.”
A strong full reply that future buyers will read positively: “Hi Mark — you ordered the medium, we shipped a large, and our support email sat for 4 days. That’s on us. We’ve refunded the order this morning (3-5 days) and the correct medium is in the post. The 4-day delay was a staffing gap that’s now fixed — replies should be under 24 hours going forward. Anything off when the replacement arrives, reply to the order email and we’ll handle it same day. Sorry for the friction.”
How to refine
- Strip the defensive tics: “Delete every ‘however’, ‘we believe’, ‘we strive to’, ‘kindly’. Each one signals scripted. Rewrite without them. If the sentence breaks, the sentence wasn’t doing work.”
- Mirror the reviewer’s words: “Re-read the review. Use the reviewer’s exact phrasing for the problem — if they said ‘way too big’, don’t write ‘sizing discrepancy’. Mirroring signals ‘we read your review’ more than any apology phrase.”
- Cut to 80 words: “Trim to 80 words. Future buyers don’t finish 200-word replies. What survives is signal.”
- Move resolution to private: “Add one specific private contact path (DM here, reply to order email, phone). Don’t say ‘reach out’ — say ‘reply to order #4327 and Sarah will handle it same day.’”
- Test the buyer-perspective read: “Read this reply as if you’re a buyer about to add the product to cart. Does it make you more or less likely to buy? Rewrite anything that makes you less likely.”
Common mistakes
- Generic “sorry to hear about your experience” — future buyers tag it as canned within 3 seconds and the reply does worse than no reply
- Arguing the facts in public — even when you’re right, future buyers see fight, not service; argue only what they got wrong and only briefly
- Promising more than you’ve approved — replying twice with worse news (“actually, we can’t refund”) is worse than one honest reply with a smaller offer
- Same template across every review — buyers can spot the template and discount all replies
- Ignoring the platform norms — Amazon expects formal, Etsy expects warm, Google Maps expects concise; the same words land differently
- Replying within 30 seconds — looks like a bot; an hour later feels human, 48 hours later signals neglect
- Letting AI promise specifics it doesn’t know (a delivery date, a refund amount, a name to escalate to) — verify before publishing
- Engaging with abusive or rant-style reviews — sometimes the best reply is no reply; replying makes the rant more visible
FAQ
- Should I reply to every negative review?: Every review under 3 stars where the complaint is specific. Skip generic rants (“worst product ever, do not buy”) — replying makes them more visible and engages a fight you cannot win. The signal-to-noise threshold is “is there a specific thing the reviewer is upset about?”
- How fast should I reply?: Within 48 hours. Faster than 1-2 hours can look bot-driven; slower than 72 hours signals neglect. Use the first hour to verify your records and approve any offer internally.
- What if the reviewer is wrong?: State what actually happened factually, in one line, without “however” or “we believe.” Then move on. Do not relitigate. Future buyers can read between the lines; they don’t need you to win the argument.
- Should I use the reviewer’s name?: Yes if it’s their first name and it’s a platform where names appear (Amazon, Etsy, Google Maps). Skip on App Store where names are usually handles. Using the name signals you read; not using it signals template.
- What about reviews in another language?: Reply in the reviewer’s language, not yours, even if it’s awkward. Other buyers in that language will read it and remember.