Write a Customer Outage Update for Status Page, Email and Social
Get a status page post, customer email and social update for an ongoing incident, built only from confirmed facts, with no guessed causes and a clear next update time.
You getStatus page update, customer email and social post
Prompt
You are an incident communications lead at a software company. Your job is to write customer-facing updates about an ongoing outage or incident.
Before writing anything, ask me these questions in one message and wait for my answers:
1. What do we know for certain right now (what is broken, since when, who is affected)?
2. Which features, regions or plans are affected, and which still work normally?
3. Is there a workaround customers can use?
4. When will the next update be posted, and in which time zone?
Rules:
- State only confirmed facts. Do not guess at causes. If the cause is unknown, say we are investigating it.
- Never promise a fix time unless I give one. Always state the next update time with a time zone.
- Name affected and unaffected features explicitly so customers can tell whether they are impacted.
- Plain words, no technical jargon, no blame on vendors or staff, and one apology only.
- Status page body under 80 words; social post under 280 characters.
Output format:
1. Status page update: title, status label (Investigating, Identified, Monitoring or Resolved), body.
2. Customer email: subject line, body under 150 words, sign-off from the team.
3. Social post: one version that points readers to the status page.
End with a short list of facts that were missing or unclear that I should confirm before publishing.Example output
Tips and common edits
Why this works
- Asking for confirmed facts first stops the model from filling gaps with guessed causes or invented fix times.
- Requiring affected and unaffected features lets customers decide in seconds whether the incident touches them.
- The closing list of missing facts catches errors before an update goes public, when corrections are costly.
Use during a live incident when you need consistent updates fast. Have your confirmed facts, affected features and next update time ready. Works in ChatGPT, Claude or Gemini; rerun for each new update.
Common edits
- Add a fourth output: a short in-app banner message under 120 characters.
- Ask for a Resolved version with a plain summary of impact and duration once the incident ends.
Prompt details
- By
- Prompts-GPT editors
- Published
Keep exploring
More like this
Audit a Help Center Article for Gaps, Jargon and Outdated Steps
Paste a help center article and get a pass/fail checklist scorecard plus a line-by-line fix list ranked by customer impact, without a full rewrite.
Turn Feature Notes into a Step-by-Step Help Center How-To Guide
Paste rough notes about a product feature and get a customer-ready how-to guide with one action per step, bold UI labels, expected results and a troubleshooting section.
Write Chatbot Intent Answers with Trigger Phrases and Human Handoff Rules
Get a set of chatbot intents for your top support questions, each with customer-style trigger phrases, a short bot answer, and an exact rule for handing off to a human.
Write Help Article Titles and Meta Descriptions in Your Customers' Words
Get help article titles that start with the customer's task verb and meta descriptions within search length limits, each with a character count and the customer phrase it matches.
Build a Yes/No Troubleshooting Decision Tree for a Recurring Product Issue
You get a step-by-step yes/no troubleshooting tree ordered from fastest, most likely checks to slowest, with ready-to-send customer messages and a clear escalation point.
Find the Themes in Customer Feedback and CSAT Comments with Real Counts
Returns a theme table with exact counts, a verbatim quote from your data, likely root cause and suggested owner, plus top actions and data gaps.