Proactive Outage Communication Template Kit
Create a complete set of outage and incident communication templates — including status page updates, customer emails, social media posts, and internal escalation messages for every phase of an incident.
Prompt Template
You are a customer communications expert specializing in incident and outage management. Help me build a complete outage communication template kit for my company. Company details: - Company name: [company name] - Product type: [SaaS platform / API service / e-commerce / etc.] - Customer base: [B2B / B2C / both] with [number] customers - Communication channels: [email, status page, Twitter/X, Slack community, in-app] - Support team size: [number] - Typical incident types: [list common issues, e.g., API downtime, slow performance, data sync delays] Please create templates for each incident phase: 1. **Detection & Initial Alert** (within 5 minutes) - Internal Slack/Teams message to engineering - Status page update (investigating) - Twitter/X post 2. **Acknowledged & Working** (within 30 minutes) - Status page update (identified) - Customer email (for major incidents) - In-app banner text 3. **Mitigated / Partial Fix** - Status page update (monitoring) - Customer email update 4. **Resolved** - Status page update (resolved) - Customer email — all clear - Twitter/X resolution post 5. **Post-Incident Follow-Up** (within 48 hours) - Customer-facing post-mortem email (transparent but not overly technical) - Status page post-mortem summary 6. **Internal Playbook** - Escalation decision tree (when to email all customers vs. status page only) - Roles and responsibilities during incidents - Severity level definitions (P1–P4)
Example Output
Outage Communication Kit: CloudSync (B2B SaaS)
Phase 1: Detection & Initial Alert
Internal Slack (#incidents):
🚨 INCIDENT DETECTED — P1
What: API response times >5s, error rate 23% (normal: <1%)
Impact: All customers on US-East region
First detected: 10:42 AM UTC
Lead: @sarah-eng
Status page: Updating now
Thread for updates 👇
Status Page (Investigating):
"We're investigating reports of increased API latency and errors affecting the US-East region. Our engineering team is actively diagnosing the issue. We'll provide an update within 30 minutes."
Twitter/X:
"We're aware of issues affecting our API in the US-East region and are actively investigating. Updates: status.cloudsync.io"
Phase 2: Acknowledged
Customer Email:
Subject: ⚠️ Service Disruption — CloudSync API (US-East)
"Hi [Name],
We're experiencing a service disruption affecting API requests in our US-East region. Here's what we know:
**What's happening:** Elevated error rates and latency on API calls
**Impact:** Syncs may fail or be delayed
**Started:** 10:42 AM UTC
**Root cause:** Identified — database connection pool exhaustion
**ETA to fix:** We expect to restore service within 60 minutes
We'll send another update in 30 minutes or sooner if resolved.
We're sorry for the disruption.
— The CloudSync Team"
Phase 5: Post-Incident Follow-Up
Customer Post-Mortem Email:
Subject: Post-Incident Report — March 23 API Disruption
"What happened: A routine database maintenance operation triggered unexpected connection pool exhaustion...
Duration: 10:42 AM – 12:15 PM UTC (93 minutes)
Customers affected: ~2,400 (US-East region)
What we're doing to prevent this: [3 specific actions with timelines]..."
Escalation Decision Tree
P1 (Full outage) → Status page + Email ALL + Twitter + In-app banner
P2 (Degraded, >30% affected) → Status page + Email affected segment
P3 (Minor, <10% affected) → Status page only
P4 (Cosmetic/non-functional) → No external comms, internal tracking only
Tips for Best Results
- 💡Speed beats perfection — get the first status page update out within 5 minutes, even if details are sparse.
- 💡Always include an ETA (even if rough) and commit to the next update time — silence breeds anxiety.
- 💡Write post-mortems within 48 hours while details are fresh. Focus on what you're doing to prevent recurrence.
- 💡Pre-write templates now so you're not crafting messages under pressure during an actual outage.
Frequently Asked Questions
What is the Proactive Outage Communication Template Kit prompt?
Create a complete set of outage and incident communication templates — including status page updates, customer emails, social media posts, and internal escalation messages for every phase of an incident. It's a free ChatGPT prompt template from our Customer Support collection — copy it, fill in the bracketed variables, and paste it into your AI tool.
Which AI tools work with this prompt?
It's written and tested for ChatGPT, Claude and Gemini. Any AI assistant that accepts free-form text prompts will handle it well.
How do I customize this ChatGPT prompt?
Replace the bracketed variables — such as [company name], [B2B / B2C / both], [number] — with your own details before running it. Speed beats perfection — get the first status page update out within 5 minutes, even if details are sparse.
Is this prompt free to use?
Yes. Every prompt on PromptAtlas is free to copy, customize, and use — no signup required.
Related Prompts
SaaS Trial Extension Request Response Builder
Write policy-safe SaaS trial extension responses with decision rules, customer context checks, and sales or success handoff notes.
Subscription Pause Request Support Workflow Builder
Create a support workflow for subscription pause requests with eligibility checks, retention-safe responses, billing notes, and escalation rules.
Customer Complaint Response Template
Write a professional, empathetic customer complaint response that resolves issues and preserves the relationship.