Crisis Communication Plan Builder
Build a comprehensive crisis communication plan with pre-written holding statements, stakeholder messaging matrices, escalation protocols, and social media response frameworks for any business emergency.
Prompt Template
You are a crisis communication strategist who has managed PR crises for Fortune 500 companies, startups, and public-facing brands. Build a comprehensive crisis communication plan for my organization. **Organization:** [company name, industry, size] **Public Presence:** [B2B / B2C / both] — [social media following, customer base size] **Key Stakeholders:** [customers, employees, investors, regulators, media, partners — list all relevant] **Past Crises (if any):** [describe any previous incidents and how they were handled] **Most Likely Crisis Scenarios:** [select or describe] - [ ] Data breach / security incident - [ ] Product failure / recall - [ ] Negative press / viral social media backlash - [ ] Employee misconduct / leadership scandal - [ ] Service outage / operational failure - [ ] Legal / regulatory action - [ ] Financial / layoffs / restructuring - [ ] Customer harm / safety issue - [ ] Other: [describe] **Spokesperson(s):** [who speaks for the company — CEO, Head of Comms, etc.] **Existing Comms Infrastructure:** [PR agency, in-house comms team, nothing formal] Please create: 1. **Crisis Classification Framework** — Severity levels (Level 1-3) with clear criteria for escalation, defining who is notified and what response speed is required for each level 2. **Pre-Written Holding Statements** — For each crisis scenario selected, provide: - Initial holding statement (within 1 hour of discovery) - Detailed follow-up statement (within 24 hours) - Resolution statement (when crisis is contained) Each with [fill-in-the-blank] sections for specific details 3. **Stakeholder Messaging Matrix** — For each stakeholder group, define: - Key message (what they need to hear) - Channel (email, press release, social media, 1:1 call, all-hands) - Timing (when they should be notified, in what order) - Tone (empathetic, factual, reassuring, transparent) 4. **Social Media Response Protocol** — How to handle real-time social media crises: - Monitoring and detection triggers - Response templates for different sentiment levels - When to respond publicly vs. take it to DM - When to go silent vs. stay visible 5. **Internal Communication Plan** — Employee communication during a crisis: - What employees should know first - What they should say if asked by media/customers - FAQ document template 6. **Crisis War Room Setup** — Who's in the room, roles, decision authority, communication cadence 7. **Post-Crisis Playbook** — After the crisis, how to: - Conduct a blameless post-mortem - Rebuild trust with affected stakeholders - Update the plan based on lessons learned - Monitor for reputation recovery
Example Output
# Crisis Communication Plan: CloudSync SaaS (B2B, 5,000 customers)
1. Crisis Classification Framework
| Level | Description | Examples | Response Time | Who's Notified |
|-------|------------|----------|---------------|----------------|
| **Level 1 — Critical** | Immediate threat to business operations, safety, or legal standing | Data breach with customer PII exposed, service outage >4 hours, regulatory investigation | **1 hour** | CEO, Legal, Head of Engineering, Head of Comms, Board (if public) |
| **Level 2 — Major** | Significant reputational risk or operational disruption | Viral negative social media, major bug affecting subset of customers, employee misconduct news | **4 hours** | CEO, Head of Comms, relevant department head |
| **Level 3 — Minor** | Contained issue with limited exposure | Isolated customer complaint going semi-viral, minor service degradation, industry-wide issue | **24 hours** | Head of Comms, Customer Success lead |
2. Pre-Written Holding Statements
Scenario: Data Breach / Security Incident
Initial Holding Statement (within 1 hour):
> We are aware of a security incident affecting [description of what was affected]. We are actively investigating the scope and impact with our security team and [external forensics firm if applicable].
>
> The security of our customers' data is our highest priority. As a precaution, we have [immediate action taken — e.g., rotated credentials, isolated affected systems].
>
> We will provide an update within [timeframe — 4/8/12 hours] with more details. If you have concerns, contact our dedicated support line at [number/email].
24-Hour Follow-Up Statement:
> **Update on Security Incident — [Date]**
>
> Here's what we know:
> - **What happened:** [factual description of the incident]
> - **What data was affected:** [specific data types — names, emails, payment info, etc.]
> - **Who is affected:** [number of users/accounts impacted]
> - **What we've done:** [remediation steps taken]
> - **What you should do:** [specific actions for affected users — change passwords, monitor accounts, etc.]
>
> We take full responsibility for this incident. [Name], our [CEO/CTO], is personally overseeing the response.
>
> **Next steps:** [what happens next — ongoing investigation, credit monitoring offered, third-party audit]
>
> We'll continue to provide updates at [URL of status page/blog post].
3. Stakeholder Messaging Matrix — Data Breach
| Stakeholder | Key Message | Channel | Timing | Tone |
|-------------|------------|---------|--------|------|
| **Affected customers** | Your data may be affected. Here's what happened and what to do. | Email (direct) + in-app banner | First (within 2 hours) | Empathetic, transparent, action-oriented |
| **All customers** | We had an incident. Here's what we know and what we're doing. | Email + blog post | Second (within 4 hours) | Reassuring, factual |
| **Employees** | Here's what happened, what we're doing, and what to say if asked. | All-hands Slack + emergency meeting | Within 2 hours (parallel to customers) | Honest, calm, directive |
| **Investors/Board** | Incident details, business impact assessment, remediation plan. | Direct call from CEO | Within 1 hour of discovery | Factual, strategic, with action plan |
| **Media** | Official statement only. No speculation. | Press release + prepared spokesperson | Reactive (when asked) or proactive if story is breaking | Professional, accountable, concise |
| **Partners/integrations** | Impact on shared systems, any actions they need to take. | Direct email from partnerships lead | Within 4 hours | Technical, collaborative |
4. Social Media Response Protocol
Detection Triggers
- Brand mentions spike >300% above baseline
- Negative sentiment ratio exceeds 40% of mentions
- Any mention by media outlet or influencer with >10K followers
- Customer screenshot of incident goes viral (>500 shares)
Response Framework
| Sentiment Level | Response | Example |
|----------------|----------|---------|
| **Angry customer (individual)** | Acknowledge publicly, move to DM | "We hear you, [name]. This isn't the experience you should have. Let's fix this — DMing you now." |
| **Growing thread (5-20 mentions)** | Public acknowledgment with link to statement | "We're aware of the issue and actively working on it. Details and updates here: [link]" |
| **Viral (100+ mentions)** | CEO/founder posts personal statement | "I'm [name], CEO of CloudSync. Here's what's happening and what we're doing about it..." |
| **Media picking up** | Refer to official statement. No ad-lib. | "We've published a full statement here: [link]. We'll continue to provide updates." |
Golden Rules
- Never delete complaints (screenshots exist forever)
- Never argue or get defensive
- Respond within 30 minutes during active crises
- One voice: all social responses go through the designated comms person
6. Crisis War Room
Core Team (always present):
- CEO — Final decision authority
- Head of Comms — Message approval, media
- Legal — Liability review of all statements
- Head of Engineering (for technical crises) — Facts and timelines
Cadence:
- Level 1: War room meets every 2 hours until resolved
- Level 2: Daily standup until resolved
- Level 3: Async updates in dedicated Slack channel
7. Post-Crisis Playbook
**Within 1 week:** Blameless post-mortem
- What happened (timeline)
- What went well in our response
- What went poorly
- What we'll change
**Within 2 weeks:** Publish a public post-mortem (for technical incidents) or a "what we've learned" update (for other crises)
**Within 30 days:** Update this crisis plan based on lessons learned
**Ongoing:** Monitor brand sentiment weekly for 90 days to track reputation recovery
Tips for Best Results
- 💡Write your holding statements BEFORE a crisis happens. Under stress, you won't write clearly — having pre-approved templates saves critical hours when every minute matters.
- 💡The first 60 minutes define the narrative. If you don't fill the information vacuum, speculation and misinformation will. Even saying 'we're investigating' is better than silence.
- 💡Always communicate to employees BEFORE or simultaneously with external audiences. Nothing destroys trust faster than employees learning about a crisis from Twitter instead of leadership.
- 💡After the crisis, publish a transparent post-mortem. Companies that own mistakes publicly (Cloudflare, GitLab) actually build MORE trust than they had before the incident.
Frequently Asked Questions
What is the Crisis Communication Plan Builder prompt?
Build a comprehensive crisis communication plan with pre-written holding statements, stakeholder messaging matrices, escalation protocols, and social media response frameworks for any business emergency. It's a free ChatGPT prompt template from our Business collection — copy it, fill in the bracketed variables, and paste it into your AI tool.
Which AI tools work with this prompt?
It's written and tested for ChatGPT, Claude and Gemini. Any AI assistant that accepts free-form text prompts will handle it well.
How do I customize this ChatGPT prompt?
Replace the bracketed variables — such as [company name, industry, size], [B2B / B2C / both], [select or describe] — with your own details before running it. Write your holding statements BEFORE a crisis happens. Under stress, you won't write clearly — having pre-approved templates saves critical hours when every minute matters.
Is this prompt free to use?
Yes. Every prompt on PromptAtlas is free to copy, customize, and use — no signup required.
Related Prompts
One-Page Business Plan
Generate a concise, investor-ready one-page business plan covering all critical aspects of your venture.
SWOT Analysis Framework
Conduct a thorough SWOT analysis with actionable strategies derived from each quadrant.
Customer Persona Builder
Create detailed, research-backed customer personas that drive product and marketing decisions.