Easy integration & configuration

• Tired of incident response bots with hours of set up on process automation? Us too. You can get set up and start using our bot in minutes, without having to pre-program response automation
• But you can customize things at a workspace level:

• Default broadcast channels
• Status update reminder intervals
• Incident Commander & Communications Lead role descriptions

Flexible to fit each incident

• Incidents often don’t follow the same path every time. Without automation locking you into a specific workflow, you can:

• Change which channels get broadcast messages throughout the incident
• Update the severity, roles, and stages at any time

• The bot will prompt you to add some context to what led to your changes, to help inform stakeholders and give you a record free of hindsight bias for your incident review.
• Our stages are simple: Investigating, Identified, and Mitigated. Having an understanding of “where we are within the incident” breaks the incident into smaller chunks and helps responders, both within engineering and on the customer communication side, to reorient themselves around what new tasks they may be expected to perform in the next stage.
• There is no single path to resolution. You can easily move back and forth between the stages as you gain new information and pivot your response.

Here to make your life easier

• Convert an existing Slack message from any channel into a status update with just an emoji, or use our message shortcut.
• Set reminders for things you wanted to look into after the incident, then decide upon mitigation what to do with them.

Combine our free bot with a free trial of Jeli incident analysis

• Our bot for Slack turns each incident into an archived Opportunity in Jeli that can be annotated later.
• Cross-incident analysis of Opportunities leads to new discoveries and insights.