The Social Clinic All articles
Treatment Plans

Seventy-Two Hours to Contain It: A Field Manual for the Post That Won't Stop Spreading

The Social Clinic
Seventy-Two Hours to Contain It: A Field Manual for the Post That Won't Stop Spreading

Photo: Acabashi, CC BY-SA 4.0, via Wikimedia Commons

Every brand that has ever had a bad post go wide has felt the same urge in the same two minutes: delete it, pretend it never happened, hope the internet has a short memory.

It doesn't. The screenshot already exists. Someone has already quoted it. And deleting doesn't remove the post so much as remove your side of the story, which is the only part you control.

The instinct is right, though, in one sense: you do need to isolate it. You just need to do that with a plan rather than a panic.

Hour 0 to 6: isolate the strain

Before you touch anything, work out what you're dealing with. There are roughly five strains, and they need different treatment.

Don't delete in the first six hours. There are narrow exceptions — personal data exposed, harassment, copyright, anything that could cause real harm — and if one of those applies, remove it and say why in the same breath. Otherwise, deleting now just makes you the story.

What you do instead is gather evidence. Screenshots with timestamps, the post's metrics, a sample of the comments, who's amplifying it and whether they're a customer, a competitor or a passer-by. Save it somewhere the whole team can see. You'll need it for the post-mortem and for the statement.

Then appoint one incident lead. One person who decides, one person who posts. Two people deciding in a group chat at 11pm is how brands end up with three different positions in four hours.

Hour 6 to 18: contain the outbreak

Containment is mostly about stopping the spread you're still causing yourself.

Pause scheduled content for 24 hours. Not forever, and you don't have to announce it — just don't let a chirpy product post land in the middle of a backlash. Pause paid spend, and specifically check whether the offending post is being boosted anywhere. Nothing extends a crisis quite like paying to put it in front of more people.

Brief whoever handles your comments and DMs. Give them a short script, a line they can use, and a clear escalation route for anything legal, threatening or press-related. Don't let them improvise an apology.

Resist muting comments as a first move. On most platforms it reads as a confession and generates a second wave of screenshots. It's a last resort for abuse and illegal content, not a way to avoid a difficult Tuesday.

Hour 18 to 36: the statement

By now you know the strain and the scale. If it's still climbing, you need to say something.

Four parts, in this order: what happened, what we got wrong, what we're doing about it, when we'll update you. That last one matters more than people think. Giving a date turns an open wound into a process.

What to leave out: 'we hear you', 'we're sorry if anyone was offended', blaming an intern or an agency, emoji, and anything longer than about 120 words. UK audiences are attuned to corporate fog. Plain English reads as accountability; polished language reads as legal review.

If the mistake was factual, correct the fact first and apologise second. If it was tonal, name the tone you got wrong. If it was a joke that landed badly, don't explain why it was funny.

Pin the statement. Post it on the platform where it happened, not just on a corporate news page nobody visits, and put it wherever your customer service team is answering questions.

Hour 36 to 72: recovery

The temptation now is to go quiet for a fortnight. Don't. Silence after a statement reads as hiding, and it hands the narrative to whoever's still annoyed.

Return to normal service, slightly softer. Keep posting the useful stuff. Reply to individuals rather than broadcasting at them — a direct, specific answer to a specific complaint does more for sentiment than any pinned paragraph.

Watch it by reading, not by refreshing a sentiment dashboard. Dashboards lag, and they can't tell the difference between anger and people quoting your apology approvingly.

When to hold the line

Not every pile-on deserves an apology. If you posted something accurate and the backlash is built on a misreading, a holding statement plus the evidence is stronger than a grovelling retraction you don't mean. Say what you meant, show your working, stay polite, and don't argue in the replies at midnight.

Anonymised examples from UK campaigns

A regional food brand we worked alongside replied to criticism of a seasonal campaign with a joke in the comments at hour two. It doubled the reach of the original complaint and turned a small grumble into a two-day story. The post was fine. The reply was the incident.

A consumer app, by contrast, paused all paid activity for 48 hours and published a five-line statement with a date for an update. The reply quoting was largely positive, because the brand had visibly done something rather than felt something.

The flow, in plain order

Is it illegal or harmful? Remove it and explain. Is it factually wrong? Correct it publicly. Is it a tone problem that's growing? Statement within 24 hours. Is it a small grumble? Reply properly, once, and move on. Is it a misinformed pile-on? Hold the line with evidence.

After the 72 hours: the follow-up appointment

Book the post-mortem within seven days, while memories are accurate. What triggered it, what would have caught it pre-publication, and which line of the sign-off process failed. Update the pre-op checklist. Adjust your escalation thresholds. Brief the team that wasn't in the room.

Most viral misfires burn out inside three days. What survives longer than that isn't the post. It's how you behaved while it was happening.

All Articles

Related Articles

The Scan Doesn't Lie: What Reading Six Rival Accounts Like an X-Ray Told Us About Our Own Brand

The Scan Doesn't Lie: What Reading Six Rival Accounts Like an X-Ray Told Us About Our Own Brand

Algorithm Flu Comes Every Season. Most Brands Still Haven't Built an Immune System

Algorithm Flu Comes Every Season. Most Brands Still Haven't Built an Immune System

Overheard in the Waiting Room: Why Your Customers' Group Chats Know More Than Your Analytics Dashboard

Overheard in the Waiting Room: Why Your Customers' Group Chats Know More Than Your Analytics Dashboard