Product roadmap

Product roadmap

The Future 🔮
Private incident channels
Some incidents, such as security related incidents, should not be public to everyone in the organisation. You should be able to declare a private incident that's only visible to the people you want to be involved.
Automatically create incidents from alerts
Many companies will always create an incident after a specific alert fires. Let's save you some clicks by automatically doing that from your alerting provider of choice.
Custom nudges and actions
Right now, we nudge you for a few different things such as setting a lead, or prompting you to update the status page. However, you might want to add your own process in here: for example, reminding people to take a break after 2 hours, and swap roles. Let's make it easier for people to set their own nudges.
Default actions
Creating a set of actions to complete at the start of every incident: for example, assess the impact, update the status page, and so on.
Subscribing to incidents
Right now, we work on a pull model: you need to go to the incident to understand what is happening. It'd be nice if we could reverse that so you could subscribe to updates on a particular incident (e.g. by SMS), or all incidents, with some criteria (email me whenever there's an incident that affects Payments).
Live-refresh the incident homepage
It's very 2005 that you have to refresh the homepage by hand. If you don't, you might be operating on stale data. Let's get some real-time streaming happening so you're always seeing the latest state of the incident.
Next Up 👀
API and webhooks
They're your incidents. We should be able to tell you about them as soon as they happen, when interesting updates occur to them, and allow you to fetch data so you can build whatever custom integrations you like.
Improving Insights
We built a first version of Insights, but it could be a lot more powerful! We'll spend some time adding metrics like MTTR, MTTD, and breaking things out by your custom fields.
Doing 👷🏽‍♀️
We're going to make it so you can connect applications and fully automate your incident response process using, to make it even easier for your team. For example, sending an email to your executive mailing list, and paging an incident manager when the severity is set to Critical.
Add video-conferencing integrations
Right now, you have to handle your own calls. Wouldn't it be nice if we started a call for you, recorded it, and attached it to the incident? Yes, it would.
Done ✅
Search, filter and sort incidents
Right now, our incident search page is quite primitive. Let's upgrade it and make it so you can slice, dice, sort and filter incidents every which way.
Custom Fields
Define and set your own fields on incidents, like systems, products and number of customers affected. You can then ensure these are collected before an incident is closed, and use them in postmortems, Insights and search.
Custom incident roles
Define and set your own roles for incidents, like communications lead, or incident response manager, and have help fill them for you.
Right now, we don't do a great job of onboarding you, teaching you how to use the product, and helping you set up a great way to respond to incidents. Let's make that better!
Statuspage integration
You're in an incident, and things have taken a turn for the worse. It's time to let your customers know through your status page. First, you need to find the login. Next you need the text. And finally you need to mess with the myriad of settings. We can streamline this by bringing status page updates into Slack. No more login pain, customisable template messages, and lightning fast updates that keep pace with your incident response.
Attach a postmortem to an incident
Right now, our postmortem export is a little hacky. Some people might not use Google Docs. Let's copy the document to your clipboard, and allow you to set a postmortem document link on the incident.
Better modelling of incident states
Model the incident as a more granular series of states than "open" and "closed". We know it's not perfect, and we can't wait to fix it. This will also lay the foundation for lots of metrics that we want to expose like MTTD and MTTR.
Exporting actions to an issue tracker
Allow you to export actions from an incident to an issue tracker like JIRA, and for have track when they've been completed. We can then provide statistics on how long it takes you from having an incident, to all actions being completed, and alert if that isn't within some SLA.
Quickly understand the impact of your incidents in aggregate, and provide a home for iteration as we release other features which would make the insights we provide richer.
Making the bot quieter
The bot can be a little loud in the incident channel, which makes it harder to scan. Let's give you the option to make it quieter, if that's what you want.
Allow you to page people directly within the incident channel and escalate to other teams. We'll start with PagerDuty, and then add other providers like Opsgenie and VictorOps.