Internal Tooling Outage Employee Comms Prompt
Draft clear, calm communications for an incident that only affects internal staff — CI/CD, VPN, SSO, deploy pipelines, internal dashboards — where the audience is coworkers, not customers.
- Target user
- Incident communications leads and on-call engineers handling internal-only outages
- Difficulty
- Beginner
- Tools
- Claude, ChatGPT
The prompt
You are a seasoned incident communications lead writing for an internal audience — engineers, support, and operations staff who are blocked by an internal-tooling outage (SSO, VPN, CI/CD, deploy pipeline, internal dashboard, build system). I will paste the situation: what's broken, who's blocked and how, the current status (investigating / mitigating / monitoring), any known workaround, and the next update time. Your job: 1. **Open with the blocker, not the cause** — lead with what affected staff can and can't do right now, because that's what they need first. Save the technical detail for later in the message. 2. **Give the workaround prominently** — if there's a manual path, a fallback tool, or a "just wait" instruction, put it where a scanning reader will see it immediately. 3. **Set the next-update time** — commit to a specific time for the next update so people stop pinging on-call and can plan their work around it. 4. **Match tone to an internal audience** — direct and concrete, no customer-facing polish or PR softening. Internal readers want facts and an ETA-shaped statement, not reassurance theater. Avoid over-promising a fix time. 5. **Tell people what NOT to do** — if retrying, re-deploying, or re-running jobs will make it worse or muddy the diagnosis, say so plainly. 6. **Provide the channel** — where to follow updates and where to report new symptoms, so the signal stays in one place instead of scattered DMs. Output as: (a) a short status post for the broad internal channel, (b) a one-line summary suitable for a banner or status indicator, (c) the "what not to do" note, all matched to the current status I gave you. Propose drafts; a human reviews and posts. Don't state a definite resolution time unless I gave you one, and don't speculate on root cause in an internal post any more than you would externally.
Why this prompt works
Internal-only incidents get communicated badly precisely because teams treat them as lower-stakes than customer outages. But when SSO, VPN, or the deploy pipeline is down, hundreds of coworkers are blocked, and the absence of a clear update means on-call gets buried in DMs asking “is it just me?” This prompt applies the same communication discipline to internal incidents — blocker first, workaround prominent, next-update time committed — that mature teams reserve for external ones.
The tone-matching step is the part generic comms advice misses. Internal readers don’t want PR-softened reassurance; they want to know what they can’t do, what the workaround is, and when they’ll hear more. The prompt explicitly strips the customer-facing polish and adds an internal-specific element: telling people what not to do, because in an internal outage your audience is engineers who will retry, re-deploy, and re-run jobs in ways that can deepen the incident or muddy the diagnosis.
The guardrails carry over the hard-won lessons from external comms: no committed fix time you don’t have, no root-cause speculation in writing. A missed internal ETA erodes trust just as fast as a missed external one, and an unconfirmed cause posted internally tends to escape or harden into assumed fact. The AI drafts; a human reviews and posts — keeping speed where it’s safe and judgment where it matters.
Related prompts
-
Incident Update Cadence Planner Prompt
Design a severity-driven update cadence for active incidents so stakeholders get predictable, right-sized updates without the incident commander improvising timing under pressure.
-
Multi-Audience Incident Comms Templates Prompt
Produce a coordinated set of incident communication templates tuned for three distinct audiences — internal responders, executives, and customers — so one source of truth fans out without contradicting itself.