Global, multimodal messaging allows you to easily keep customers, partners and other stakeholders informed during critical incidents to minimize inbound call center volume, quickly put the response team in place, and ensure key executives are kept in the loop. In an effort to automate processes for IT Alerting, Everbridge is offering a ServiceNow certified connector application to integrate key features of ServiceNow and Everbridge. These features include contact and group synchronization, incident alerting and management, and reporting of all Everbridge notification events within the relevant ServiceNow incidents. By using the Everbridge connector application, you can ensure that when critical incidents occur, the right on-call resources are notified and escalations take place to reduce the response time.
- MULTI-MODAL ALERTING: Notification recipients will be reached through multiple modalities such as email, push notification, SMS text and voice.
- TRUE SCALABILITY AND GLOBAL REACH: Built to deliver millions of messages around the world at the same time, the Everbridge platform is tested daily and trusted by the most demanding Federal, State, Military, Healthcare and corporate customers.
- AUTOMATIC ASSIGNMENT AND ESCALATION: Assign users based on their response and track it in the ServiceNow Incident “Assigned To” section. If nobody responds, automatically escalate to individuals, groups or on-call resource based on customizable and self configurable rules.
- DETAILED PERFORMANCE REPORTS: All Everbridge notification details and delivery details are available for reporting. ServiceNow users know what incidents were launched from Everbridge and what delivery paths were used to reach contacts. Users can also see who responded through which delivery paths at what time.
- EASY TO USE TEMPLATES: No need to code template – use ‘drag and drop’ conditional logic and tokens to build flexible templates.
- CONTACT AND GROUP SYNCHRONIZATION: The integration with ServiceNow allows for easy contact and group synchronization from ServiceNow to Everbridge. Contacts are uploaded to Everbridge using in-memory file and is not stored anywhere.
- SIMPLE TO CONFIGURE: The integration with ServiceNow is completely self configurable. ServiceNow administrators can define the conditions under which an Everbridge incident will be launched. The conditions can be configured based on any of the ServiceNow incident fields.
Version 3.5.1
Support for Utah, Tokya, San Diego and Rome release. Please note this connector is now under maintenance mode. Please reach out to your account manager to learn about our new Smart Orchestration (SORCH) based connector or look at our xMatters connector.
Version 3.5.0
Support for Rome, Quebec and Paris release. Please note this connector is now under maintenance mode. Please reach out to your account manager to learn about our new Smart Orchestration (SORCH) based connector or look at our xMatters connector.
Version 3.4.3
Support for Orlando release
Version 3.4.2
Support for New York Release
Version 3.4.1
This release has the following changes:
- Contact sync now supports overriding the default bahavior of passing all groups a contact belongs to the csv upload file. A flag "getSelectiveGroup" can be set to true in the extension file to only pass the groups that are marked with sync flag to true in the Everbridge table
- Sync Contacts and Group & Sync Contacts now do not make a separate API call to create a group. Group creation is handled by the CSV upload.
Note: This is the same version as 3.3.3, certified to work with Kingston as well as London
Version 3.3
This release has the following changes:
- Contact sync now supports overriding the default bahavior of passing all groups a contact belongs to the csv upload file. A flag "getSelectiveGroup" can be set to true in the extension file to only pass the groups that are marked with sync flag to true in the Everbridge table
- Sync Contacts and Group & Sync Contacts now do not make a separate API call to create a group. Group creation is handled by the CSV upload.
Version 3.2
- Added support for "Partial" and "Replace" mode for Contact Upload
Version 3.1
- Resolved contact and group sync issue
- Resolved configuration table issue and migrated to new table
- Added option to disable delivery path sync for external sync
Utah, Tokya, San Diego and Rome