Skip to main content
If you already have an existing Slack app that uses /inc or /incident, installing the incident.io Slack app will take over those commands. This guide walks you through how to install incident.io to use /incident-io instead, to avoid conflicts with existing tooling.

​
Setup

The order matters, so work through these in sequence.
1

Sign in to incident.io with Slack

This is the first step in signing up for incident.io. At this point, please do not install the incident.io Slack app. If you have installed it, you will need to temporarily uninstall it.
2

Tell us your incident.io account ID

After signing in, you’ll be on a URL like app.incident.io/my-company/setup.Send that URL to your account manager, or to support@incident.ioWe will opt your account in to using the alternative /incident-io command, and let you know when to continue.
3

Install the main incident.io Slack app

Once we’ve confirmed you’re opted in to the alternative command, you can continue with account setup by installing our main Slack app.You can use incident.io in Slack, on mobile, and in our web dashboard at this point, but you won’t be able to control incidents via slash commands or shortcuts on messages at this point.
4

Install the alternative slash commands app

To add the /incident-io command to Slack, you’ll need to install a separate Slack app, called Alt commands for incident.io.This app does not request any access beyond adding the slash command. It cannot read or post messages, or take any other actions within your workspace.Go to Settings → Slack channel, find the Slash commands section, and select Add to Slack.
5

Check it's working

Type /inc in any Slack channel, and look at the list of commands Slack suggests.You should see /incident-io from incident.io. You should not see /inc or /incident attributed to incident.io: those will either be gone, or still belong to your other app.Run /incident-io to confirm it opens.

​
FAQs

If someone in IT or security needs to check they’re approving the right thing:The short name is because Slack caps app names at 35 characters. It’s a different app from the main incident.io app, and both need to stay installed.This app isn’t in the Slack Marketplace yet, so searching there won’t find it, and you can’t install it from Slack’s app directory. The Add to Slack button in your incident.io settings is the only way to install it.
Yes, and it works the same way in a single workspace. On Enterprise Grid you can install to a single workspace, or across your entire Grid.You can see and manage which workspace(s) each app is installed in from Settings → Slack channel. The slash command will only work in workspaces where both apps are installed.
One: /incident-io. It replaces both /inc and /incident, and everything the standard commands do, it does. See the command cheatsheet for what’s available.
Yes. Once the other app no longer owns /inc or /incident, the Settings → Slack channel page offers to add them back to the main incident.io app. That’s a reinstall of the main app, nothing destructive, and /incident-io keeps working while it happens.You can later uninstall the alternative commands app if you’re no longer using /incident-io. There is no interruption in service.
Only what you send it. Its single Slack scope is commands, which means Slack contacts it when someone runs one of its commands and at no other time. It can’t read your messages. It has a bot user because Slack requires one before it will accept slash commands, but we never use it: the work is all done by the main incident.io app.
Yes, from Settings → Slack channel. Turn a command off and set the message we reply with when someone uses it. At least one command must stay enabled.