Major Incident Management (MIM) Templates (IA)
Major Incident Management (MIM) workflows automate and accelerate major incident management with preset actions.
When starting a major incident, Biggy will prompt you to select a MIM template. For more information about handling major incidents, see the Manage Major Incidents documentation.
As major incident management processes vary across services and scenarios, you can configure multiple templates.
Configure MIM templates in the web app at Manage > Workflows > MIM Templates.

MIM Templates
In the MIM Templates list, you can see information about each existing template:
Template Name
Description
Number of actions
Number of entities
Last updated time
Status (Enabled or Disabled)
To make a template the default, click the Star icon. Default templates appear first in the selection list when initiating a MIM.
To edit an existing template, click the Pencil icon.
To create a new MIM template from an existing one, click the Clone icon.
To delete a template, click the Trash Can icon.
Use the Search bar at the top of the page to find a specific template.
Create or Update a MIM Template
To create a new MIM template, click New Template.
Choose between the Guided Setup, Quick Start, Generate with AI, or Start from Scratch.
Clone a template
If your organization has already created one or more MIM templates, you can create a new template using an existing one.
Use the Clone button to copy an existing template. Choose a unique name for the new template. You can then edit or add fields to the new cloned template.

The Guided Setup walks you through each step of creating the template in a step-by-step wizard. This option is especially helpful if it's your first time creating a MIM template.
Quick Start creates a basic preset template containing an incident announcement, recurring status updates, and a resolution summary.
Use Generate with AI to describe the major incident program you want in natural language, and Biggy will draft the full template for your review.
After finishing the guided setup, quick start, or generate with AI, you can edit any fields as needed in the full template builder.
To open the full, blank template builder, select Start from Scratch.

At the top right of the page, use the Template Status toggle to determine whether the template is active or inactive. Only active templates can be selected when initiating a major incident.
You can use Design with Biggy to populate the template using AI. Describe the incident program and Biggy proposes channels and actions. You review before saving.
The template creation page is divided into the following tabs:
Overview
The Overview tab provides a summary of the template at a glance.

The What this template does section provides a summary of the current configuration. Click a line to open the page where the setting is configured.
The Actions at a glance section displays a summary of the action timeline. Click Open Actions to go to the Actions tab.
The Recent versions section shows when the template has changed, and who edited it. Click History to view the full revision history, and revert to earlier versions of the template.
Settings
In the Settings tab, populate basic information about the template, and configure settings related to incident priority, swarm investigations, broadcast channels, and message threading.
Template Details
In the Template Details section, provide basic information to help other users understand the template's purpose.
Configure the following fields:
Template Name (Required): A clear, descriptive name for the template.
Description: Details about how and when this template should be used.
Incident Priority
In the Incident Priority section, select whether the incident priority is predetermined in this template, or if it should be chosen at MIM creation.
The custom priority values configured in General Settings are used.
Select one of the following options:
Set on MIM Creation: users select the priority each time they create a MIM using this template.
Preselect in Template: the same priority is always used whenever this template is selected. If you select this option, choose the Default Priority from the drop-down menu.
Sync from ServiceNow: Sync the priority from the linked ServiceNow ticket. The linked ticket owns this MIM's priority, and its value is translated using your organization's ServiceNow priority mapping.
Swarm Investigation
In the Swarm Investigation section, decide whether or not to auto-start an investigation swarm when a MIM is created using this template. Choose from the following options:
Always - Swarm investigations always automatically start for every incident created from this template.
Ask on MIM creation - Users choose whether to start a swarm investigation when they create the incident.
Disabled - No swarm investigations will be created for incidents using this template.
When enabled, choose whether the swarm Requires root-cause approval. When enabled, the swarm pauses at Pending Resolution until someone approves its proposed root cause, and fully resolves when the incident is resolved.
In the Priority Scoping section, scope the swarm to incident priorities.
Define the priority when an incident should Always start at and, if Ask on MIM creation was selected, the priority when an incident should Optionally start at.
Both lists are re-evaluated on every priority change: a change into an "always start" priority starts the swarm even if it was declined at creation. De-escalation never stops a started investigation. Leave both empty to keep the behavior above for every priority.
Status Page
Enable the Status Page section to auto-generate an internal Status Page when a MIM is created using this template. The status page will update as the incident progresses.
After enabling this section, populate the following information:
Template - select a status page template to use with this MIM template.
Auto-update interval - enter how often (in minutes) the status page will update.
Default view - select whether the status page should be directed towards an Executive or Technical audience.
Prompt override (optional) - if you would like to override the status page template prompt, enter a prompt override to use with this MIM template.
Default Members
In the Default Members section, define which users or user groups are invited when a MIM starts. Select to invite people or groups to all incidents or to incidents with a specific priority level.
Broadcast Channels
In the Broadcast Channels section, select one or more channels to receive an incident announcement.
Select whether incidents should only be posted in the channel when the priority is a specific level, and the notification behavior on incident resolution.
When an incident's priority changes mid-incident, newly matched channels receive the announcement. Broadcast posts are updated in place and never removed mid-incident. A Slack channel set to Delete notification has its announcement removed when the incident completes, keeping live-view channels limited to active incidents. Reopening the incident posts a new announcement.
Message Threading
In the Message Threading section, determine where incident updates land in Teams channels and in the Slack thread an incident was started from.
Enable or disable the following options:
Threaded Teams Output: Post incident updates as replies under the original Teams channel post instead of new channel posts. Applies to Teams channels only; meeting and group chats are unaffected.
Updates in the Starting Slack Thread: When a major incident is started from a Slack thread, Biggy posts the activation message as a reply in that thread instead of in the channel, and mirrors later stakeholder updates there too. The incident channel still receives every update. Off, or a start without a Slack thread, changes nothing.
Communication Entities
In the Communication Entities tab, configure which channels or communication sources (such as chat channels, ServiceNow tickets, or emails) will be monitored for updates, used to post automated actions, or used for on-call paging. Multiple communication entities can be added to a single MIM template.
If your template has existing communication entities, basic information about each entity will be displayed.

