---
name: saas-downtime-status-memo
description: "Writes the status page updates for an outage, clear about what is broken, what you are doing and when to expect the next word. Use when a support or engineering lead must post status page updates during an unexpected service outage. Do not use for a full post-incident report or internal incident coordination. Related topics: customer support, communication, saas."
---

# SaaS Downtime Status Memo

Writes the status page updates for an outage, clear about what is broken, what you are doing and when to expect the next word.

## When to use

Use this skill when a support or engineering lead must post status page updates during an unexpected service outage. Do not use it for a full post-incident report or internal incident coordination.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Describe the impacted services and symptoms in terms customers recognise.
3. Write the Investigating update with what users see and when the next update comes.
4. Write the Identified update with the action under way and the ETA labelled as an estimate.
5. Write the Resolved update with confirmation and the discount claim steps if offered.
6. Add a one-line social post and email subject.

## Inputs

- **Impacted services** (choose any: Database, Auth, Storage, Web App, Mobile App)
- **ETA for resolution** (free text, e.g. "2 hours")
- **Apology discount offered** (choose one: Yes, No)
- **What users see** (longer free text)

## Output

Three timed status updates, plus a one-line social post and an email subject.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### SaaS Downtime Status Memo

Draft status page notifications for an unexpected outage.

- Impacted services: {{Impacted services}}
- ETA for resolution: {{ETA for resolution}}
- Apology discount offered: {{Apology discount offered}}
- What users see: {{What users see}}

Write three updates in order: Investigating, Identified and Resolved. Each one states the time, which services are affected in plain words (not internal names), what users will notice, what the team is doing, and when the next update will come. Use the ETA as an estimate, never a promise, and say so. If a discount is offered, mention it only in the Resolved update with how to claim it. Be calm and factual: no blame, no jargon and no speculation about the cause until it is confirmed.

Add a one-line short version for social media and a one-line subject for email.

## Pitfalls

- Promising an ETA as a fixed time, then missing it and losing trust.
- Naming a root cause before it is confirmed.
- Using internal service names that customers do not recognise.
