If you forget any specific Jeli Slackbot commands, you can enter /jeli and we’ll prompt you with our most common commands.

Run /jeli help in any Slack channel where you've added the Jeli Slackbot to see a list of available commands. The bot's response will be an ephemeral message that is only visible to you. The command /jeli help is contextual, meaning it will suggest different commands depending on whether you’re in an incident channel (i.e., in the middle of incident response) or trying to import data from other Slack channels. You can expand the message to see a list of all commands.

Initiate incident response with a single command. Include the available information about the incident in the Add More Details section, and utilize any configured integrations in the Use Integrations section.

Note: No field is required, if you do not add a name we will generate one for you from a randomized list of adjectives and nouns.

We’ll send you an ephemeral message confirming the incident has been created with a link to the generated slack channel. We’ll also notify your selected broadcast channels that an incident has been created.

Add More Details

Every field in this section is optional, just add what you know now such as the:

• Summary
• Severity
• Add or remove relevant Broadcast Channels
• Assign yourself to a role within response

All of these fields are editable during response as well through various slash commands.

Use Integrations

Your Jeli Settings and Integrations will determine the default selections on this page and can be changed on a per-incident basis here, including:

• Automatically initiate a Zoom call
• Automatically initiate a Google Meet call
• Create a Primary Jira Jira ticket when the Jeli incident opens
  • More information about creating Jira tickets from Jeli here
  • Note: Using the Primary Jira ticket integration does change the naming scheme of the incident channels.

Incident Channel Naming

• When an incident is created the generated Slack channel name will follow this format: #jeli-[incident number]-[incident name], e.g., #jeli-29-docs-pages-are-down.
• If you elect to have a primary Jira ticket automatically created, it will add the Jira ticket number as a prefix on the channel name as opposed to the #jeli- prefix: #[jira ticket project and ticket id]-[incident name], e.g., #inc-133-payroll-is-down.
• If you do not add a name we will generate one for you from a randomized list of adjectives and nouns and the channel name will get the #jeli- prefix or the Jira ticket prefix based on your configurations, e.g., #eng-34-full-lemon.
• To distinguish demo incidents from actual events, the naming differs: #jeli-demo-[incident name]-[YYYY-MM-DD], e.g., #jeli-demo-just-testing-2023-06-20.
• If Jeli is currently undergoing an incident of our own impacting incident creation, we have fallbacks in place which will change the name format to: #jeli-[incident name]-[YYYY-MM-DD], e.g., #jeli-emails-are-delayed-2023-06-21.

Aliases: /jeli incident, /jeli open-incident, /jeli start, /jeli start-incident

Type what you know about the issue so far and update it when anything significant changes.

The summary is the main description of the incident. It is displayed in the overview responders can use to get up to speed in the incident channel. As well as in the incident notification sent to the broadcast channels, where those not involved in active response can stay up to date on the status of response.

To quickly update the status without opening a dialog box use /jeli summary [type out summary before hitting enter].

Aliases: /jeli update-summary

Select from the severity options of 0, 1, and 2, provide some in the moment context behind your decision and customize the broadcast based on the severity. Severity is not required and can be disabled by request.

To quickly set the severity without opening a dialog box use /jeli severity [severity level number].

Aliases: /jeli severity, /jeli set-severity

Select to assign anyone in Slack as the main point of contact for incident coordination. Anyone can use this command in the incident channel to claim or pass off the incident commander responsibilities.

When an incident commander is set, we update the role in the overview and broadcast channels. We also ping the assignee in the incident channel with the role prompt configured in settings, and DM them the same prompt for easy reference.

To quickly assign without opening a dialog box use /jeli incident-commander [@username|me].

Aliases: /jeli incident-commander, /jeli set-ic

Select to assign anyone in Slack as the main point of contact for incident communication. Anyone can use this command in the incident channel to claim or pass off the communication lead responsibilities. When a communications lead is set, we update the role in the overview and broadcast channels. We also ping the assignee in the incident channel with the role prompt configured in settings, and DM them the same prompt for easy reference.

To quickly assign without opening a dialog box use /jeli communications-lead [@username|me].

Aliases: /jeli communications-lead, /jeli set-cl

Compose an update regarding the incident's current status to be shared in the incident channel and appended to the update thread in broadcast channels. The status field has a limit of 240 characters.

To quickly update the status without opening a dialog box use /jeli status [type out status message before hitting enter].

Hover over a Slack message and select Set incident status to convert the message into a status update.

Or react to a message with the 📣 :mega:, 📌 :pushpin:, or 📫 :mailbox: emoji to turn any message in the incident channel into a status update.

Aliases: /jeli status-update

Incidents often don’t follow the same path every time. Throughout response you can change the stage of the incident as you gain new information and pivot into different efforts.

The bot will prompt you to add some context to what led to those changes, to help inform stakeholders and give you a record free of hindsight biases for your incident review.

Jeli incident stages are: 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, orient 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 adjust your response.

Create followups to remind yourself or others what to work on once impact is mitigated.

You can view them anytime with /jeli reminders.

To quickly create a followup without opening a dialog box use /jeli remind [me or @user] [type out follw up before hitting enter].

Add multiple links to the overview of the incident, such as quick access links to an incident video call, reference document, and relevant dashboards. Use the Display Text field to describe what’s being linked.

Aliases: /jeli add-link

Create new Jira issues and link existing issues. For more information see our docs on:

