Incident status update drafts for stakeholders
During an incident, an agent drafts regular status updates from the incident channel so the commander can edit and send them.
DifficultyBeginner
Setup time1-2 hours
CategoryIT & DevOps
The use case
Incident commanders are expected to fix the problem and also keep executives, support and customers informed. PagerDuty's AI agents surface key information from the incident and draft status updates to keep people in sync. The commander edits the draft, checks it does not reveal internal details or promise a fix time the team cannot meet, and sends it. Internal updates can go out with light review, but anything shown to customers, such as a status page post, always needs a person to approve the wording.
Example workflow
- Agent watches the incident channel and timeline
- Agent drafts an update at a set interval
- Commander edits for accuracy and tone
- Commander sends internal updates
- A person approves any customer-facing status page post
Tools
- PagerDuty
- Slack
Risks and guardrails
- Drafts can include internal details not meant for customers
- Agent may state a cause before it is confirmed
- Never auto-publish to a public status page
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- PagerDuty: AI agents: www.pagerduty.com/platform/ai-agents
- PagerDuty MCP server (official page): support.pagerduty.com/main/docs/pagerduty-mcp-server-integration-guide (checked 2026-11-09)
- Slack MCP server (official page): docs.slack.dev/ai/slack-mcp-server (checked 2026-11-09)