Who should reply to a negative review: the owner, support, or whoever can fix it?
One consistent person should write the public reply, usually the owner in a small business or a named support lead, but the facts in it should come from whoever can fix the cause. A reply that says what went wrong and what has changed needs input from product or operations; a reply from someone who cannot promise anything reads like a template. Decide in advance who replies, who supplies the facts, and which reviews wait for escalation.
What this comes down to
- One consistent voice should write public replies, while the facts in each reply come from the person who can fix the cause.
- A reply is only as good as what it can truthfully promise, so defect and delivery complaints need facts before an answer.
- Some reviews should not get a quick public reply, such as a safety claim that has to be investigated first.
- Writing the routing down once means replies no longer depend on who happened to see the review.
The short answer: one voice, several sources
Customers reading your replies should meet the same voice every time: same tone, same sign-off, same willingness to take responsibility. That argues for one writer.
But the writer rarely knows the facts. Was the zip faulty in one batch or all of them? Did the courier change last month? A reply that answers those questions needs someone from product or operations behind it. The job splits in two: writing and knowing.
The best reply is written by one person and informed by the person who can fix the problem.
Owner, support lead, or the person who can fix it
| Writer | Strength | Risk |
|---|---|---|
| Owner | Can promise changes; replies carry weight | Little time; takes criticism personally |
| Support lead | Consistent, fast, practised in tone | May not know the cause or be able to commit to a fix |
| Person who can fix it | Knows the facts | Not practised at public writing; replies get technical or defensive |
Route by what went wrong
The writer stays the same. The source of facts changes with the complaint:
- Defect or quality. Ask product or sourcing: is this known, and what has changed?
- Delivery, damage, wrong item. Ask operations: what happened with this order, and is it a pattern?
- Confusion or setup. Support can answer directly, and should update the help article or listing that caused it.
- Abuse or a review about something else entirely. Use the platform’s own reporting route rather than arguing in public.
Working out which team a complaint belongs to is covered in whose fault is a negative review.
The reviews that wait for escalation
A review that alleges injury, a health reaction, fraud, or threatens legal action should go to whoever handles those matters before anyone replies. A fast, friendly reply can accidentally concede something that has not been established.
Those are the reviews a severity label exists to catch. Pull them out daily; everything else can wait for the normal reply queue.
Three rules whoever replies has to know
Handing replies to one person also means one person has to know the rules. Three matter more than tone:
- No incentive tied to the review. The FTC’s Consumer Reviews and Testimonials Rule, in force since 21 October 2024, bans incentives that depend on a review’s sentiment. A refund or voucher offered in return for changing or removing the review crosses that line. Offer the fix because the complaint deserves it.
- No suppression. The same rule bans suppressing negative reviews. Reporting a review that breaks a platform’s rules is fine; threatening or intimidating a customer into taking down an honest one is not.
- No personal data in public. Order numbers, addresses and full names stay out of the reply, even when the reviewer included them. Move the details to email.
Write the routing down once
Five lines are enough. For example:
- Replies are written by the support lead and signed with the store name.
- Defect complaints: ask product for the facts within two working days.
- Delivery complaints: ask operations for the order history first.
- High severity: owner decides before any reply goes out.
- Abusive or irrelevant: report through the platform, no reply.
Once the routing exists, the Review Analyzer’s topic and severity labels tell you which line applies to each review, and its needs-a-reply flag builds the queue.
Questions
Should the business owner respond to negative reviews?
In a small business it often works well, because the owner can promise changes. The risk is time and temper. Many shops have a support lead write the replies and bring in the owner only for high-severity cases.
Should we use the same reply for every negative review?
No. Identical replies tell future customers that nobody read the review. Keep a structure (thank, acknowledge the specific problem, say what changed or what to do next), but write the words for each review.
Should a developer reply to app store reviews about bugs?
The developer should supply the facts, such as which version fixes the bug. Whoever writes the app’s other replies can then turn that into a short, plain answer.
Read next
Who is a review reply for? The reviewer, and every shopper after them
A public reply is read by every later shopper, not just the reviewer. What each audience needs, a four-line reply shape, and what reads badly in public.
When to respond to a negative review, and which ones should wait
Reply once you know the facts, usually within a working day or two. Which reviews wait for escalation first, and the timing mistakes that cost you trust.
Whose fault is a negative review? Ask who can fix the cause instead
To the customer it is always the seller’s problem. Inside the business, route each negative review to the owner who can fix its cause, without blame.