incident.io helps all of the tools you use work better, together.
From issue trackers to on-call management, we're adding new providers every day. Use something to help with your incidents which isn't on our list? Let us know!
Supported Issue Trackers
Supported Escalation Tools
Supported Video Conferencing
- Google Meet
Supported Editors (for postmortems)
- Google Docs
- Confluence (+ Jira)
Every company has a slightly different setup when it comes to severities. At incident.io, we use
Critical and these are the defaults you're provided with our of the box.
However, you can easily customise them to suit your needs. Head on over to https://app.incident.io/settings/severities where you can change how they're referred to them and the descriptions, too, so if you use P1, P2 or SEV1, SEV2, we've got you covered.
Adding a default call URL
Instead of setting up a call for each incident, you can leave a permanent call running that you can dial into. If you set that for incident.io, we'll automatically attach it to every incident you create.
Setting your Slack channel prefix
As you might know by now, we'll create you a Slack channel for every incident. Have particular naming conventions to your Slack channels that you want to stick to? No problem. Choose from multiple different prefixes to match your style.
Got a prefix that you'd like to see supported? Let us know!
Customising Incident Documents
Once an incident is over, you'll want to put together an incident document to summarise what happened and help you run a debrief session. You may already have a template your team follow, with prompts and sections that work for you, in which case, no problem!
We have a few preset sections you can choose to include (or disable) and you can add your sections of arbitrary content, too.
Roles are 'hats that you can wear' during an incident, like the 'Incident Commander', or the 'Communications Manager'. They help break up responsibilities during an incident, so it's clear who needs to pick up what, and when.
You can add the roles that best suit your organisation and process by heading to the Incident Roles tab on the Settings page.
We'd recommend spending time writing some good instructions and linking out to relevant docs. Whenever someone is assigned to a role, we'll send them these instructions so it's clear what they need to do.
Custom Fields 🆕
Custom Fields are a way for you to define the data that you want to collect on your incidents, and have incident.io collect it for you before, during or after an incident.
Collecting this data is really useful! It allows you to collect high quality data about your incidents that reflect your process, makes for clearer communication
We'll be connecting Custom Fields with Insights, and richer filtering and searching of your incidents very soon. Watch this space!
Here's a few examples of useful Custom Fields that we commonly see:
- 'System Affected', which would let us collect which systems were affected on our incidents. We then enter our systems as an option to choose from.
- 'Type', to reflect whether this is a Platform incident, Security incident, or HR incident.
- 'Team', which denotes which team
However, it's entirely up to you which fields you create. The only limit is your imagination..
Right now, we support:
- Select: selecting a single value from a drop-down list
- Multi-select: selecting multiple values from a drop-down list
We'll shortly support collecting text values, and number values.
To learn more and get started, head to the Custom Fields section of your Settings page.