How is Runframe different from other tools that integrate with Slack?

Most incident tools send Slack notifications with links back to a web dashboard. Runframe is a native Slack app. You declare incidents, page people, change severity, and resolve without opening a browser. The incident channel is the control room.

Can my team run the entire incident from Slack?

Yes. /inc create opens an incident and creates a channel. /inc page alerts the on-call engineer via DM and email. /inc severity and /inc move change severity and status. /inc resolve closes it. Every action is logged to the timeline automatically.

Does Runframe require Slack admin permissions?

On most Slack plans, any member can install Runframe. If your workspace restricts app installations, an admin approves it once. After that, every team member can use it immediately.

What happens if the on-call engineer does not respond?

Runframe follows your escalation policy. If the primary on-call does not acknowledge within the configured timeout, the next person is paged automatically via Slack DM and email.

Does Runframe create a new channel for every incident?

Yes. Each incident gets a public channel named after the incident number and title. This keeps communication focused and easy to find later.

Can I use Runframe without Slack?

Yes. The web dashboard works standalone for incident management, on-call scheduling, and postmortems. Slack is optional but most teams find it significantly reduces response times.

Do team members need to link their Slack accounts?

No. Runframe matches users by email address during the OAuth connection. If your Runframe email matches your Slack workspace email, DM paging works automatically.

What about postmortems?

When you resolve an incident with /inc resolve, Runframe generates a postmortem draft pre-filled from the incident timeline. Every status change, page, and escalation that happened in Slack is already captured.

What is Slack-native incident management?

Slack-native means the incident workflow runs inside Slack, not alongside it. Instead of getting a Slack notification with a link to a separate tool, you declare incidents, page engineers, update severity, and resolve from slash commands and interactive buttons. The Slack channel is the incident control room.

What Slack slash commands does Runframe support?

Eight commands: /inc create to declare incidents, /inc page @user to page someone, /inc severity to change severity (SEV0 through SEV4), /inc move to change status, /inc assign to assign a responder, /inc update to add a timeline note, /inc resolve to close with a summary, and /inc close to close the incident.

Does Runframe work with free Slack workspaces?

Yes. All incident management features work regardless of your Slack plan. Slash commands, paging, incident channels, and postmortems are all available on free workspaces.

What is ChatOps for incident management?

ChatOps means managing operations through a chat tool like Slack. For incident management, that means declaring incidents, paging on-call engineers, and posting status updates with slash commands instead of switching to a separate dashboard. Runframe is built for this.

How does Slack incident management reduce MTTR?

By removing context switching. Your team is already in Slack. Having incident management in the same place means faster response, immediate visibility, and no time lost navigating between tools. The incident channel becomes the single source of truth.

Incident management
without leaving Slack

Your team already lives in Slack. Runframe is a native Slack app that handles the full incident lifecycle from the channels you are already in. No tab switching, no dashboard hopping.

Start Free Integration Details

Runframe incident management inside Slack showing slash commands, incident channel, and interactive buttons

Not a bot that posts links.

PagerDuty sends you a Slack notification with a link to their web app. OpsGenie does the same. Runframe is a native Slack app built on Block Kit, slash commands, and interactive components. Declare an incident, page the on-call engineer, change severity, and resolve. All from Slack.

What you can do from Slack

/inc commands

Eight subcommands cover the full lifecycle. Create, page, severity, move, assign, update, resolve, close. All from any channel.

Auto-created incident channels

Every incident gets a public channel named after the incident number and title. The right people are invited automatically.

Page on-call via DM and email

/inc page @user sends a Slack DM with incident details and an Acknowledge button. Email goes out at the same time.

Acknowledge and escalate with buttons

Incident messages include Acknowledge and Escalate buttons. One click. No command to remember.

Change severity and status inline

/inc severity SEV1 changes the severity. /inc move investigating changes the status. Every update is logged to the timeline.

Timeline writes itself

Every command, button click, and status change is logged automatically. When the incident resolves, the postmortem draft is already half-written.

The workflow

From alert to postmortem without opening a browser.

1/inc create database-outageIncident channel created, on-call paged

2On-call clicks AcknowledgeAcknowledgment logged, escalation timer stopped

3/inc severity SEV1Severity updated, timeline entry added

4/inc move investigatingStatus changed, team notified

5/inc resolve "connection pool fix deployed"Incident resolved, postmortem draft generated

Frequently asked questions

Your team already lives in Slack. Your incidents should too.

Free plan available. Connect your workspace in under 2 minutes.

Start Free Slack Integration Details

Incident managementwithout leaving Slack