reaperinvest Crisis Communications Planner
When to Use This Skill
- Negative review or social media post going viral
- Product defect, service outage, or delivery failure
- Employee misconduct or internal issue becoming public
- Data breach or security incident
- Proactively building a crisis response plan before anything happens
Core Principle
IN A CRISIS, SPEED AND HONESTY WIN. A fast, honest, imperfect response beats a slow, polished, defensive one every time.
Workflow
Step 1: Assess the Situation
Ask the user:
- What happened? (the factual situation)
- Who's affected? (customers, employees, public, partners)
- Is it still ongoing or resolved?
- What's the current public exposure? (contained, spreading, viral)
- What's been said publicly so far?
Minimum needed: question 1.
Step 2: Determine Crisis Level
| Level | Description | Response Time | Example |
|---|---|---|---|
| Level 1 | Minor complaint, limited exposure | 24 hours | Single bad review, minor product issue |
| Level 2 | Growing attention, multiple stakeholders | 4-8 hours | Social media thread gaining traction, service outage |
| Level 3 | Viral/media attention, significant impact | 1-2 hours | Data breach, major product recall, viral PR disaster |
Step 3: Draft Response Messages
For each stakeholder group, write:
- Public statement (social media, website) — Under 150 words
- Customer email — Personalized, empathetic, action-oriented
- Internal team message — Facts, talking points, what to say if asked
- Media statement (if needed) — Factual, no speculation
- Follow-up update — Sent when situation is resolved
The Response Formula:
- Acknowledge what happened (no minimizing)
- Express genuine empathy
- State what you're doing about it
- Commit to a follow-up timeline
Step 4: Build Escalation Protocol
Define who does what:
- First responder: Who drafts the initial response?
- Approval: Who approves before publishing?
- Monitor: Who tracks social media and press coverage?
- Follow-up: Who sends the resolution update?
Step 5: Post-Crisis Review
After resolution:
- What happened and why?
- How fast was the response?
- What worked and what didn't?
- What systems need to change to prevent recurrence?
Examples
Example 1: E-commerce Product Quality Issue
Situation: A batch of skincare products caused allergic reactions. 15 customers reported issues on social media.
Public Statement (Instagram + Twitter):
We've received reports that a recent batch of our Glow Serum caused skin reactions for some customers. We take this seriously.
We've immediately pulled the affected batch (Lot #2847) from our store. If you purchased Glow Serum in the last 30 days, please stop using it and check the lot number on the bottom of the bottle.
If you're affected: → Email care@brand.com for an immediate full refund → We'll cover any dermatologist visit costs
We're working with our manufacturer to identify the cause and will share a full update within 48 hours.
We're sorry. Your trust matters more than any product.
Customer Email to Affected Buyers:
Subject: Important safety notice about your recent Glow Serum order
Hi [Name],
We're reaching out because you recently purchased our Glow Serum, and we've identified a quality issue with a specific batch that may cause skin irritation.
Please stop using your Glow Serum and check the lot number on the bottom of the bottle. If it reads Lot #2847, please discard it.
Here's what we're doing for you:
- Full refund processed automatically — you'll see it in 3-5 business days
- Replacement product from a verified batch shipped free when available
- If you experienced any skin reaction, reply to this email and we'll cover your dermatologist visit
We're deeply sorry for this experience. We're investigating the cause with our manufacturer and will share a transparent update within 48 hours.
[Name], Founder
Example 2: Service Outage (SaaS)
Public Statement (Status Page + Twitter):
We're experiencing a service outage affecting all users. Our team identified the issue at 2:15 PM EST and is actively working on a fix.
Current status: Data is safe. No data loss has occurred. Estimated resolution: Within 2 hours. Next update: 4:00 PM EST.
We know you depend on us and we're sorry for the disruption. Updates will be posted here every 30 minutes.
Internal Team Message:
Team — we have a Level 2 outage. Here's what you need to know:
What happened: [Technical explanation] Customer impact: All users unable to access the platform since 2:15 PM EST ETA to fix: ~2 hours
If customers contact you:
- Acknowledge the outage and apologize
- Direct them to status.ourapp.com for live updates
- Do NOT speculate on the cause or give technical details
- Do NOT promise a specific resolution time beyond "within a few hours"
- Log every customer interaction for follow-up
Do not post on personal social media about this.
Recovery & Fallbacks
- User wants to ignore the crisis: This always makes it worse. Even a short acknowledgment is better than silence. Silence is interpreted as guilt or indifference.
- Legal concerns about admitting fault: Express empathy without legal admission: "We're sorry this happened" (not "We're sorry we caused this"). When in doubt, consult an attorney before publishing.
- Crisis is escalating faster than response prep: Post a brief holding statement: "We're aware of [issue] and are investigating. We'll share a full update within [timeframe]." This buys time without silence.
- User is emotional/angry: The response must be calm and empathetic regardless. Draft it, wait 15 minutes, re-read, then publish.
Constraints
- NEVER lie, minimize, or shift blame — honesty is the only viable crisis strategy
- NEVER delete negative comments unless they contain threats, slurs, or personal information
- Response must include a specific follow-up timeline ("within 48 hours" not "soon")
- Always separate what you know from what you're investigating
- Every public statement must include a way for affected people to reach you directly
- Internal messaging must include clear "what to say / what NOT to say" guidance