Run incidents without leaving Slack
Tailored to your organization for smarter incident management
Confident, autonomous teams guided by automations
Learn from insights to improve your resilience
Build customer trust even during downtime
Connect everything in your organization
Streamlined incident management for complex companies
Run incidents without leaving Slack
Tailored to your organization for smarter incident management
Confident, autonomous teams guided by automations
Learn from insights to improve your resilience
Build customer trust even during downtime
Connect everything in your organization
Streamlined incident management for complex companies
Sometimes you might want to schedule a debrief meeting after your incident has been resolved, to regroup and discuss what happened. We already help by pre-filling a Google calendar event with important information, but you can now decide which users should be invited to that event.
For example, you might want the incident responders to always be invited, but additionally include senior leadership if it’s a critical incident. You can make this as complex as you like with the power of expressions, for example we can invite engineering@incident.io
if the incident is one type, or customersuccess@incident.io
if it’s another.
We already let you define policies about your follow-ups and post-mortems, and we’re now extending this to debriefs. If it’s crucial that your critical incidents always invite senior leadership, or that the debrief is scheduled a certain number of days after the incident is resolved, you can now bake that logic in to your configuration. If a debrief violates your policy, we can let the debrief organizer know that they need to update the event.
It’s now possible to filter the incidents that have a debrief, by choosing “Has debrief” from the incidents list page. If this is an important view for you, you can always hit “Save view” to make it available to everyone in your organisation.