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

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

At a glanceLedgerly EU card payment incident at a glanceConfirmed facts used across status page, email and social post
Card payments failing since
09:40 CET
EU region customers only
Next update by
11:30 CET
Cause still under investigation
Channels covered
3 updates
Status page, email and social
Facts to confirm
4 questions
Checked before publishing

Example for: Ledgerly, an invoicing app, where card payments on invoices have failed for EU customers since 09:40 CET; cause unknown, bank transfer still works, next update at 11:30 CET.

1. Status page update

Title: Card payments failing for EU customers

Status: Investigating

Body: Since 09:40 CET, customers in the EU region may see card payments on invoices fail at checkout. Creating, sending and viewing invoices works normally, and bank transfer payments are not affected. Customers outside the EU are not affected. We are investigating the cause. We will post our next update by 11:30 CET.

2. Customer email

Subject: Card payments on invoices are failing in the EU – here's what we know

Hi,

Since 09:40 CET today, card payments on Ledgerly invoices are failing for customers in the EU region. Your clients may see an error when they try to pay by card.

What still works: creating, sending and viewing invoices, and payments by bank transfer.

What you can do now: if a client needs to pay today, ask them to use the bank transfer option shown on the invoice.

We are investigating the cause and do not yet have a fix time. We're sorry for the disruption this causes you and your clients.

We will share our next update by 11:30 CET. You can follow live progress on our status page at any time.

The Ledgerly Team

3. Social post

We're investigating failed card payments on invoices for EU customers since 09:40 CET. Bank transfer payments and all other features work normally. Next update by 11:30 CET – follow along on our status page.

Facts to confirm before publishing

  • Are payments failing for all EU customers or only some card types (e.g. Amex)?
  • Will failed payment attempts be retried automatically, or do clients need to pay again?
  • Are customers in the UK and Switzerland counted as EU region in your system?
  • Has anyone been charged without the invoice being marked paid?
Written by AI from this prompt. Your results will vary.

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

Did this prompt work?

Keep exploring

More in Customer Support