• Creating/linking additional incident tickets
• Jira integration

Use Jeli’s Statuspage Integration integration to share regular updates on your company’s status page to keep stakeholders and customers informed during an incident.

Enter /jeli overview in the Slack incident channel to receive a full overview of the current incident. The message is only visible to the person that runs the command. The overview will also be automatically shown to anyone who joins the incident channel for the first time (it will only be visible to the individual who has just joined).

The incident overview is also what is visible in the broadcast channels and includes:

• Incident Title
• Incident Stage
• When the incident was opened
• Incident Severity
• Link to the incident Slack channel
• Summary
• Assigned Incident Commander
• Assigned Communications Lead
• Added Links
• The most recent status update

Aliases: /jeli info

Enter /jeli history to display the most recent status update first and a list of the entire status history in reverse chronological order. It is shown in the incident channel but is only visible to whomever runs the command.

The full list of status updates is also visible in a thread under the message containing the incident overview in the broadcast channels.

Aliases: /jeli status-history

Entering /jeli reminders displays the full list of followups created during the incident. It is shown in the incident channel but is only visible to whomever runs the command. From here you can edit followups and mark them as done.

Aliases: /jeli followups, /jeli list-followups, /jeli followups-list

Displays all active incidents using the Jeli Slackbot in your Slack workspace. This command is helpful for when you’re not sure if someone’s already opened an incident for an issue, if you’re tracking multiple incidents at a time, or even to find your way back the the appropriate Slack channel.

This command is most handy when you are joining an active incident channel, or are participating in an incident and want to catch-up on the latest happenings. Jeli will use the status updates in the incident channel to create an AI-summarized writeup of what's happened so far.

Aliases: /jeli ketchup

Page those who are on-call or additional responders using /jeli page. This will trigger the workflow that you set up in your on-call platform, e.g., PagerDuty.

When moving the incident to the mitigated stage, we also create a Jeli Opportunity for when you’re ready to begin your incident review. After you provide an optional reason for the stage change, you will be prompted with the option to rename the incident based on all of the information you’ve gathered throughout response, and provide a new summary.

The new name and summary will be included in the opportunity created in Jeli, as well as updated in the broadcast channels in Slack.

📘

Slack Channel Name

Changing the name of the incident will not change the name of the associated incident channel in Slack. To change the name of the Slack channel, use /jeli rename.

Moving to the mitigated stage also means we will no longer send you status update reminders on your set intervals. We know that the time between mitigation and closing out an incident can be vary depending on your organization’s process, so feel free to take your time in this stage.

Note: Moving to the mitigated stage is not required to close out an incident, address followups, or create a Jeli opportunity. If you skip this stage, we’ll still prompt you with those items upon closing the incident. You can also move back into the identified or investigating stages from mitigated and continue response if need be. (Status reminder intervals will be restored if you return to either identified or investigating stages.)

When an incident is moved to the mitigated stage, we send the incident channel the list of followup items you asked us to remind you about throughout the incident. You can choose to schedule a reminder on a followup and we’ll ping you again about that item at the time of your choosing.

You can also mark the followup as done, if you’ve already addressed it, or edit the followup to add more details or to remind someone else about that item.

Note: Scheduled reminders for followups will not ping to remind you if the followup is marked as done, marked as ignored, or the incident is closed.

Enter /jeli close to close an incident in the mitigated stage. Closing an incident will end the Jeli Slackbot's involvement in the incident channel. Since you have already mitigated the incident, closing it will look a little different than if you are closing it from an investigating or identified stage.

You will be prompted to fill out the close modal and any followups you created during the incident will appear after you close the incident with options to:

• Schedule a reminder
• Edit the followup
• Mark Done if you've completed the followup

We will update the Jeli opportunity with any messages sent in the incident channel since mitigation, and notify you when that is complete. We will also set the final status update with a link to the Jeli opportunity.

The broadcast channels will be updated as well, moving the incident stage to closed, setting an incident closed time, and linking to the Jeli opportunity.

Enter /jeli close to close out an incident that is in the investigating or identified stages. You will be prompted with the option to rename the incident based on all of the information you’ve gathered throughout response, update severity, provide a new summary, and address any followups. The new name and summary will be included in the opportunity that is created in Jeli, as well as updated in Slack broadcast channels.

📘

Slack Channel Name

Changing the name of the incident will not change the name of the associated incident channel in Slack. To change the name of the Slack channel, use /jeli rename.

If you attempt to close out an unmitigated incident, you will be prompted to optionally change the incident stage to mitigated.

Closing the incident ends Jeli Slackbot's involvement in the incident channel, and creates an opportunity in the Jeli web app for incident review. Jeli will then update the channel with a final status indicating that the incident is closed and provide a link to the Opportunity.

The broadcast channels will be updated as well, moving the incident stage to closed, setting an incident closed time, and linking to the Jeli opportunity.

Aliases: /jeli close-incident, /jeli end, /jeli end-incident

Running a demo incident with the Jeli Slackbot gives you all the same features as normal response, but we do not broadcast the incident, or upload the Slack channel into Jeli once the incident is closed.

This is great for familiarizing yourself with Jeli’s features without creating any false alarms. You can use it when running stress tests, game days, or mock incidents to practice response with your team.

Importing Slack channel data into Jeli helps bring more context into your timelines and helps you prepare for your incident reviews. Use this command to create a new Opportunity or import event data to an existing opportunity.