Create and List Incidents via Slack
How To: Create and List Incidents via Slack
Slack Agents allow teams to retrieve incident information and create new incidents directly from Slack using natural language interactions.
Instead of switching between Slack and the Exemplar console, responders can list active incidents, review status and severity, create new incident records, and confirm incident details from the same collaboration workspace.
This helps teams coordinate faster during operational events while keeping incident communication close to where response discussions already happen.
List incidents
Slack Agents can retrieve active or existing incidents and display key details directly in Slack.
Typical incident information includes:
- Incident title
- Current status
- Severity
- Priority
- Created time
- Affected services or context
- Expanded incident details using Show more
This allows responders to quickly understand ongoing incidents and prioritize operational work without leaving Slack.
Create an incident
Slack Agents can guide users through the incident creation process by collecting required incident details before creating the record.
Typical incident information includes:
- Incident title
- Status
- Severity
- Priority
- Operational context
- Affected service or issue description
Before creating the incident, the agent presents a generated incident configuration for review.
Slack Agents ask for confirmation before creating incidents so users can review key details and avoid accidental operational records.
Review and confirm incident details
Before an incident is created, the agent provides a summary of the proposed incident configuration.
This allows users to:
- Verify the incident title
- Review status, severity, and priority
- Confirm operational context
- Expand details with Show more
- Update values before final creation
Once confirmed, the incident is created and added to the organization’s incident inventory.
Operational benefits
Using Slack Agents for incident management helps teams:
- Reduce context switching during response
- Retrieve incident details faster
- Create incidents from ongoing Slack discussions
- Improve collaboration during operational events
- Keep incident status visible to responders
- Confirm newly created incidents immediately
Best practices
- Use clear and descriptive incident titles
- Review severity and priority before confirmation
- Expand incident details when more context is needed
- Confirm incident configuration before creation
- Keep Slack incident discussions aligned with the created incident record