The First Response to a Bad Review SOP

Purpose

A standard operating procedure (SOP) is the written, repeatable process every person follows the same way, so a bad review gets a calm, consistent response instead of whatever the first person to see it fires off angry. A negative review is read by every future customer weighing your shop, and the response matters more than the review itself, because prospects judge how you handle a complaint far more than the fact that you got one. This SOP is the workflow for the first response: who gets told, how you cool off, the facts you gather before typing a word, who drafts and who approves, and the offline recovery you attempt in parallel. It is the process, not the wording craft, which lives in its own article.

Scope

Applies to any public negative review across platforms. Covers detection, internal notification, fact-gathering, drafting and approval, posting, and the offline recovery attempt. Deciding whether a specific review is even worth engaging, and the exact language of a public reply, are covered in related articles; this SOP is the standard intake-and-response process around them.

Roles and responsibilities

Procedure

1. Do not reply in the moment, log and notify

The first rule is a hard stop: nobody fires back a reply the minute they see it. An emotional, same-minute response is the one that goes viral for the wrong reason and cannot be taken back. Whoever spots the review logs it and notifies the reputation owner. The response is a process starting, not a reflex.

2. Cool off before anything gets written

Build in a deliberate pause before drafting. A short cooling-off period, hours, not the instant, takes the heat out of the reply and is almost always long enough; a review that sat up for a day is not made worse by a few more hours of a measured response. Nothing about a bad review is so urgent that a rushed, defensive reply beats a calm one.

3. Gather the facts internally first

Before drafting, pull what actually happened: find the job, read the notes, talk to the tech who was there. You cannot respond well to a complaint you have not verified. Sometimes the review is accurate and you owe a real fix; sometimes it is distorted or not even your customer. Either way, the facts shape the response, and guessing in public is how you make a false statement you have to walk back.

4. Match the response to what the facts show

Sort what you found: a legitimate complaint, a misunderstanding, or a fake or fraudulent review. A real complaint gets an accountable, non-defensive reply and a genuine effort to fix it. A misunderstanding gets a calm clarification. A fake review that violates the platform's policy gets reported for removal through the platform, in parallel with, or instead of, a reply. Do not treat all three the same.

5. Draft the public reply and route it for approval

The reputation owner drafts the reply; the owner or manager approves it before it posts. The reply stays short, professional, never argues the specifics in public, never exposes the customer's private details, and points the conversation offline. A second set of eyes before posting catches the defensive sentence the drafter could not see in their own writing. The wording craft is covered in the related how-to.

6. Attempt offline recovery in parallel

The public reply is not the real fix; it is a signal to onlookers. The actual repair happens offline: call or message the customer directly to understand and make it right. A public "we would like to make this right, please call us" backed by a real call that resolves the issue is what sometimes turns a one-star into an updated review, and always shows every future reader that you engage.

7. Close the loop and note the pattern

After the response and any recovery, record the outcome. If the same complaint keeps appearing across reviews, the reviews are a symptom and the real fix is a process change, not a better reply. One bad review is noise; the same bad review three times is data telling you where the shop actually leaks.

Watch out for

• Replying in the heat of the minute. The impulse reply is the one that makes it worse; log and pause.
• Responding before verifying the facts. Guessing in public creates a statement you have to retract.
• Posting without a second reader. The defensive line is invisible to its own author.
• Treating the public reply as the fix. The repair happens offline; the reply just shows you tried.

References

• Major review platform policies on responding to and reporting reviews
• See related: Writing a Review Response That Sounds Human; Responding to a Bad Review Decision Tree; The Customer Review Request SOP
• Trade-standard practice for reputation management