Everything you need for better incident response

From on-call rotations to incident response to the final postmortem, Incident/Ops captures what matters and helps your team learn from every incident.

Simple Slack Commands

Start, update, and resolve incidents with intuitive slash commands. No training required—your team can start using IncidentOps in seconds.

• /incident start [sev] - Begin tracking
• /incident severity - Change severity
• /incident status - Log updates
• /incident resolve - Close incident

Automatic Timeline Capture

Every update is timestamped and organized automatically. Never miss a detail during the chaos of an incident.

• Precise timestamps for all events
• Automatic duration tracking
• Chronological event ordering
• No manual note-taking needed

AI-Powered Postmortems

Generate comprehensive postmortems with root cause analysis, action items, and lessons learned—all with a single command.

• Intelligent root cause analysis
• Automatic action item suggestions
• Lessons learned extraction
• Blameless language by default

System of Record

All incidents are persisted and searchable. Build institutional knowledge over time and never lose incident context.

• Searchable incident database
• Full timeline preservation
• Historical trend analysis
• Knowledge base building

Export to Markdown

Share postmortems in your wiki, docs, or anywhere else. One-click export to Markdown format.

• Clean Markdown formatting
• Compatible with any wiki
• Copy-paste ready
• Preserves all incident data

Channel-Based History

View past incidents by channel. Spot patterns and recurring issues across your infrastructure.

• Per-channel incident views
• Pattern recognition
• Recurring issue detection
• Team-specific insights

Severity Tracking

Set severity levels when starting incidents and adjust them as the situation evolves. Prioritize response based on impact.

• /incident start sev2 - Start with severity
• /incident severity sev1 - Escalate severity
• Supports sev1, sev2, sev3, sev4
• Severity shown in list view

Incident Analytics

Get insights into your incident trends. Track mean time to resolution, incident frequency, and severity breakdown.

• /incident analytics - 30-day overview
• /incident analytics 7 - Weekly stats
• MTTR tracking
• Severity breakdown

Incident List

Quickly view recent incidents in your workspace with severity levels and duration at a glance.

• /incident list - View recent incidents
• Shows severity levels
• Displays incident duration
• Quick status overview

Jira Integration

Connect your Jira instance and create tickets directly from Slack. Track incidents in your existing project management workflow.

• /incident config jira - Configure your Jira
• /incident ticket - Create ticket instantly
• Links tickets to incidents
• Works with any Jira project

On-Call Management

Know who's on-call at a glance. Track rotations, handoffs, and keep your entire team informed—all from Slack.

• /oncall - View current on-call
• /oncall @user - Set on-call engineer
• /oncall history - View rotation history
• Automatic team notifications

Instant Handoffs

Transfer on-call responsibility in seconds with a simple command. The whole team is notified automatically.

• One-command handoffs
• Tracks who made changes
• Records shift durations
• Full audit trail

On-Call Notifications

Configure channels to receive on-call updates. Never miss a rotation change or handoff.

• /oncall channel #channel - Set notifications
• Automatic rotation announcements
• Keep team informed
• Works with any channel

On-Call Analytics

Get insights into your on-call rotations. Track incidents per engineer, rotation frequency, and on-call hours.

• /oncall analytics - 30-day overview
• /oncall analytics 7 - Weekly stats
• Incidents per rotation
• Fair workload distribution

Slack-Native Paging

Page engineers via Slack DM with an interactive Acknowledge button. No external tools needed for basic paging.

• /page @user - Page specific user
• /page oncall - Page on-call engineer
• Interactive Acknowledge button
• Full acknowledgment tracking

Auto-Escalation

Automatically escalate unacknowledged pages to the next person in your escalation chain after a configurable timeout.

• /page config escalation @user1 @user2
• /page config timeout 10
• Checks every 60 seconds
• Escalates until acknowledged

Auto-Page on Incident

Automatically page the on-call engineer when incidents of configured severity levels are started.

• /page config autopage sev1,sev2
• No manual paging needed
• Critical incidents get attention
• Works with severity system

PagerDuty Integration

Connect PagerDuty for phone calls and SMS alerts. Acknowledgments sync automatically via webhook.

• /page config pagerduty
• Phone and SMS alerts
• Webhook for ack/resolve sync
• Works alongside Slack pages

Built for the way engineers actually work

IncidentOps integrates seamlessly into your existing Slack workflow. No context switching, no separate dashboards, no training required.

Works in any channel

Run incidents in your existing channels or create dedicated incident channels—Incident/Ops adapts to your workflow.

Familiar interface

If your team uses Slack, they already know how to use Incident/Ops. No learning curve, instant productivity.

Real-time collaboration

Multiple team members can contribute to the timeline simultaneously. Everyone stays in sync.

Incident lifecycle in Slack

$/incident startsev2API latency spike

→ Incident #243 started (SEV2)

$/incident statusRestarted service, latency normalizing

→ Timeline updated (14:45:22)

$/incident resolve

→ Incident #243 resolved (18m)

On-call management

$/oncall

→ Current on-call: @sarah (since 2h ago)

$/oncall@mike

→ On-call updated to @mike

$/oncall history

→ Last 5 on-call rotations

Paging & escalation

$/page oncallDB is down

→ Paging @sarah (on-call)...

$/page ack

→ Page acknowledged

$/page status

→ 1 active page (acked), 0 pending

Ready to improve your incident response?

Join engineering teams who trust Incident/Ops to capture, learn, and improve.