Incidents and on-call, simplified.
No context switching. No manual note-taking. Run incidents and manage on-call rotations naturally in Slack.
Start an incident
Kick off tracking with a single command. Optionally set severity (sev1-sev4). Your team is notified instantly.
/incident start [sev2] <incident title>Log updates as you go
Add timeline events as you investigate and resolve. Every update is captured automatically.
/incident status <update>Generate your postmortem
AI analyzes the timeline and generates a clean, structured postmortem document.
/incident postmortemA complete walkthrough
See how Incident/Ops handles an incident from start to finish.
Something breaks. Start tracking immediately.
When an incident occurs, anyone on your team can start tracking with a single command. Optionally set a severity level. Incident/Ops creates a timeline and notifies relevant team members.
Escalate severity if things get worse.
If the impact grows, escalate the severity with a simple command. The severity change is logged in the timeline.
Log updates as you investigate and fix.
As your team works the incident, log updates with simple status commands. Every message is timestamped and added to the timeline automatically.
Resolve the incident.
Once the issue is fixed, resolve the incident. Incident/Ops calculates the duration and preserves the complete timeline.
Generate an AI-powered postmortem.
Request a postmortem and let AI analyze your timeline. Get a comprehensive document with summary, root cause analysis, timeline, and action items—ready to share.
Database timeout caused checkout failures for approximately 23 minutes due to a missing index on the orders table.
Missing index on orders.created_at column caused slow query performance during peak traffic.
- 10:00:00 - Incident started
- 10:05:23 - Identified slow query in orders table
- 10:12:45 - Added index, query time down to 50ms
- 10:23:00 - Incident resolved
- Add monitoring for query performance on orders table
- Set up alerts for database connection timeout
- Review other tables for missing indexes
Create a Jira ticket to track follow-ups.
ProOnce you've resolved the incident and generated a postmortem, create a Jira ticket with a single command. The ticket includes incident details and links back to your Slack conversation.
First time? Configure your Jira connection with /incident config jira
Track your incident trends over time.
ProView analytics to understand your incident patterns. Track MTTR, incident frequency, and severity breakdown to improve over time.
Use /incident list to see recent incidents with severity and duration.
On-call management, built in
Know who's on-call at a glance. Manage rotations and handoffs without leaving Slack.
Check who's on-call instantly.
Anyone on your team can see who's currently on-call with a simple command. No digging through schedules or external tools.
Hand off with a single command.
When it's time to rotate, hand off on-call responsibility instantly. The team is notified and the change is recorded.
View history and analytics.
Track on-call rotations over time. See who was on-call when, how many incidents they handled, and ensure fair distribution.
Page engineers instantly
When incidents happen, get the right people involved immediately. Slack-native paging with optional PagerDuty integration.
Page the on-call engineer instantly.
During an incident, page whoever is on-call with a single command. They'll receive a Slack DM with an interactive Acknowledge button.
Acknowledge via Slack or PagerDuty.
Engineers can acknowledge directly in Slack using the button or command. If you've configured PagerDuty, acknowledgments sync automatically.
Auto-escalate if unacknowledged.
If a page isn't acknowledged within your configured timeout (default 5 minutes), it automatically escalates to the next person in your chain.
Pro tip: Configure /page config pagerduty for phone/SMS alerts via PagerDuty.
Why teams love this workflow
Zero context switching
Stay in Slack where the conversation is happening. No need to open another tool during an incident.
Nothing gets lost
Every status update is automatically timestamped and preserved. Perfect timeline, every time.
Postmortems in minutes
AI generates a complete postmortem instantly. No more spending hours writing up incident reports.