What is a holding statement?

A holding statement is a short, pre-approved message posted quickly to acknowledge an issue while you gather facts. It shows you are aware and taking it seriously, buying time without committing to details you can't yet confirm.

How should crisis severity be graded?

Common practice uses three tiers: low for isolated complaints handled by community managers, medium for spreading negative sentiment needing a coordinated reply, and high for issues threatening safety, legal exposure, or major reputation damage that require leadership.

Why have a fixed approval chain?

In a fast-moving crisis, ambiguity about who can approve a public statement causes dangerous delays. A pre-agreed chain — who drafts, who approves, who posts at each severity — lets the team respond in minutes, not hours.

What are the key do's and don'ts?

Do respond fast, stay factual, show empathy, and move detailed discussion to private channels. Don't delete critical comments, argue publicly, speculate, or go silent. Silence and defensiveness almost always make a crisis worse.

Should responses differ by platform?

Yes. A measured public X reply differs from a longer LinkedIn statement or a fast, empathetic Instagram comment reply. The plan captures platform-specific guidance so the team's tone and format fit each channel.

What is the Social Media Crisis Response Plan Builder?

Creates a social media crisis comms plan with trigger scenarios graded by severity, ready-to-edit holding statement templates, an approval chain, do's and don'ts, and platform-specific response guidance. It runs free in your browser on Gera Tools, with nothing uploaded.

Social Media Crisis Response Plan Builder

Name: Social Media Crisis Response Plan Builder
Creator: Gera Tools
License: https://creativecommons.org/licenses/by/4.0/

Get one useful tool a week

Like this tool? Enter your email and we'll send you one genuinely useful Gera tool a week — plus a link to come back to this one. No spam, one-click unsubscribe any time.

A crisis plan ready before you need it

The worst time to write a crisis response is during the crisis. This builder produces a ready-to-use plan: severity-graded triggers, editable holding statements, a clear approval chain, do’s and don’ts, and platform-specific guidance — so when something breaks, the team acts in minutes instead of arguing about who decides.

How it works

The plan grades incidents into three severity tiers so the team responds proportionately: low-severity issues are handled by community managers, medium-severity issues trigger a coordinated reply, and high-severity issues escalate to leadership. For each tier you have a holding statement — a short, pre-approved acknowledgement that buys time while facts are confirmed — and a named approver, removing the delay that ambiguity causes. The do’s and don’ts encode hard-won rules like respond fast, stay factual, never delete critical comments, and never go silent. Platform notes adapt tone and format per channel. The whole plan renders for copy into your runbook.

Why speed-to-first-response matters so much

The first 30 to 60 minutes of a public social media crisis are disproportionately important. A credible holding statement posted within that window tells the audience you are aware and taking it seriously, buying you time while you establish the facts. Without it, the narrative fills itself — often with speculation or the framing of whoever posted the original complaint. Teams that go silent, even for two hours, regularly find the story has moved far beyond the original trigger.

Worked scenario

Suppose a customer screenshots a product defect and it spreads on X to several thousand impressions before your team notices. This is a medium-severity trigger: real negative sentiment, spreading, but no safety risk.

Your medium-severity holding statement from the plan might read: “We’ve seen your messages and we’re looking into this now. Thank you for flagging it — we’ll have an update shortly.” That gets posted within 20 minutes while the social lead contacts the product team and the named approver reviews the factual statement. Meanwhile the platform note reminds the on-call team not to get drawn into individual reply arguments publicly — move detailed troubleshooting to DMs.

Operational tips

Pre-approve the holding statements now, while no one is under pressure — that is the entire point. Under pressure, every word feels uncertain.
Make the approval chain a single name per tier, with a named backup. A chain like “the CEO, the CMO, or the head of comms” is a guarantee of delay.
Rehearse a mock high-severity incident once or twice a year. Plans that are never tested fail in the ways the drill would have caught.
Store the plan somewhere the on-call team can access in seconds — a pinned Slack message or a bookmark, not a shared drive three folders deep.
Review and update it after any real incident. What the team actually said is better guidance for next time than the original template.