Crisis Communications
A Crisis Communications workspace for coordinating legal, PR, comms, customer success, and leadership during an active incident. It gives you a shared command center for decisions, approvals, customer updates, and post-incident follow-through.
Trusted by frontline teams 15 years of frontline software
Built for: Saas · Healthcare · Financial Services · E Commerce · Enterprise Technology
Overview
Crisis Communications is a team workspace template for incidents that require fast, coordinated messaging across Legal, PR/Comms, Customer Success, leadership, and the operational team handling the issue. It is built around a live situation-room channel, a decision-log, external-comms drafting, customer-success coordination, leadership updates, and a retrospective so the response stays organized from first confirmation through review.
Use this template when the incident has real external impact or reputational risk and you need a clear approval path for statements, customer guidance, and executive updates. The milestone flow helps the team move from incident confirmation to approved holding language, customer outreach, remediation ownership, and post-incident review. The task lists are stage-based, so the team can separate fact gathering from messaging, outreach, and follow-up work. The pinned resources keep the runbook, approval matrix, timeline log, and approved templates in one place.
Do not use this as a generic project workspace or for routine internal updates. If the issue does not require cross-functional approvals, customer communication, or a formal review, this structure is more than you need. It also should not replace your incident management system; it should sit alongside it as the communications layer. The template works best when each role has a clear DRI and the workspace mirrors the actual response structure, not the org chart in theory.
What's inside this template
Members
This section defines the response roles so every decision, draft, and follow-up has a clear owner.
Channels
These channels separate live coordination, approvals, customer support, leadership updates, and review work so the response stays organized.
-
situation-room
Primary channel for live incident updates, facts, timeline changes, and operational coordination.
-
decision-log
Channel for approvals, final decisions, message sign-off, and escalation outcomes.
-
external-comms
Drafting and review space for press statements, customer notices, social posts, and FAQ language.
-
customer-success
Channel for customer-facing impacts, account-level outreach, support scripts, and escalation handling.
-
leadership-updates
Briefings for executives and functional leads on status, risks, decisions needed, and next milestones.
-
retrospective
Post-incident review channel for lessons learned, follow-up actions, and process improvements.
Check ins
These check-ins set the cadence for crisis coordination and executive visibility when the situation is changing quickly.
- Daily crisis standup
- Weekly leadership update
Milestones
Milestones mark the major response phases so the team knows what has been confirmed, approved, published, and reviewed.
-
Incident confirmed and command structure established
Core team assembled, facts verified, and communication path defined.
-
Initial external statement approved
Holding statement or first public message cleared through the approval chain.
-
Customer outreach and support guidance published
Frontline teams have approved scripts and impacted customers have been contacted.
-
Remediation plan and follow-up owners assigned
Post-incident actions are documented with DRIs and due dates.
-
Post-incident review completed
Lessons learned captured and closure criteria confirmed.
Task lists
These task lists break the response into stage-based workstreams with a clear DRI for each phase.
-
Triage and Fact Gathering
Establish the incident scope, confirm facts, and identify immediate risks before external communication begins.
-
External Messaging and Approvals
Draft, review, and approve all outward-facing communications with a clear DRI and sign-off path.
-
Customer and Stakeholder Outreach
Coordinate proactive outreach to customers, partners, and internal stakeholders with consistent messaging.
-
Recovery and Follow-Up
Track remediation, post-incident actions, and the transition into the retrospective phase.
Default apps
These defaults connect the workspace to the tools used for drafting, tracking, and live coordination.
Integrations
These integrations keep incident facts, documents, action items, and meetings linked to the workspace.
- Slack
- Google Drive
- Jira
- Zoom
Pinned resources
These pinned resources give the team the approved language, runbook, timeline, and escalation contacts needed to respond consistently.
- Crisis Communications Runbook
- Approved Holding Statement Template
- Customer FAQ and Support Script Template
- Incident Timeline Log
- Approval Matrix and Escalation Contacts
How to use this template
- 1. Replace the placeholder members with the actual response roles, assign a DRI for each task list, and confirm who is Responsible, Accountable, Consulted, and Informed.
- 2. Open the situation-room channel for live fact gathering, then use the decision-log to record every approved statement, escalation, and material change in the incident narrative.
- 3. Populate the External Messaging and Approvals and Customer and Stakeholder Outreach task lists with concrete deliverables, owners, and due times tied to the current incident phase.
- 4. Post the approved holding statement, customer FAQ, incident timeline, and approval matrix in the pinned resources so everyone works from the same source of truth.
- 5. Run the Daily crisis standup to review new facts, blockers, and next actions, then use the Weekly leadership update to summarize impact, decisions, and remediation progress.
- 6. After the incident stabilizes, move remaining work into Recovery and Follow-Up, complete the retrospective, and assign owners for any open remediation or process changes.
Best practices
- Use roles instead of names for members so the workspace can be reused across incidents without rebuilding the structure.
- Keep the situation-room focused on facts, not messaging drafts, so the team can separate evidence from external wording.
- Log every approval in the decision-log with the approver, time, and version of the message to avoid conflicting statements later.
- Assign one DRI per task list so ownership is obvious when the response moves quickly across functions.
- Treat the approved holding statement as the default external position until Legal and Comms approve a fuller update.
- Mirror the real escalation path in the approval matrix, including backup approvers for nights, weekends, and holidays.
- Move customer-facing questions into the customer-success channel early so support teams do not improvise answers from memory.
- Close the loop on remediation by linking each follow-up item to a milestone, owner, and due date before the workspace is archived.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this Crisis Communications template for?
This template is for running a time-sensitive response when an incident is already underway, such as a data breach, executive departure, service outage, or public-facing failure. It gives the team one workspace for facts, approvals, external statements, customer guidance, and follow-up ownership. Use it to reduce confusion when multiple functions need to move in sync. It is not meant for routine project work or long-term planning.
Who should be in the workspace?
The workspace should be filled with roles, not individual names, so it can be cloned and reused across incidents. Typical members include Legal, PR/Comms, Customer Success, Engineering Lead, Support Lead, Executive Sponsor, and Incident Commander or DRI. Each role should have a clear responsibility in the response chain. If a role is not needed for a specific incident, leave it out rather than forcing a generic roster.
How often should the check-ins run?
The template includes a Daily crisis standup and a Weekly leadership update because crisis work needs both operational coordination and executive visibility. In the first phase of an incident, the daily standup is the main cadence for facts, decisions, and next actions. The weekly update is useful when the response extends beyond the first few days and leadership needs a stable summary. If the incident is severe, you can add ad hoc check-ins without changing the core structure.
What kinds of incidents fit this template?
This template fits incidents that require coordinated internal and external communication, especially when timing and approval flow matter. Common examples include security incidents, major product outages, executive transitions, customer-impacting failures, and reputation-sensitive events. It is less useful for low-risk issues that can be handled inside a normal project channel. If there is no need for a holding statement, stakeholder outreach, or decision logging, a lighter workspace is usually enough.
How does this differ from an ad-hoc Slack channel?
An ad-hoc channel is useful for quick discussion, but it often loses decisions, owners, and approved language. This template adds structure through dedicated channels, milestone tracking, task lists, and pinned resources so the response stays organized under pressure. The decision-log and approval matrix help prevent conflicting messages. That makes it easier to hand off work across legal, comms, and customer-facing teams without re-litigating earlier decisions.
What should be customized before using it?
Start by replacing the placeholder members with the actual roles involved in the incident response. Then tailor the task lists, milestone names, and pinned resources to the specific incident type and approval path. Update the external-comms channel guidance so it reflects who drafts, who reviews, and who signs off. If your organization has a formal incident command structure or escalation policy, mirror that language in the workspace.
What integrations are most useful here?
Slack is useful for live coordination, Google Drive for shared drafts and source documents, Jira for remediation work, and Zoom for live incident calls. The key is to keep the workspace linked to the places where facts, approvals, and action items already live. For example, the incident timeline can reference Drive docs while remediation tasks sync to Jira. Use integrations to reduce duplicate entry, not to create another layer of process.
What are the common rollout mistakes?
The biggest mistake is creating the workspace after the incident is already chaotic, which slows down the first decisions. Another common issue is using vague roles or leaving owner ambiguity in the task lists, which causes approvals to stall. Teams also forget to retire or archive unused channels after the incident, which makes later reviews harder. A short setup checklist and a clear DRI for each milestone usually prevent those problems.
What should happen after the incident ends?
The workspace should transition from active response to review and remediation, not just sit idle. Use the post-incident review milestone to capture what happened, what was communicated, what was approved, and what follow-up work remains. Then assign owners for remediation, customer follow-up, and any policy or process changes. That makes the workspace useful for learning, not just for live coordination.
Related templates
Go deeper on the topic
-
Internal communications is how a company talks to itself: news, announcements, leadership messages, safety alerts, and the daily hum of "what's happening...
-
An internal newsletter is a regularly cadenced digest of organizational updates — business news, people news, policy changes, culture moments — sent to the...
-
Frontline communication is how a company reaches the 80% of its people who don't live in email. It's targeted, mobile-first, often bilingual or multilingual,...
-
Enterprise search with RAG (retrieval-augmented generation) answers questions by fetching the company's own content first, then asking a model to summarize...
-
Top 5 Yammer alternatives for enterprise collaboration software, with secure deployment options and the best fit for your team.
-
MangoApps is named a Gartner Visionary for the third consecutive year in the 2025 Magic Quadrant for Intranet Packaged Solutions—ranked top 3 across all six...
-
Learn what RSS feeds are, why they matter for business communications, and how an intranet platform like MangoApps centralizes content subscriptions for your...
-
Workplace by Facebook is shutting down. See how MangoApps replaces it with AI-powered intranet, mobile-first design, and a hassle-free migration process.
Ready to use this template?
Get started with MangoApps and use Crisis Communications with your team — pricing built for small business.