You can edit or delete any existing communication entity. In the list of communication entities, click the Pencil icon to edit a communication entity, or click the Trash Can icon to delete an entity.
To add a new communication entity, click the + button on the right side of the Communication Entities tab.
Populate the following information for all entity types:
Field | Description |
|---|---|
Entity Type | Select the communication channel used for this entity. This channel can gather context, push updates, or be used for paging, depending on the selected entity type or usage context. The following entity types are available:
|
Label (Required) | A descriptive name for the communication entity. |
Hint Text | Additional information to help users understand the purpose of the communication entity. |
Different information needs to be populated depending on the type of communication entity you create. Follow the instructions for the entity type you selected:
Create a Meeting URL Communication Entity
To create a communication entity that uses a meeting URL, populate the following information:
Field | Description |
|---|---|
Usage Context | How the communication entity will be used. Select one of the following:
|
Required Entity | When enabled, Biggy will post and continuously update the incident banner message with the title, status, impact, and key findings. Note: Automatically created entities are always available and cannot be marked as required. |
How should this meeting be determined/created? | Choose how Biggy should create a meeting, or determine which meeting to use. The following options are available:
|
Create a Slack Channel, MS Teams Channel, or MS Teams Chat/Meeting Communication Entity.
To create a communication entity that uses a Slack or MS Teams channel, populate the following information:
Field | Description |
|---|---|
Usage Context | How the communication entity will be used. Select one or both of the following:
|
Biggy Spotter Agent | The Biggy Spotter Agent actively listens to the channel, and when an intent to perform an action is detected, it identifies potential risks and suggests steps to complete the action. Select the Biggy Spotter Agent behavior:
|
Required Entity | When enabled, Biggy will post and continuously update the incident banner message with the title, status, impact, and key findings. Note: Automatically created entities are always available and cannot be marked as required. |
How should this channel be determined/created? | Choose when this channel should be selected. Select from the following options:
|
Optional Channel Lookback | This option only appears if you choose the Select an existing channel when executing the MIM, or Preset this channel now channel creation option. Enable this option to allow incident creators to include messages prior to MIM start as context for this entity. When the MIM starts, creators will see a lookback prompt for this entity. Select one or both of the following input modes:
|
Enable Teams Channel Meeting Creation | This option only appears if you selected MS Teams Channel as the entity type. Automatically create a Teams meeting inside this channel with transcription included. The meeting will appear as a Meet Now card in the channel, and responders can join directly from it. |
Create an Email Communication Entity
To create a communication entity that uses email, populate the following information:
Field | Description |
|---|---|
Usage Context | How the communication entity will be used. Emails can only be used as an Output Destination. |
Required Entity | When enabled, Biggy will post and continuously update the incident banner message with the title, status, impact, and key findings. Note: Automatically created entities are always available and cannot be marked as required. |
How should these email addresses be determined/created? | Choose how Biggy should determine which email addresses to use. The following options are available:
|
Create a ServiceNow Ticket Communication Entity
To create a communication entity that uses a ServiceNow ticket, populate the following information:
Field | Description |
|---|---|
Usage Context | How the communication entity will be used. Select one or both of the following:
|
Required Entity | When enabled, Biggy will post and continuously update the incident banner message with the title, status, impact, and key findings. Note: Automatically created entities are always available and cannot be marked as required. |
ServiceNow Tables | Add one or more ServiceNow table names. Users will input record numbers from the tables entered here when creating the incident. |
Mark as Primary Ticket | Designate this as the incident ticket of record. When it reaches Resolved or Closed in ServiceNow, the MIM auto-resolves. The sync is one-way: resolving the MIM does not close the ServiceNow ticket. |
How should this ServiceNow ticket be determined/created? | Choose how Biggy should create a ticket, or determine which ticket to use. The following options are available:
|
Create a Jira ticket communication entity
To create a communication entity that uses a Jira ticket, populate the following information:
Field | Description |
|---|---|
Usage Context | How the communication entity will be used. Select one or both of the following:
|
Required Entity | Enable this field to require users to provide a value for this entity when initializing the MIM. |
How should this Jira ticket be determined/created? | Choose how Biggy should create a ticket, or determine which ticket to use. The following options are available:
|
Create an On-Call Paging Communication Entity
To create a communication entity that uses a paging service, populate the following information:
Field | Description |
|---|---|
Paging Service | Select the on-call service used to page responders. Only tools you have integrated are selectable. |
Paging Mode | Select how users will pick the paging targets during a major incident. The following options are available:
|
Custom Message Template (Optional) | Optionally enter a custom description used when paging. Default is blank. |
Default Paging Targets | This option only appears if you selected Paging Directory or Static as the Paging Mode. Select the targets that will be selected by default when creating the major incident. Paging targets will only appear as a selectable option if they have been configured in the integration. See the On-Call Integrations documentation for more information. |
Actions
In the Actions tab, define automated actions. Use automated actions to automatically update stakeholders, or invoke capabilities, workflows, or custom prompts.
If actions have already been configured for this template, a timeline of when each configured action occurs during a major incident is provided. For each action, basic information about what occurs during execution is displayed.

