Topic

This article describes how the operator form behaves when sending a follow-up incident in Everbridge Suite, how incident variables affect the operator form, how contact selection works on follow-up notifications, and how the order of fields on the operator form is determined.

Description

Incident variables are placeholders that can be defined in an incident template and filled in by the operator when launching an incident. These variables can be inserted into message body, subject, and other fields, and their values are automatically replaced when the incident is launched. Incident variables allow dynamic content population, but they do not support conditional message branching.

When launching a follow-up notification, the contact selection process is more restrictive than for an initial notification. On a follow-up, contacts are first selected based on their confirmation status from the previous notification. After that selection step, when the operator proceeds to the Incident Operator Form, only those selected contacts are pre-filled. An informational banner indicates that default template contacts are not automatically included in this context. Users who have the necessary permissions can manually add additional contacts if needed.

The operator form lists fields in the order they were checked or added when each template was built. If different templates were created with variables added in different sequences, the operator form field order can vary between those templates. To make the order consistent, templates can be built with fields checked in the same order, or the scenario can be edited and the variables reordered directly (using drag-and-drop) into the desired sequence before launching.