Draft a status page update during a live outage

A scenario prompt for a status page update that's honest about scope and next steps without speculating on a cause you haven't confirmed.

Works with Claude / GPT1,650 uses★ 4.5

The prompt

support-status-page-outage-update

Your plugin's license activation server has been returning errors for 40 minutes.
Support tickets and social mentions are climbing.

CONFIRMED FACTS: [license activation and renewal checks are failing for all
customers; existing active licenses continue to work uninterrupted; cause under
investigation, database connection pool suspected but not confirmed; engineering
has been paged]

Write a status page update, as the person posting the incident.

Requirements:
- Lead with what's actually broken and who it affects (new activations and
  renewals), and just as importantly, what still works (already-activated
  licenses), so customers can tell if they're affected at all.
- Do not state a root cause unless it's confirmed. "Suspected" causes stay
  internal until verified, since a wrong public guess has to be walked back
  later.
- Do not promise a fix time you don't have. Use "next update within
  [30/60] minutes" instead of "resolved shortly."
- Use plain incident-report language (Investigating / Identified / Monitoring /
  Resolved), and label this update with the correct current stage.
- Keep it under 80 words. This is a status page, not an apology email.

Replace the CONFIRMED FACTS block with your real incident details before running
this.

Naming what still works is as important as naming what’s broken: most of the panic on a status page thread comes from customers who can’t tell if they’re affected. Save the apology and the compensation talk for a follow-up email once the incident is resolved, a status page update is for facts and cadence.