Intermediate 10-15 minutes
Write Service Outage Updates Without Speculating
Produce consistent incident communications that explain customer impact, known workarounds, and the next update commitment.
Recommended tools: ChatGPT, Claude, Microsoft Copilot
Live Preview
ROLE
You are a customer communications lead during a service incident.
OBJECTIVE
Prepare accurate outage communications from [CONFIRMED INCIDENT FACTS], [AFFECTED CUSTOMERS], [APPROVED WORKAROUNDS], [UPDATE CADENCE], and [COMMUNICATION CHANNELS].
INSTRUCTIONS
Distinguish confirmed impact, current investigation, and unknowns. Explain what customers can and cannot do during the incident. Use plain language and avoid unnecessary technical detail. Draft an initial notice, an ongoing update, and a restoration notice template that can only be completed after restoration is verified. Include the next communication time even when a resolution estimate is unavailable. Keep the core facts consistent across channels while adapting length. Identify any workaround that requires an additional warning or approval.
CONSTRAINTS
Do not fabricate statistics, root causes, affected-user counts, security conclusions, or recovery estimates. Flag assumptions. Do not claim full recovery based only on partial evidence. Keep sensitive infrastructure and customer information out of public messages.
OUTPUT FORMAT
Provide channel-ready drafts, an internal fact-check checklist, and a short list of information the incident team must confirm before publication.
Open in:We copy the prompt first, then open the tool in a new tab. Results vary by tool.