The original title is about incident communication and status pages. Let me craft a concise headline that preserves the key facts.

Short summary

A practical guide to incident communication covering status page update cadences by severity (P1/P2/P3), message structure, and pre-built templates for investigating, identified, monitoring, and resolved states. Includes concrete examples of bad vs good communication, internal vs external messaging differences, and a post-incident report template. Emphasizes that silence during outages destroys customer trust more than the outage itself.

• •Defines update cadence rules by severity: P1 every 15 min, P2 every 30 min, P3 hourly
• •Provides pre-built status page templates for each incident phase
• •Contrasts internal technical comms (Slack) with external user-facing comms
• •Includes post-incident report structure to publish within 48 hours

Generated with AI, which can make mistakes.