Ensure Every Team Learns from Every Incident

1. Read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sending domain for the sender. 2. In PagerDuty, use an incident webhooks subscription for resolved incidents, then use the PagerDuty REST API to read the incident, service, responders, teams, notes, and timeline/log entries. 3. For each resolved major incident, compile a concise postmortem distribution package: executive summary, customer impact, root cause, contributing factors, remediation items, owners, due dates, and links to the full report. 4. Identify affected recipients from PagerDuty service ownership, escalation policies, responder teams, and stakeholders mentioned in notes; create separate email drafts for executives, engineering teams, support, and customer-facing teams with detail levels appropriate to each audience. 5. Run MultiMail in gated_send mode: compose the emails and hold them for engineering review before sending. Ask me only for PagerDuty credentials, brand voice, approved sender identity, and final go-live approval.

1. Read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sending domain for the sender. 2. In Jira Service Management, trigger this from an Automation rule when an Incident issue transitions to Resolved or Done, or from a Jira webhook for issue updated events filtered to incident resolution. 3. Use Jira issue data, comments, linked issues, components, affected services, assignees, reporters, labels, and resolution fields to summarize the incident, cause, impact, timeline, follow-up work, and open risks. 4. Build recipient groups from affected service owners, component owners, linked project teams, watchers, assignees, and stakeholders in the incident comments; draft tailored distribution emails for engineering, product, support, leadership, and any impacted operations teams. 5. Run MultiMail in gated_send mode: compose and schedule the distribution only after the incident owner approves the drafts. Ask me only for Jira credentials, brand voice, approved sender identity, and final go-live approval.

1. Read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sending domain for the sender. 2. In ServiceNow IT Service Management, trigger this from a Flow Designer flow or Business Rule when a Major Incident or Incident record is closed or resolved, then read the incident record, work notes, comments, related tasks, affected configuration items, assignment groups, and problem record if one exists. 3. Compile a postmortem summary with severity, business impact, affected services, timeline, root cause, workaround, permanent fix, corrective actions, owners, due dates, and links to the full ServiceNow record or post-incident review. 4. Identify distribution lists from assignment groups, affected CI owners, business service owners, major incident stakeholders, related task owners, and problem management participants; draft audience-specific emails with sensitive infrastructure detail minimized outside engineering groups. 5. Run MultiMail in gated_send mode: compose the emails and require engineering or incident management approval before any send. Ask me only for ServiceNow credentials, brand voice, approved sender identity, and final go-live approval.