Skip to content

Send Clear Internal Comms During an Active Tooling Outage or IT Disruption

Stop 200 duplicate 'is SSO broken?' pings and arm Sales/Support with approved customer talking points within 10 minutes of an active outage.

Copy the prompt and paste it into the AI assistant you already use.

What customer-facing and internal teams need in the first 10 minutes

  1. 01

    State clearly what IS working alongside what is degraded

    Panic spreads when people assume the entire platform is dead; specify 'Analytics dashboards are timing out; live checkout, API webhooks, and login remain 100% operational.'

  2. 02

    Include a copy-paste 'Approved Customer Snippet' for Sales & CS

    Without approved phrasing, twenty reps improvise twenty conflicting guesses on root cause—give them two verified, calm sentences safe to send externally.

  3. 03

    Direct all chatter to ONE read-only status thread to shield engineers

    Explicitly instruct employees 'Do NOT DM on-call engineers directly; check #incident-status—next update guaranteed at 11:30 ET even if unchanged.'

  4. 04

    Never speculate on root cause or data loss before verification

    Stick strictly to observed symptoms and mitigation progress during active triage; unverified early guesses ('probably AWS') create embarrassing walk-backs later.

Common questions

How fast should the first internal advisory go out during a noticeable outage?

Within 10 to 15 minutes of confirmed impact—saying 'We are aware, Engineering is actively investigating, use Sandbox B for demos, next update at :45' beats 40 minutes of radio silence.

How often should internal updates post if the outage drags past two hours?

Commit to a predictable cadence—every 30 minutes for P1 outages, every 60 minutes for P2 internal tool issues—and honor the timestamp even if the update is 'mitigation rolling out, testing now.'

Should everyone in the company receive email blasts for minor tool hiccups?

Reserve all-staff email for company-wide blockers (SSO, email, payroll) or P1 customer outages; post department-specific tool issues (like Salesforce sync lag) in GTM channels only.

Learn more

Related guides and background articles for this task