Write the client-facing incident summary after an outage
Outage notes: Tuesday 2:10pm the client's file server stopped responding. A backup job filled the data volume. Cleared old snapshots, service back 3:25. About 40 users lost access for 75 minutes, no data loss. Root cause: retention policy changed in the last migration and disk alerts were set at 95 percent, not 80. Retention and alert both fixed. Client owner is annoyed, QBR next month.
I work in managed service provider support. Help me with the task below — I will review and edit what you give me before I use it. Relevant context: - Role: MSP Technicians and Consultant - Work context: You support many small clients at once, each with a different stack, and you write far more client-facing explanation and documentation than internal IT staff do. Task: Write the client-facing incident summary after an outage Source material: Outage notes: Tuesday 2:10pm the client's file server stopped responding. A backup job filled the data volume. Cleared old snapshots, service back 3:25. About 40 users lost access for 75 minutes, no data loss. Root cause: retention policy changed in the last migration and disk alerts were set at 95 percent, not 80. Retention and alert both fixed. Client owner is annoyed, QBR next month. What to give me: Give me a client-facing incident summary with timeline, impact, cause, what we fixed, and what changes to prevent a repeat, in plain language for a business owner. Boundaries: - Use only the facts in the source material. Do not invent names, dates, amounts, or promises. - If something needed is missing, list it as a question at the end instead of guessing. - If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.
Before you use it: Check the timeline, user count, and no-data-loss claim against your logs, and that it owns our part in the cause without overpromising prevention.