Translate a Technical Incident Report Into a Client-Facing Communication

Something broke, the engineering write-up is all forensic detail, and now the client needs to hear from you. Paste the internal report and this prompt translates it into a client-facing message: empathetic, clear, forward-looking, without the jargon or the defensiveness. Good for anyone in a customer-facing technical role who has to explain an outage without making it worse.

<context>
Technical incident reports are written for engineers; client communications are written for trust. The same event requires two very different documents: one forensic and precise, one empathetic and forward-looking. Translating between them is a critical skill in customer-facing technical roles.
</context>
<task>
Paste your internal incident report or describe the incident: [incident description]. Translate it into a client-facing communication. The client needs to understand: what happened at a non-technical level, how it affected them, what you did to resolve it, and what you are doing to prevent recurrence. They do not need to understand the root cause in technical detail.
</task>
<output_format>
A structured client email with: Subject line, Opening (acknowledge impact without excessive apology), What Happened (two sentences, plain language), How It Affected You (one sentence referring to service disruption without technical detail), What We Did (three to four bullet points of actions taken), What We Are Doing to Prevent Recurrence (two bullet points), and Closing (forward-looking, confidence-restoring). 200-300 words.
</output_format>