Loading

Support incident postmortem

The customer-facing postmortem, drafted from the war room before anyone forgets.

10 minOperationsClaude Cowork
Loading

Set up

Connect your tools

Claude is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access.

Add a connector for each tool you want Claude to use.

Slack
Read the war-room channel end to end and pull every status update, decision, and timestamp.
Connect
Zendesk
Pull every ticket opened during the impact window, with the customer's own words.
Custom connector
GitHubOptional
List the deploys and merged changes in the 24 hours before the incident started.
Connect

Set your working folder

Drag the files you'll use (your customer-postmortem template, an export of the war room, the ticket CSV) into one folder and give Claude access to it in the Claude desktop app. Claude reads the template from there and writes the draft back to it. Create a project from that folder so the template stays attached.

Support / Incidents / INC-4417
customer-postmortem-template.mdFeb 3, 20263 KB
tickets-2026-04-24.csvApr 25, 202662 KB
war-room-export.txtApr 25, 2026340 KB
In Cowork’s chat bar:Support / Incidents / INC-4417

The prompt

Copy this into Claude

Draft the customer-facing incident review for INC-4417. Pull the war-room thread, tickets from the impact window, deploys from the prior 24 hours, and direct customer quotes. Reconstruct the timeline, quantify how many customers were impacted and for how long, and write the first cut in our template with recommended remediation owners.

Support / Incidents / INC-4417

Why this works

Prompt

Name the audience up front. The register changes; this is the doc your CSMs forward, not the engineering retro.

Prompt

Quantify the impact. "How many, for how long" forces a number you can put in the SLA-credit conversation.

Prompt

Ask for direct quotes. The affected-customer voice is the part leadership pays attention to; ask for it explicitly.

Prompt

Set a time range. Tickets and deploys are bounded by the incident timestamps, so the suspect list is short and relevant.

Get a better draft

Practice

Separate internal from external. Add "write an internal appendix with the suspect deploys; keep the customer doc to impact and remediation" so one run produces both.

Practice

Add an example to match. Drop a past review you were proud of in the folder and Claude matches the structure and the apology tone your brand uses.

Make Claude work for you

Tell Claude your own rules for this task, such as your tone guide and your SLA-credit language, then save what you've done as a skill of your own. A few minutes of conversation and it runs with your standards from then on.

Make what we've done in this task so far into a skill called /incident-review.

Support / Incidents

Review the skill, and save it if Claude hasn't already.

Make it repeatable

Run it when the war room closes

The customer doc should exist before the first CSM asks for it. Ask Claude to set up a scheduled task, or open Scheduled in the sidebar, and /incident-review runs each weekday on newly closed war rooms and writes the first cut.

Set up a scheduled task for every weekday at 9am: check for any #inc- channel marked resolved in the last 24 hours, run /incident-review on it, and write the draft to Support/Incidents/<incident-id>/customer-review.md.

Support / Incidents
Scheduled taskActive
Customer incident-review draft

Each weekday at 9am, finds war rooms resolved in the last 24h, runs /incident-review on each, and writes the customer-facing draft to the incident folder.

Every weekdays at 9:00amOpen in Claude

To use a folder on your computer during a scheduled task, keep your computer on and awake with the Claude desktop app open so Claude can access it.

Share with your teammates

Your /incident-review skill now carries your template, your tone guide, and your SLA-credit language. Share it so every incident gets the same customer doc, whichever support lead was on shift.

What changes after an incident

The customer-facing incident review is drafted from the source record with impact quantified and remediation assigned — ready to edit and send rather than write from scratch.

You did this for one incident. The same approach covers internal retros, status-page updates, and SLA-credit summaries — each one becomes a skill your team runs the same way.

Next: Turn the thread into a decision doc