Quickstart
Create your first incident in 5 minutes.
Prerequisites
Before you begin, make sure you’ve installed the Runframe Slack app and are signed in.
Creating incidents from Slack
Step 1: Create the incident
In any Slack channel, run:
/inc create
A modal will appear asking for:
| Field | Description |
|---|---|
| Title | Brief summary (e.g., “API latency spike”) |
| Severity | P0 (critical) through P4 (minor) |
| Description | What’s happening, symptoms observed |
| Affected Services | Which services are impacted |
| Customer Impact | Is this affecting customers? |
Step 2: Assign responders
Runframe automatically suggests the on-call engineer for the affected services. You can:
- Accept the suggestion
- Assign a different person with
/inc assign @username - Assign an Incident Lead and Communications Lead for larger incidents
Step 3: Track the incident
Runframe creates a dedicated incident channel (named inc-YYYY-MM-DD-###) and posts:
- Incident summary with severity badge
- Assigned responders
- SLA deadlines (acknowledgment and resolution)
- Live updates as status changes
Step 4: Post updates
As you investigate, keep everyone informed:
/inc status investigating
/inc status identified
/inc status monitoring
Each status update posts to the incident channel and updates the dashboard.
Step 5: Resolve
When the incident is resolved:
/inc resolve
Runframe will ask for a brief resolution summary and prompt you to start a postmortem.
Creating incidents from the web dashboard
Step 1: Navigate to Incidents
- Go to app.runframe.io
- Click Incidents in the sidebar
- Click New Incident
Step 2: Fill in incident details
Complete the incident form:
- Title and description
- Severity (P0–P4)
- Affected services
- Incident roles (Lead, Comms lead, Operations lead)
- Customer impact flag
Step 3: Create and notify
Click Create Incident. Runframe will:
- Generate the incident number (e.g., INC-001)
- Create a Slack channel
- Notify assigned responders
- Set SLA deadlines
Step 4: Manage from the dashboard
From the incident detail page, you can:
- Update status and severity
- Add and remove responders
- Post updates visible in both dashboard and Slack
- View SLA countdown and escalation status
- Attach related incidents as duplicates or dependencies
Step 5: Resolve and postmortem
Click Resolve Incident when done. You’ll be prompted to:
- Provide a resolution summary
- Start a postmortem document (PM-###)
- Track action items from the incident
What just happened?
You created your first incident. Here’s what Runframe set up for you:
| Feature | What it does |
|---|---|
| Incident number | Unique ID (INC-###) for tracking and reference |
| Slack channel | Dedicated inc-YYYY-MM-DD-### channel for coordination |
| SLA deadlines | Automatic acknowledgment and resolution targets based on severity |
| Assignment | Notified responders and suggested on-call engineer |
| Audit trail | Every status change, assignment, and update is logged |
| Postmortem prompt | Automatic nudge to capture learnings |
Next steps
You’ve created an incident. Now configure Runframe for your team:
Configure rotations so Runframe knows who to page when incidents occur.
Define what happens when SLAs are breached or responders don’t acknowledge.
Integrate Datadog, Sentry, or Prometheus to auto-create incidents from alerts.
Define what P0–P4 means for your organization and set SLA targets.
Need help?
- Slash Commands – All
/inccommands - Incident lifecycle guide – Deep dive on incident management
- Join our Slack community – Ask questions and share feedback