Output destination
There must be at least one communication entity configured as an output destination to add an action.
Click the + button to open the Add MIM Action sidebar.
Populate information in the following sections:
Section | Description |
|---|---|
Basic Information | Contains descriptive information about the action that helps other users understand its purpose. Populate the following fields:
|
Schedule | Determine what type of schedule the action should follow. In the Schedule Type field, select from the following options:
|
Per-priority schedules | This option only appears if you selected Recurring as the priority type. Override the interval while the incident holds specific priorities (for example, every 30 minutes at P1). The first matching override takes precedence, otherwise the default interval above applies. When a priority change selects a different interval, the timer resets from the change. |
Run only for priorities | The action runs only while the incident's current priority matches; otherwise it is skipped with a visible reason. Leave empty to run for every priority. |
Only when changing from | This option only appears if you selected On Priority Change as the schedule type. Optional source scope: the change must come from one of the selected priorities. A first-time priority has no previous value and never matches a source scope. |
Context Sources | Determine which context sources defined in the Communication Entities should be used to aggregate information and content. |
Context Lookback Period | Choose whether Biggy will evaluate context from the start of the incident or only since the last action occurred. Select From Incident Start to always analyze the full context from incident creation to now. Select From Last Execution to only analyze the new context available since the last action occurred. |
Skip when no meaningful updates | This option only appears if you selected One-Time, Recurring, or On Resolution as the Schedule Type. When this option is enabled, actions will not be posted if nothing substantive has happened in the context sources since the last action. A record of the action will still be logged in the timeline. |
Output Destinations | Choose where the content generated by Biggy will be posted. In the Post to all output destinations field, toggle on to send the content to all configured output destinations. Toggle off and the Select Specific Destinations field will appear, where you can choose a communication entity. |
Execution & Action Instructions | In the Execution section, choose what type of execution you'd like to take place when this action occurs. You can choose from the follow execution types:
|
Approval Settings | Choose whether you would like to require approval prior to posting the AI-generated content. Click the Require Human Approval box to require a review of the draft before posting. If this option is selected, the user who starts the major incident will receive a direct message from Biggy requesting approval prior to posting actions. If this option is enabled, select the Approval Destination. |
Click Create Action to save the action.
You can edit or delete any existing action. In the actions timeline, click the Pencil icon to edit an action, or the Trash Can icon to delete it.
Presentation
In the Presentation tab, control the MIM's banner content, start message links, naming, and time zone.
Banner Content
In the Banner Content section, control how much incident detail the pinned MIM banner shows in Slack and Teams. Choose from the following options:
Standard - Default banner layout. Includes summary, impact, root cause, environment, region, related links, and action items.
Detailed - Includes all aspects of the standard layout, plus deterministic actions progress and the next scheduled update.
Custom - Select which fields to include in the banner.
Banner content settings apply to new MIMs created from this template; running MIMs retain their original layout.
Slack and Teams show the same sections. On Teams, text sections render in the facts table above links and action items.
Start Message Links
In the Start Message Links section, choose which communication entity the Join Incident Bridge button on the MIM start message points at. View Incident Banner always follow the banner destination.
Choose from the following options:
Automatic - Uses the banner destination's own meeting when it has one, otherwise the first meeting-bearing entity.
Always this entity - Define a specific Bridge entity. This entity is always used. If it cannot produce a meeting link, the start message says so instead of linking elsewhere.
Hidden - Omit the Join Incident Bridge link from the start message.
Naming and Time
In the Naming and Time section, control How new incident titles are formed and which timezone incident communications use for timestamps.
The following settings are available:
Ticket Number in Incident Title: When enabled, start new incident titles with the linked ServiceNow ticket number so several concurrent incidents are easy to tell apart. Affects the MIM execution title only, not channel or meeting names.
Display Timezone: Define the timezone for timestamps in incident communications generated from this template. Organization default uses the org-wide output timezone, or UTC when none is configured.
Policies
In the Policies tab, control what happens when incidents are mitigated, and access to banner actions.
While the Incident is Mitigated
In the While the Incident is Mitigated section, select what recurring actions do once the incident is marked as mitigated, and which action notices reach Slack and Teams.
Under Recurring Actions, select from the following behaviors:
Send one final update, then stop - Each recurring action runs once more at mitigation, then holds until the incident is active again.
Keep sending on the normal schedule - Recurring actions continue at their configured cadence while mitigated.
Stop immediately - Recurring actions hold from the moment of mitigation. On Mitigation actions and Run now are unaffected.
Enable Post skipped-action notices to post a "Biggy skipped" line in the incident thread and notify the incident starter when a scheduled action has nothing new to say. Skips always stay in the action history.
Enable Post action progress notices to post the short running, completed, or awaiting approval line under the banner while an action runs. The update itself always posts.
Banner Action Access
In the Banner Action Access section, determine who may use the banner's interactive actions and manage the incident on the web, optionally per priority. Unrestricted with no overrides means anyone in the channel.
In the Who can use banner actions drop-down, choose from the following options:
Everyone: Anyone who can see the banner can use its buttons. Pick a restricting option to gate the buttons on Slack and Teams and the management actions on the web.
Assigned at creation: Only people assigned when the MIM is created (default members for its priority plus the creator's picks) can use the buttons. The list is fixed for the incident: later invites, priority changes and paging do not add to it. Everyone else gets a private "not authorized" notice.
When this option is selected, you can also choose to allow the person who started the incident.
Users with Execute MIM permission: Only people who currently hold the Execute MIM permission can use the buttons. Granting or removing the permission takes effect on the next click, even on a running incident. Standard User and System Admins include this permission by default.
When this option is selected, you can also choose to allow people assigned at creation and the person who started the incident.
Users with Manage MIM permission: Only people who currently hold the Manage MIM permission can use the buttons and manage the incident on the web. Manage MIM does not start a MIM, and Execute MIM does not include it. Standard User does not have the permission by default; System Admins do.
When this option is selected, you can also choose to allow people assigned at creation and the person who started the incident.
In the Priority Overrides section, define banner action access by priority. Viewing is never restricted. Changes apply to incidents created after you save.
Click + Add priority override to add a new override. Choose a Priority level, User type, and what can be Also allowed.