Runframe
Guides

Guides

Runframe guides covering Slack integration, slash commands, incident channels, and best practices for incident management.

Slack Integration

Runframe lives where your team works - right in Slack.

Slash Commands

Creating Incidents

/inc create

Launches an interactive modal to create a new incident. You can also pass a title directly:

/inc create Database connection pool exhausted

Updating Status

/inc move investigating
/inc move identified
/inc move monitoring

Update the current incident's status. Works in incident channels (auto-detects incident) or with an explicit incident number:

/inc move INC-123 investigating

Posting Updates

/inc update Deployed hotfix to prod-3

Post a narrative timeline update without changing the incident status.

Changing Severity

/inc severity critical
/inc severity SEV1

Supports both friendly names (critical, high, medium, low, pre-emptive) and SEV notation (SEV0-SEV4).

Assigning Responders

/inc assign @username

Assign a responder to the current incident.

Resolving Incidents

/inc resolve Fixed race condition in payment service

Resolves the incident with a summary (minimum 10 characters). Prompts for postmortem creation.

Closing Incidents

/inc close

Archives the incident channel after resolution and follow-up is complete.

Paging On-Call

/inc page
/inc page @username
/inc page oncall
/inc page api-backend

Page the on-call engineer, a specific person, or the team responsible for a service.

Incident Channels

When an incident is created, Runframe automatically:

  1. Creates a dedicated Slack channel
  2. Names it using the pattern #inc-00042-title-slug
  3. Invites relevant team members
  4. Pins important information

Channel Features

  • Automatic updates: Status changes are posted automatically
  • Timeline: All actions are logged in the channel
  • File sharing: Attach logs and screenshots directly
  • Threaded discussions: Keep conversations organized

Best Practices

  1. Keep the incident channel focused - Use threads for side discussions
  2. Document decisions - Use /inc update for narrative context and /inc move for status changes
  3. Share context early - Link to relevant logs and dashboards in the first message
  4. Close the loop - Always post a resolution summary with /inc resolve