Uptime Status Page and Communication Plan
Plan how to tell users about incidents.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Plan a status page and incident communication approach. Customer types and their expectations: [CUSTOMERS]. Channels available (status page, email, social media, in-app banner): [CHANNELS]. Sensitive contractual commitments, if any: [COMMITMENTS]. Define severity levels with the communication each triggers and the maximum time to first update. Write templates for investigating, identified, monitoring, and resolved updates, each under 60 words and in plain language without blame. Provide components to show on the page and rules for when a component is marked degraded, partial outage, or major outage. Include a maintenance notice template. Add guidance on what not to say (speculating on causes, promising a time to fix) and an internal approval workflow. List who writes, who approves, and a backup. Add a short list of rules for tone and timing, such as updating at the promised interval even when there is nothing new, and a decision record explaining how the page differs from internal incident channels. Include a plan for what to do if the status page itself is unavailable, and who has permission to publish when the primary person is asleep.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.