A Negative Online Review Goes Up: Decision Tree

Why this matters

Someone on the team just spotted a fresh one-star review, and the next hour of internal handling matters as much as whatever gets typed in the public reply. A review handled by whoever happens to see it first, replied to in anger, or left sitting for a week because nobody owns it, turns a single bad review into a bigger problem than the original complaint. This tree is the internal triage the moment a review appears, before you write a word of the public response, so the right person handles it, at the right speed, with the facts in hand.

Start here: who saw it, and who owns it now

The instant someone notices the review, the first decision is not what to say back, it is who is now responsible for the response.

• Route it to one owner immediately, whoever handles reviews and complaints at your shop, rather than letting whoever saw it first fire off a reply. A review answered by an emotional tech who feels personally accused often does more damage than the review itself.
• Do not reply within the first few minutes, even to acknowledge it, unless your process specifically calls for an instant holding reply. A same-minute response written in the heat of just seeing it is rarely your best one. A same-day or next-day considered reply beats a fast angry one.
• Screenshot it now. Reviews get edited or removed by the platform or the reviewer, and you want a record of exactly what was posted.

Step 1: identify the job and pull the facts

Before deciding anything about tone or remedy, find out what actually happened.

• Search your records for the name, address, or date mentioned. If you cannot find a matching job at all, that changes the whole path, see the branch below.
• Talk to whoever did the work. Get their account of what happened, not just the review's account. Two sides of the same event are normal, not a sign someone is lying.
• Check for any prior contact. Did this customer already call or email a complaint that never got resolved? A review is sometimes the second attempt after a first one went nowhere internally, which is itself a process gap worth fixing.

Branch 1: you cannot find a matching customer or job

If nothing in your records matches the reviewer's name, address, or described service, treat this as a possible mistaken-identity post or a fake review before assuming it is a real customer you failed.

• Do not accuse anyone publicly of being fake. Reply briefly and politely that you have no record of the visit and would welcome a chance to help if there has been a mix-up.
• Flag it through the review platform's official reporting channel if it appears to violate policy, off-topic, wrong business, abusive content. Removal is not guaranteed and can take time.
• See related: The Fake or Unfair Review Decision Tree for the full path once you have gotten this far.

Branch 2: it is a real customer with a legitimate complaint

This is the most common outcome. The facts confirm the customer had a real, valid reason to be unhappy.

• Resolve it privately first, if you have not already. Call the customer directly, separate from the public reply, and actually fix what went wrong.
• Draft the public reply only after the private outreach is in motion, not before. A public apology with no attempt to actually contact the person reads as performance.
• Keep the public reply short, specific, and off the details. See related: Responding to a Bad Review Without Sounding Defensive for the language itself.

Branch 3: it is a real customer, but the complaint is exaggerated or one-sided

The visit happened, but the account leaves out context, a decision the customer made, a scope they agreed to, a factor outside your control.

• Do not correct the record aggressively in public. State the shared facts calmly if a correction is needed, and still offer to resolve it offline.
• Resist the urge to "win" the story publicly. The audience reading later cares more about your composure than about who was more right.

Branch 4: the review is abusive, contains a threat, or is clearly a policy violation

Profanity, personal threats, or content unrelated to any actual service.

• Do not engage with the content itself in public. Report it through the platform's abuse-reporting channel.
• Post a brief, calm holding reply if the platform allows it, without matching the tone, while the report is pending.

What happens after the internal triage, regardless of branch

Once you know who owns it, what happened, and which branch applies, the remaining work is the public reply itself and the private resolution. Those are separate skills covered elsewhere. This tree exists because most damage from a bad review happens in the first hour, before anyone has actually checked the facts, and it happens internally, not in the public comment thread.

What never to do in the first hour

• Do not let the person named in the review write the public reply about themselves.
• Do not let the review sit unassigned for days assuming someone else will handle it.
• Do not discuss the specific customer by name in any internal channel visible outside the team, and do not screenshot-share it casually where it could leak.
• Do not decide on a comp or remedy before you have actually verified what happened.

References

• Trade-standard practice for online reputation management and complaint triage.
• Federal Trade Commission guidance on responding to consumer reviews.
• See related: The Fake or Unfair Review Decision Tree; Responding to a Bad Review Without Sounding Defensive.