Crisis Communications
New business and client engagements where creative vision, strategy alignment, and multi-stakeholder approval determine outcomes.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Rapid Situation Intake
Capture the immediate facts, legal constraints, stakeholders, timeline urgency, and desired outcomes to prioritize response actions.
Discovery Questions
Quick Check: Your current posture
- Tell me briefly about the most recent incident your team managed, including timing and outcome.
- How often do incidents that require an immediate communications response occur for your organization?
- Which of these issue types has your team handled in the last two years?
- Describe who typically rings the alarm first inside your organization and how that alert reaches you.
- Estimate the typical time from first alert to a leadership communications decision in your last three incidents.
- When you think back to your last response, what felt like the single biggest communications mistake and why?
Where pressure peaks
- Name the one misstep in past incidents that cost you the most stakeholder trust.
- Who outside the executive team has the authority to demand disclosure or a public statement during an active event?
- How many external channels—media outlets, social platforms, regulators—typically start reporting within the first 24 hours for incidents like yours?
- Describe the legal or regulatory constraints that have forced you to withhold or delay communications in past events.
- If a regulator subpoena or law enforcement request arrived during a public response, what immediate action would stop the communications plan?
People, power, and approvals
- Tell me why your current approval path would survive an incident that requires a same-day public statement.
- Which roles are always included in crisis calls and which are optional?
- Who is the single final approver for any public messaging, and under what circumstances can that change?
- List the documents or legal signoffs you must have before a statement goes live.
- Rate the readiness of those approvers to convene within two hours during off-hours.
- What single legal or board-level condition would prevent you from authorizing a media response even if leadership wanted to speak?
Operational readiness and gating factors
- Explain which internal systems, data sources, or monitoring feeds must be available before a partner can run your monitoring and distribution playbook.
- Name the third-party systems that would need to connect to monitoring, distribution, or reporting tools for this engagement to work.
- Identify which team owns API access, credentials, or vendor relationships the partner would need to operate effectively.
- Estimate the headcount or FTE time your team can dedicate to onboarding and daily coordination during a 30-day engagement.
- Are there regulatory approvals, board notifications, or legal clearances that could push initial availability beyond 72 hours?
- If those systems or approvals are not in place, can your team commit to setting them up within four weeks to meet a go-live window?
Other paths you're weighing
- List the alternatives you are actively evaluating, including internal options, your incumbent provider, and other firms.
- For each alternative, explain the condition under which you would stick with it instead of changing.
- Has anyone on your team proposed solving monitoring and rapid response internally, and if so who would lead that effort?
- Select the factors that would make you choose to stay with your current approach.
- Suppose an external partner guaranteed named senior counselor availability within two hours, name the internal barrier that would still prevent you from engaging them.
What success looks like under pressure
- Assume we had 48 hours to show measurable progress, outline the three metrics you would expect to move first.
- Provide target thresholds for media sentiment, executive visibility, and employee communications engagement you would consider acceptable after one week.
- Identify the decision-maker who will sign off on those thresholds and explain how they balance speed against legal exposure.
- When would you expect a partner to deliver a written after-action summary, and who on your team must receive it?
- Suppose a pilot shows the promised reduction in misinformation spread, which of the following would speed your internal approval to retain the partner?
Next steps and deal accelerators
- Point to the one internal decision that, if approved this week, would let you sign a contract within 10 days.
- Indicate the role that controls the budget for this engagement.
- Are there procurement steps, security reviews, or vendor onboarding checks that typically extend contracting beyond your target window?
- Outline the minimal SLA, retainer, or response-time commitments you require to move forward.
- Assuming the seller named the senior counselor you need and committed to a 24-hour start, would there be any other barrier to you signing within the month?
-
Scenario Walkthrough & Tabletop
Walk through how the seller will operate in the buyer's context using realistic scenarios to validate roles, approval flows, and expected outputs.
Solution Experience
- Scenario Walkthrough and Tabletop Session
- Confirm the current state and its cost to your team
- You confirm the demonstrated workflow removes the approval bottlenecks that currently delay statements.
- Deliver a tailored scenario playbook draft mapping approvals, templates, and a 48-hour on-call roster within 48 hours.
- You confirm the named approvers, spokesperson roster, and escalation thresholds reflect your decision authorities.
- Run a live buyer-context scenario walkthrough
- Provide the definitive list of legal approvers, spokesperson candidates, and their contact availability windows.
- You agree the seller will produce a tailored scenario playbook and a simulation schedule that will serve as final proof points toward engagement.
- Validate approval flows and spokesperson controls
- Share any existing crisis templates, recent media sensitivities, and regulatory reporting deadlines relevant to the scenario.
- Draft and test the initial holding statement and channel actions
- Run a 60-minute simulation with the identified approvers within the next 7 days to validate the playbook under time pressure.
- Confirm the future state and remaining evidence
- Scenario Walkthrough and Tabletop Session
- Scenario Walkthrough Deck
- Scenario Walkthrough Brief
- meeting
- slides
- document
-
Working Sessions & Simulations
Run structured workshops, simulated press conferences, and stakeholder rehearsals to surface gaps and align on playbook actions.
Working Meetings
- Scenario Selection and Exercise Planning
- Tabletop Walkthrough, Scenario A
- Simulated Press Conference and Media Q&A Rehearsal
- Stakeholder Rehearsal and Approval Workflow Test
- Playbook Update, Readiness Decision, and Next Steps
- Update the playbook sign-off workflow with SLA timings and escalation steps based on the timed rehearsal results.
- Compile a short practice plan for the spokesperson addressing identified delivery issues.
- Recap scenario and key messages
- A validated sign-off workflow with SLAs for each approver role and a list of edits required to meet timing targets.
- Completed draft internal FAQ and regulator response templates ready for insertion into the playbook.
- A list of required contact detail updates and escalation paths for the stakeholder roster.
- Confirm scope and success criteria
- Publish the internal FAQ and regulator response templates as draft artifacts for final legal review.
- Produce an updated stakeholder contact list and escalation matrix with preferred contact methods and backup contacts.
- Review consolidated changes and artifacts
- A versioned playbook approved for use during incidents with a published change log of what changed.
- Named owners and an on-call schedule documented and accepted for the agreed readiness period.
- A documented readiness decision, or a clear remediation plan with owners and deadlines if not yet ready.
- Publish the versioned playbook with a change log and distribute to the stakeholder roster.
- Schedule and publish the on-call rotations and handoff procedures for the next 90 days.
- Activate the agreed monitoring feeds and set the first incident report cadence with templates.
- A prioritized list of 1 to 3 scenarios with severity tiers and inject points agreed for the working sessions.
- A signed exercise plan including participant roles, schedule, and success criteria for each scenario.
- A logistics checklist for running simulations, including recording and documentation assignments.
- Draft scenario scripts for each agreed scenario including timeline, initial facts, and three injects.
- Produce participant role list and contact availability windows for the scheduled exercises.
- Prepare exercise logistics pack including platform access, recording permissions, and note templates.
- Brief recap of scenario facts and objectives
- A documented incident timeline with each decision point mapped to required approver roles and expected time-to-decision.
- A prioritized gap list with proposed mitigation options for each gap.
- A list of evidence and data feeds needed at each decision point to avoid delays.
- Produce a mapped decision flow diagram showing approver roles, handoff points, and SLA timings for decisions.
- Document the prioritized gap list and proposed mitigation options for playbook updates.
- Compile the list of data sources and monitoring feeds required for each critical decision point.
- Exercise objectives and scoring criteria
- A rehearsal-scored, revised statement draft ready for inclusion in the playbook.
- A populated Q&A response library with graded risk levels and escalation rules for high-risk questions.
- A list of performance improvements for the spokesperson with time-boxed practice items.
- Produce the final statement draft and mark any legal caveats or factual checks required before public release.
- Create the Q&A response set with suggested phrasing, fallback lines, and escalation triggers for out-of-scope questions.
- Select priority scenarios and severity tiers
- Simulate approval workflow under timed conditions
- Confirm owners and on-call coverage
- Deliver mock opening statement
- Walkthrough of the incident response timeline
- Role-play regulator and employee inquiries
- Role-play press Q&A
- Set monitoring, reporting, and escalation endpoints
- Identify required participants and roles
- Identify decision triggers, approvals, and maximum response times
- Agree exercise format, timeline, and logistics
- Formal readiness decision and next steps
- Capture gaps and mitigation options
- Immediate critique and message refinement
- Finalize internal FAQ and regulator response templates
-
Service Scope
Define deliverables, on-call coverage, playbook components, media monitoring, reporting cadence, and responsibilities.
Scope Configuration
- 24/7 Crisis Hotline and Rapid Response
- Draft Initial Holding Statement
- Draft Regulator Disclosure Messaging
- Draft Customer and Partner Notifications
- Draft Employee Memo and FAQs
- Real-Time Media Monitoring and Social Listening
- Message Map and Q&A Package
- Simulated Press Conference and Spokesperson Coaching
- Press Release Drafting and Distribution Support
- On-Call Media Relations and Journalist Outreach
- Social Media Rapid Response and Post Management
- Legal Clearance and Redline of Public Statements
- Localize Statements and Translations
Scope Questions
24/7 Crisis Hotline and Rapid Response
- Do you need 24/7 phone hotline coverage for initial triage of incidents (voice and voicemail-to-email)?
- How quickly must we answer an inbound hotline call for initial triage and escalation (for example within 30 minutes, 60 minutes)?
- Which members of your incident response roster should receive hotline escalations (for example general counsel, chief communications officer, head of security)?
- Who is the primary authorized contact we may call and who can approve immediate external messaging from your side?
- Are there specific jurisdictions or notification regimes (for example GDPR data protection authority, SEC, state breach-notification laws) that change hotline escalation workflows?
- Confirm whether the acceptance criterion for this module is that a senior counselor answers the hotline and documents an initial triage note within the selected SLA.
Draft Initial Holding Statement
- Do you want separate holding statement drafts for media, regulators, and employees or a single universal holding statement?
- Provide the critical facts we are permitted to include in the holding statement (for example confirmed affected systems, number of impacted records, immediate containment steps).
- Which legal constraints should we observe when drafting the holding statement (for example pending litigation, securities disclosure windows, nondisclosure agreements)?
- Who on your side must pre-clear the holding statement before distribution (for example lead counsel, chief communications officer, CEO)?
- When should the holding statement be issued relative to incident discovery (for example within 1 hour, within 4 hours, same business day)?
- Do you require a short-form headline holding statement optimized for social posts in addition to a long-form release for owned channels?
Draft Regulator Disclosure Messaging
- Which regulators or reporting regimes will likely require notification in an incident (for example data protection authority, industry regulator, securities regulator)?
- Describe the disclosure triggers your legal team uses that would require regulator messaging (for example confirmed exfiltration of >10,000 records, material impact on operations, regulatory subpoena).
- Who prepares the technical factual appendix for regulator submissions (for example your internal incident response team, external forensic vendor, or both)?
- Do you need templated regulator disclosure language for specific jurisdictions and formats (for example CSV of affected records, formal cover letter for data protection authority)?
- How quickly must regulator disclosure messaging be ready after the trigger event (for example within 24 hours, 48 hours, as counsel directs)?
- Are there mandatory data fields or formats regulators require that we must include in messaging (for example incident classification codes, affected user counts, remediation timelines)?
Draft Customer and Partner Notifications
- Which customer or partner segments need separate notification templates (for example enterprise customers, SMB clients, resellers, channel partners)?
- Provide the content tiers you expect for customer notifications (for example immediate holding message, technical details for IT contacts, remediation steps, offers of credit).
- Do you require API or CRM integration to push notifications directly from your customer database (for example integration with your CRM export or email platform)?
- How will recipient lists be authenticated and verified prior to distribution (for example CRM export with verification, hashed email lists, OTP confirmation)?
- When do you intend to send customer notifications relative to regulator filings (for example before regulator disclosure, simultaneous, after legal sign-off)?
- Which success metric will validate a customer notification deployment (for example delivery rate >95%, open rate >30%, acknowledgement from priority customers)?
Draft Employee Memo and FAQs
- Which employee populations need tailored memos and FAQs (for example frontline staff, remote employees, contractors, unionized workers)?
- Provide the permitted level of technical detail for employee memos (for example high-level reassurance, system-specific remediation steps, or detailed incident timelines).
- Do you want a manager-facing FAQ with scripted answers for difficult questions and escalation paths for HR?
- Who will manage internal distribution channels and which channels do you use (for example corporate email, intranet, Slack or Microsoft Teams)?
- When should employee communications be sequenced relative to public statements and customer notifications (for example before public statement, simultaneous, after customers)?
- Are there HR or union review steps that must occur before an employee memo is distributed (for example HR sign-off, union notification period)?
Real-Time Media Monitoring and Social Listening
- Which specific media outlets and journalist beats must be included in monitoring (for example national business press, cybersecurity reporters, key local outlets)?
- Which social platforms require active listening and moderation during the incident (for example Twitter/X, LinkedIn, Facebook, Reddit, Telegram)?
- How frequently do you require live monitoring reports during active response (for example every 15 minutes, hourly, four-hour digest)?
- What alert thresholds should trigger an escalation to the response team (for example 20% spike in negative mentions, a post with >10,000 engagements)?
- Do you require sentiment analysis and a share-of-voice comparison against named competitors or sector peers during the incident?
- Will you provide access to existing paid monitoring feeds or do you need us to provision paid vendor dashboards for media clipping and social listening?
Message Map and Q&A Package
- Which external and internal audiences must be mapped with priority messages (for example customers, regulators, employees, investors)?
- Provide up to three priority messages you want emphasized in the message map (for example containment complete, notification issued, remediation underway).
- Do you require a legal-approved Q&A with scripted lines for common media and regulator questions (for example scope of breach, number of affected users, remediation timeline)?
- Who must sign off on the final message map and Q&A package (for example in-house counsel and chief communications officer)?
- Confirm the acceptance criteria for the message map: sign-off by your legal counsel and chief communications officer and delivery of editable source files.
- Which file format do you prefer for the message map and Q&A deliverable (for example slide deck, editable Word document, Google Doc)?
Simulated Press Conference and Spokesperson Coaching
- Which named spokespersons require coaching and in what priority order (for example CEO for major statements, chief communications officer for media briefings)?
- Do you require a full simulated press conference with live journalists, a closed-room tabletop rehearsal, or both?
- How long should each simulation or coaching session run (for example 60 minutes, two hours, half-day)?
- Are there specific tough topics you want rehearsed during coaching (for example regulatory penalties, scope of data exposure, executive accountability)?
- Who will provide the factual brief and incident timeline used in simulations (for example internal incident lead, external forensic vendor)?
- Do you want video recording of spokesperson rehearsals and an annotated critique with improvement actions?
Press Release Drafting and Distribution Support
- Which distribution channels should we use for press release distribution (for example wire services, owned website press room, partner channels)?
- Do you require embargoed distribution to select reporters before public release under agreed terms?
- Which approved media contact list will we use for distribution and will you provide the verified media list or require us to build one?
- What localization or regional variant needs exist for press releases (for example market-specific statements, translated versions for LATAM or APAC)?
- How will you measure distribution success for press releases (for example pickup count, share-of-voice, syndication on top-tier outlets)?
- Do you require post-distribution clipping and media impact reports bundled with the press release delivery?
On-Call Media Relations and Journalist Outreach
- Which journalist beats and specific reporters should receive proactive outreach during the incident (for example national business editors, cybersecurity reporters)?
- Who will be authorized to go on-the-record for interviews and who is reserve spokesperson (for example named CEO, CCO, head of security)?
- Do you want pitch templates and embargo scripts prepared for outreach to priority reporters?
- How many targeted journalist outreaches per day should we plan during peak response (for example 1-5, 6-15)?
- Are there reporters or outlets you explicitly want us to avoid engaging due to prior sensitivities or legal exposure?
- When should proactive journalist outreach begin relative to the public statement (for example before under embargo, at time of release, after release)?
-
Engagement Agreement
Finalize commercial and legal terms, retainer or fee structure, SLAs, confidentiality, and escalation commitments.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Retainer and Fee Schedule
- Service Level Agreement (SLA)
- Non-Disclosure Agreement (NDA)
- Data Processing Agreement (DPA)
- Escalation and On-Call Commitment
- Media and Statement Approval Protocol
- Termination and Transition Addendum
- Regulatory Compliance Addendum (conditional)
-
Delivery
Operationalize response readiness, on-call duties, and coordinated execution.
-
Response Readiness
Capture concrete readiness facts—primary contacts, legal approvals, spokesperson roster, authorized channels, and monitoring endpoints.
Readiness Questions
Primary contacts and ownership
- Who is the buyer's primary incident lead (name and title)? Please supply a single name and role — this person will receive initial situational updates and decisions.
- Who is the secondary/on-call contact for 24/7 escalation (name, title, preferred contact method)? We need a backup we can reach outside business hours.
- Is 24/7 on-call coverage confirmed for the incident response period? (So we can schedule seller shift coverage immediately.)
- If 24/7 coverage is not yet confirmed, what is the target confirmation date? (Provide a date we can plan against.)
Legal approvals and authority
- Has the buyer pre-authorized any holding statement language for immediate release? (This lets us issue a first notification within hours if needed.)
- Who is the legal approver for public communications (name and role)? This is the person the seller will route time-sensitive drafts to for sign-off.
- Is an engagement confidentiality agreement or NDA in place that allows the seller to receive and act on sensitive materials?
Spokespersons and authorized channels
- Is the external spokesperson roster final for media responses (confirm only — exact roster entries go in DeploymentConfig)?
- Are the authorized external communication channels confirmed (press release, corporate site, social channels, regulator filings)? We will request exact channel details in DeploymentConfig.
- Are internal employee communication channels authorized for immediate use (intranet, all-staff email, town hall)? Select the current approval state.
Monitoring, alerts, and escalation readiness
- Are media and social monitoring feeds provisioned and accessible to the seller's team (so we can surface issues and trigger alerts)?
- Are escalation thresholds, alert cadence, and incident priority definitions agreed (so we know when to escalate to executive and legal teams)?
-
Operational Configuration
Lock configuration details the team will use—media lists, distribution channels, statement templates, monitoring feeds, and escalation thresholds.
Configuration Details
Operational Configuration — Overview
- Canonical configuration ID (single token used by the platform to identify this operational configuration; example: 'incident-response-prod')
- Primary deployment environment this configuration applies to (Default: Production)
Media Distribution Channels & Lists
- Select enabled distribution channels (consumed by the distribution module; default: Email + Owned social) — choose all that apply
- Master media list filename or cloud folder path used for distributions (consumed by distribution module; format example: 'media-list-20260721.csv' or 'SharedDrive/MediaLists/June2026')
Statement Templates & Approval Flow
- Which statement template types should be available in this configuration (consumed by the template engine) — choose all that apply
- Approval workflow for external statements (consumed by approval engine; Default: Legal -> Communications -> CEO)
Monitoring Feeds & Connector Endpoints
- Primary monitoring feed type (consumed by monitoring connector; Default: SaaS monitoring provider)
- If 'Customer self-hosted feed', enter the monitoring endpoint URL (format: https://...) — leave blank if not applicable (consumed by the monitoring connector). Do NOT paste credentials or API keys here.
Escalation Thresholds & On‑Call Activation
- Number of Tier-1 media escalations within a 24-hour window that will automatically activate 24/7 on-call (numeric; Default: 3)
- Canonical on-call owner identifier (enter a single name or filename for the on-call roster used by the platform; example: 'oncall-roster.csv' or 'Jane Doe')
Reporting, Retention & Handoffs
- Incident status report cadence in hours (numeric; Default: 4) — consumes the reporting scheduler
- Retention period for monitoring and distribution logs in days (numeric; Default: 90) — consumed by log retention and export routines
-
On-Call Response & Program Delivery
Execute the agreed response plan with named owners, task sequencing, 24/7 coverage, stakeholder coordination, and media engagement.
-
-
Reputation Recovery & Lessons Learned
Assess outcomes against success signals, capture lessons, and maintain a shared channel for follow-ups, issues, and enhancements.
Success Reviews
- Post-Response Health Check
- First Measurement Review
- Acceptance Gate, 90-Day Outcome Decision
- Reputation Recovery Retrospective and Lessons Learned
- Quarterly Recovery Review
Issues & Enhancements
- Produce a lessons-learned report with a redlined playbook showing required changes and rationale.
- Open remediation tickets for each failed criterion with owners and target resolution dates.
- Distribute the evidence package used for the acceptance decision to stakeholders for the record.
- Review outcome metrics and trend lines
- Document a prioritized list of lessons learned and the exact playbook changes to be made.
- Agree a timeline and owner-less tasks to implement playbook updates and training refreshes.
- Establish an ongoing monitoring cadence to watch net media sentiment score and the count of reopened reputation incidents.
- Re-confirm agreed success criteria and owners
- Create a training schedule to rehearse updated spokesperson guidance and approval flows.
- Set up a standing monitoring report tracking net media sentiment score and reopened reputation incidents, delivered each quarter.
- Review quarterly metric trends
- Confirm whether net media sentiment score and reopened incident count indicate sustained recovery or require further work.
- Agree on maintenance items and updates required to prevent recurrence of the same issues.
- Keep the remediation and playbook update tracker current with next steps and dates.
- Publish the quarterly metrics brief highlighting changes in net media sentiment score and reopened incident counts.
- Update the remediation tracker with status changes and new deadlines for persistent issues.
- Schedule any necessary follow-up workshops to address complex, recurring issues identified in the review.
- Confirm the response activities and handoff tasks are complete or have owners and deadlines.
- Identify and prioritize any critical open issues that must be closed in the next 30 days.
- Establish a short remediation plan with owners and target dates for immediate risks.
- Publish a 30-day remediation tracker listing open issues, owners, and target close dates.
- Activate monitoring feeds and distribute access to the agreed stakeholder list for ongoing observation.
- Confirm and publish the on-call escalation roster and contact protocol for the stabilization period.
- Present first measurement of net media sentiment score and time to resolution
- Determine whether net media sentiment score and time to resolution for high-severity issues are on track against targets recorded in Service Scope.
- Document root causes for any gaps and commit to specific corrective actions with target dates.
- Agree the next data refresh cadence and owner for metric reporting toward the acceptance gate.
- Deliver a metric dashboard update showing net media sentiment score and time to resolution trend lines for the period.
- Create a prioritized remediation plan addressing the top two drivers of negative sentiment, with deliverable dates.
- Schedule the acceptance gate review and circulate required evidence packet at least five business days in advance.
- Restate acceptance criteria and numeric targets
- Produce a clear pass or fail result for each acceptance criterion recorded in Service Scope.
- Capture a documented acceptance decision and, where applicable, the named signatory for the buyer.
- If any criteria failed, agree a remediation plan with owners and closure dates that will be tracked in ongoing reviews.
- Publish the acceptance decision memo listing pass/fail per criterion and the recorded signatory or buyer decision record.
- Validate deployment and deliverable completion
- Conduct timeline walk-through and decision review
- Surface persistent issues and blockers
- Present outcome data for each acceptance criterion
- Stakeholder feedback and employee sentiment snapshot
- Root cause analysis for any metric shortfalls
- Document pass or fail per criterion and capture decision
- Agree maintenance or corrective actions
- Review early media and stakeholder signals
- Capture lessons and playbook updates
- Team readiness and on-call transition
- Agree ongoing follow-ups and monitoring cadence
- Close completed items and update tracker
- Agree corrective actions and timelines
- Agree remediation items for any failed criteria
- Open issues, blockers, and remediation actions