EBS: How to Include the Geo-Location of a Contact in an SOS Notification in Everbridge Suite

Topic:

How to include the geo-location of a contact in an SOS notification.

Description:

The geo-location of a contact can be included in SOS notifications by following the sections below in order:

  1. Create a variable

The Location: Geo Point variable can be used to in a clickable link for your contacts to receive. The variable must already be created before it can be used in an incident template.

To create a clickable link for contacts to receive in an incident message, follow the steps below:

  1. Log in to the Manager Portal and select the desired organization from the upper left-hand corner.
  2. Click on the Incidents tab from the top of the page.
  3. Click the Templates sub-tab.
  4. Click on the pencil icon to the left of the incident template desired.
  5. Under Preview & Edit, click the Outgoing Message tab.
  6. Create the link by entering "http://maps.google.com/maps?q=" in the body of the message.
  7. Click to place the cursor immediately after "=", and then click to the left of the Location: Geo Point variable.
  8. Complete the rest of the template as desired and click Save.
When the incident is launched, contacts will receive the message and can tap/click the link to redirect them to a pinpoint on Google Maps.
  1. Create an incident template

Incident Templates are set-up to take advantage of easy drop-down and fill-in choices and use dynamic guidelines to pre-populate aspects of the message ahead of time. The steps below review creating one at a high level.

  1. Log in to the Everbridge Manager Portal.
  2. Click on the Incidents tab.
  3. Click on Templates.
  4. Click New Incident Template.
  5. Fill and make selections for the following areas:
  • Header - This is where the template is named, set live, given a Template ID and a Category.
  • Form and Message - This is where the variables that need to be included in the template are selected and the Outgoing Message is edited.
  • Publishing Options - This are the options for publishing the incident to additional outlets.
  • Contacts - This is where contacts, groups, and/or rules are chosen to receive the incident.
  • Settings - This is where the delivery settings for the incident notification are controlled.
  • Permissions - This is where the functionality available to the incident operator is decided
  1. Click Save.

NOTE: Include the Location: Geo-Point variable in the Form and Message of the new incident template.

  1. Create a variable mapping

Safety variable mappings allow specified variables mapped to the safety connection features used by the Everbridge Mobile App to be part of an incident. To create a variable mapping, follow the steps below:

  1. Select an organization from the upper-right hand side of the page.
  2. Click on Settings.
  3. Click on Interactive Visibility.
  4. Click on Safety.
  5. Click on Variable Mappings.
  6. In the Safety Field Name: Location, select the variable relating to a geo-point.
  7. Click Save.
  1. Create an SOS threshold

SOS thresholds are used to trigger a notification or incident when a contact uses the Safety Connection features in the Everbridge Mobile app. To create an SOS Threshold, follow the steps below:

  1. Log in to the Manager Portal.
  2. Select an organization from the upper-right hand side of the page.
  3. Click on Settings.
  4. Click on Interactive Visibility.
  5. Click on Safety.
  6. Click on Safety Thresholds.
  7. From the Launch Notification/Incident If pane on the left make the following selections:
  1. For Type is, select SOS.
  2. For Sender's Record Type is, select the desired record type.
  3. Select the check box next to Message Location is and select a desired method.
  1. From the Launch Notification/Incident pane on the right, select the check box next to Launch an Incident.
  1. From Choose Incident Templates, search for the desired incident template.
  2. Enter a Threshold Name.
  3. Click Save.
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.