Communicate·Intermediate·20 min·Updated Sep 30, 2026

Draft outage and incident communications fast

Speed up and standardize service disruption messaging so end users hear about an outage quickly and consistently.

Download PDF

Good fit for

ITOperations

Microsoft 365

Outlook

Teams

Works With

ChatGPT

Claude

Copilot

Prerequisites

Your organization's incident communication template or past examples

Business Outcome

Users get consistent, timely incident updates instead of delayed or conflicting messages from different responders.

Workflow Overview

The apps run in this order. At the AI step, pick whichever of these you have — they're alternatives, not a sequence.

Outlook

Teams

ChatGPT

Claude

Copilot

Copilot works differently from the others: with a paid Microsoft 365 Copilot license it's built right into the app above, no copy-pasting needed. Without a license, use it the same way as ChatGPT or Claude — in its own chat window.

Step 1: Gather the known facts about the incidentTeams

Before drafting anything, confirm what's actually known right now: what's affected, since when, and what the current workaround (if any) is. Don't let the draft get ahead of confirmed facts.

Step 2: Draft the notification from your standard templateCopilotChatGPTClaude

Give it the facts you just confirmed and your organization's standard incident template, and ask it to draft the notification in that exact format rather than inventing its own structure.

Prompt idea:

Draft an outage notification for a service disruption affecting [what's affected], ongoing since [start time], with [current workaround, or "no confirmed workaround yet"]. Follow our standard incident communication format and keep the tone calm and factual, not alarming.

Step 3: Verify every technical detail before sendingTeams

Have the incident commander or the engineer closest to the issue confirm the affected systems, start time, and any workaround mentioned in the draft — a wrong detail in an incident message erodes trust fast.

Step 4: Send through the standard channel and log itOutlookTeams

Send via your usual incident communication channel (status page, mass email, Teams broadcast) and keep a copy for the post-incident review.

Step 5: Draft the follow-up once resolvedCopilotChatGPTClaude

Once the incident closes, use the same approach to draft the resolution notice, including a brief root-cause note if one's confirmed.

Check the work

Confirm every technical detail (systems affected, start time, workaround) with the incident owner before sending.
Check the tone doesn't overstate or understate the actual severity.
Verify the message goes out through the channel your users actually expect incident updates on.

Source: Microsoft Copilot Scenario Library — IT (2026)

Expected Outcome

A drafted outage notification ready to send, following your standard incident communication format.

✓

AI is the right call here

Speed and consistency under pressure are the whole point: drafting from scratch during a live incident is slower and more error-prone than applying your standard template to the facts gathered in step 1.

Non-AI alternative: A pre-written template library with fill-in-the-blank fields (system, start time, workaround) covers routine outages without AI, though it's less flexible for an unusual incident.