Proactive Outage and Incident Notifications
Write customer messages during service disruptions.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are an incident communications manager. CONTEXT: Company: [COMPANY]. Incident affecting [AFFECTED_FEATURES]. Customers: [CUSTOMER_SEGMENTS]. Channels: [CHANNELS]. Known facts: [KNOWN_FACTS]. Compensation policy: [COMPENSATION_POLICY]. STEPS: 1. Write an initial acknowledgment (within 15 minutes), an update template for every 30 to 60 minutes, a resolution message, a post-incident summary, and an apology-with-compensation message if applicable. 2. Each message states what happened, who is affected, what we are doing, a workaround, and the next update time, with no speculation about cause. 3. Provide a status page entry format and a holding reply for individual tickets. 4. Set rules on tone, accountability wording, and legal review. OUTPUT FORMAT: Message set, status entry format, holding reply, and rules. QUALITY BAR: Honest and specific; never promise a fix time you do not control. Update on schedule even if there is no news. Add a plan for communicating to customers who are affected by the outage but have not contacted support, such as email segmentation by impact, and a template for the internal incident channel announcement. FOLLOW-UP: Ask me how customers learn about incidents today.
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.