A negative review hurts twice: once in the rating average, and once every time a prospective customer reads it. Merchants respond to that pain in two equally wrong ways: ignoring reviews entirely, or fighting every one of them. The productive path is a triage, and it starts with an uncomfortable truth: most negative reviews are support failures, not product failures. “No reply for a week”, “still waiting for my refund”, “nobody answers”. Read your own one-star column and count.
Step one: triage, don’t react
Before you type anything, sort the review into one of three buckets:
- Genuine and justified: a real customer, a real problem, fairly described. This one you answer, publicly and well.
- Genuine but unfair: a real customer, but the story is one-sided or the demand was unreasonable. You answer this one too, calmly, with the missing facts.
- No customer contact recognizable: no matching order, competitor vocabulary, wrong product, or a mix-up with another shop. This one you don’t answer. You report it.
The bucket decides everything, because the two playbooks are opposites.
Answering genuine reviews: you’re writing for the audience
The reviewer may never read your reply. The next hundred prospective customers will. That reframes the job completely: you’re not winning an argument, you’re demonstrating what dealing with your shop is like when something goes wrong.
The structure that works:
- Thank + acknowledge the specific issue. Not “we’re sorry you feel that way”. Name the actual thing: “You waited nine days for a reply to a warranty question. That’s on us.”
- Say what happened and what you changed, in one sentence. No excuses, no essay.
- Move the resolution to a direct channel (“we’ve written to you at the email on your order”), and then actually resolve it. A review that later gains an “update: they fixed it” edit is worth more than five unremarkable five-star ratings.
- Stay boring under provocation. A merchant arguing in public reads as a warning sign to every future customer, even when factually right.
Speed matters here the way it does everywhere in post-purchase: an answer within hours reads as a shop that cares; the same answer after three weeks reads as damage control.
Sample replies to typical negative reviews
Four examples following the structure above. Only mention changes you have actually made.
Late delivery:
“Hi Jonas, thanks for the feedback. You waited twelve days for your parcel and didn’t hear from us in that time. That shouldn’t have happened. One item shipped later than shown, and we should have told you right away. We’ve written to you at the email on your order. From now on we contact customers about delays before they have to ask. Best, Mara”
Defective product:
“Hi Sabine, sorry your kettle stopped heating after three weeks. That’s clearly covered by the legal guarantee, so the costs are on us. We’ve sent you an email: you can choose whether we repair it or send you a new one. Best, Mara”
What the law requires for defects is in our guide to the legal guarantee vs. warranty.
Return frustration:
“Hi Tim, you’re right, your refund took too long. Your return reached us on 3 March, and we only refunded it on 20 March. We’ve since sped up how we check returns. The money has been on its way since 20 March. If it hasn’t arrived yet, please write to us directly and we’ll sort it out right away. Best, Mara”
Genuine but unfair:
“Hi Chris, thanks for your review. For context, for anyone reading: the jacket came back after 45 days, and our return window is 30 days, so we couldn’t accept it anymore. We understand that’s frustrating. If you’d like, write to us and we’ll see what we can still do. Best, Mara”
For the email to an angry customer, there’s a separate template.
Getting fake reviews removed: the process and the trap
On Google you report a review directly on your Business Profile or through the review management tool, choosing a reason such as spam or conflict of interest. Google then checks it against its content policies. According to Google this usually takes several days, and you can appeal a rejection once. If the review breaks the law, for example by stating made-up facts, Google also has a separate legal removal request form.
Other review platforms run their own processes. A common one: you state that there was no customer contact, and the platform asks the author to substantiate it (say, with an order reference). In Germany, the Federal Court of Justice has held that such an objection is generally enough to trigger the platform’s duty to investigate. Escalate with a lawyer’s letter only when the obvious cases stall.
The trap almost everyone walks into: replying to a suspected fake review with the standard “we’re sorry about your experience”, because that reply can be read as confirming a customer relationship existed, which is exactly the question the takedown procedure turns on. Suspected fake → report first, reply never (or only after removal fails, and then in bucket-2 style).
What you cannot get removed: harsh but genuine opinions. “Overpriced and the packaging felt cheap” from a real buyer is a protected opinion: bucket 1, answer it well.
And the other direction is just as regulated. Under EU consumer law, submitting or commissioning fake reviews is banned outright. If you display reviews, you must tell customers whether and how you make sure they come from people who actually bought or used the product, and you may not claim they do without reasonable checks. Inviting only happy customers to review (“review gating”) or offering discounts for reviews is explicitly prohibited by Google’s policies.
Prevention: reviews are a lagging indicator of your support
The review section is where unresolved tickets go to become permanent. Which means the review strategy with the highest leverage isn’t on the review platform at all:
- First reply time. The window between “customer is annoyed” and “customer is publicly annoyed” is usually a day or two. Standard cases answered in minutes, nights and weekends included, never reach the review form. One of our beta brands cut weekend first replies from over 12 hours to under 5 minutes; their reviews stopped mentioning “no answer” within a quarter (how). With Sondercase these replies can run fully automatically; refunds, cancellations, address changes and returns come fully prepared and go out with one click (automated customer service).
- Resolve before you ask. Send review invitations after the case is closed and the parcel delivered, not on payment. Timing the ask this way is the legitimate version of shaping your rating.
- Mine the one-star column monthly. Recurring themes (a SKU, a carrier, a policy) are the same feedback loop as structured return reasons: free product research, already written down.
The pattern by now is familiar: the public-facing problem (a bad rating) is downstream of a process problem (slow, manual case handling): the same economics as everywhere in post-purchase. Fix the process, and the reviews follow.