Social media crisis response process flowchart (detect to review)
Social media crisis response template: spike detection, triage into complaint, customer care or reputational threat, severity, a pause-scheduled-content gate, timed holding statement and approvals, and review.
What the social media crisis response process flowchart (detect to review) process is
Crises on social channels move faster than the approval chains built for ordinary posts. This chart is the escalation path for the minutes after a spike: capture the evidence, then answer 'What kind of issue is it?' with Isolated complaint, Needs customer care or Reputational threat. Only the last one wakes the incident machinery, so a single angry customer gets a reply or a private hand-off and the executive sponsor is left alone. For the complaint itself, see /templates/customer-complaint-process; if the cause is an outage or a failure, run /templates/incident-management-process at the same time.
What makes this different from the routine approval chart at /templates/social-media-approval-process is the structure. It is a decision tree with time boxes. A holding statement goes out first and the full response follows only after 'Does legal clear the draft in time?' and 'Executive sponsor approves?', each with a limit. If the limit passes the chart does not wait in silence: a 'Time box missed' exception extends the holding line and escalates. The time boxes in the chart, like the severity levels, are placeholders to adapt to your own team and counsel.
One gate matters more than it looks: 'Pause all scheduled content?'. A scheduled promotion landing in the middle of a crisis reads as tone-deaf, and nobody thinks to pull it unless the process asks. The chart makes the pause a deliberate decision with a named owner, then closes with a stand-down decision, 'Stand down the response?', and a post-incident review that updates the playbook. Not legal advice; check your jurisdiction and counsel for what may be said and when.
What this flowchart covers
In this template
- Five swimlanes (Community manager, Social lead, Comms / PR lead, Legal and Executive sponsor) across five phases: Detect, Triage, Contain, Respond and Recover
- A triage decision, "What kind of issue is it?", with three exits so that complaints and care cases leave the crisis route early
- A severity gate, "Severity 1: legal, safety or press involved?", that adds legal and the executive sponsor only when it matters
- A pause gate, "Pause all scheduled content?", with Pause all and Keep running branches
- A timed approval chain: "Does legal clear the draft in time?" and "Executive sponsor approves?", with a "Time box runs out: extend holding line, escalate" exception
- Recovery: monitor sentiment, "Stand down the response?" with a Keep monitoring loop, and a post-incident review
When to use this template
- Your last bad week on social was handled in a group chat and nobody can say who owned it
- Scheduled posts kept going out during a sensitive moment because no one had the job of pausing them
- Legal and executives are pulled into every complaint, or into none until it is too late
- You need a written escalation path for a lender, insurer, board or client questionnaire
- Post-incident reviews happen inconsistently and the same mistakes repeat
How it works
Rename the lanes
Replace Community manager, Social lead, Comms / PR lead, Legal and Executive sponsor with your roles, including your agency if it runs the channels out of hours.
Define the three triage outcomes
Write what counts as an isolated complaint, a care case and a reputational threat, with examples. Name who decides at the first decision and who they can wake.
Write your severity levels
Choose two or three levels and the facts that set each one, such as legal exposure, safety or press interest. Name the incident owner who is assigned at each level.
Set the pause rule
Say who may freeze the publishing queue, which channels it covers and who lifts the freeze. Put a backup name against it.
Fix the time boxes
Add the minutes allowed for the holding statement, legal review and executive approval. The numbers on the chart are placeholders; use what your team can meet at 2am.
Pre-approve holding lines
Draft holding statements for your likely scenarios and agree with counsel what may be said without further sign-off.
Rehearse and review
Run the chart as a tabletop exercise, then after each real incident record what was slow and update the stand-down test and playbook.
Frequently asked questions
What are the steps in a social media crisis response?
Detect and capture evidence, triage the issue, assign severity and an owner, decide whether to pause scheduled content, publish a holding statement, draft and clear the full response with legal and an executive, publish it, monitor sentiment, decide when to stand down and run a post-incident review.
When should we pause scheduled social media posts?
When a scheduled post could look insensitive or misleading next to the unfolding issue. The chart makes this an explicit decision once an issue is rated a reputational threat, with a named person who can freeze the queue and lift the freeze. Pausing is reversible, so it is generally cheaper to pause than to apologise for a post that ran.
What is a holding statement?
A short public message that acknowledges the issue, says you are looking into it and promises an update. It buys time for the full response without silence. Agree wording in advance with counsel; this template cannot say what is safe in your jurisdiction.
How is this different from the incident management process?
The incident management chart at /templates/incident-management-process is about fixing the underlying failure. This chart is about the public conversation around it. For a real outage you run both, with the incident owner feeding facts to the comms lead.
Where this process fits
In most operations this process follows Social media approval process flowchart (calendar to publish).
Comes before
- Social media approval process flowchart (calendar to publish) — Social media approval process template: calendar slot, draft post, risk tiering so routine posts skip legal, tiered review, scheduling, an urgent fast lane with after-the-fact review, and comment hand-off.