EBS: How to Set Up a Cisco Spark Integration Under the IT Alerting Smart Channel Integration Setting in Everbridge Suite

Topic:

How to set up a Cisco Spark integration with Everbridge Suite.

Description:

Cisco Spark is a collaboration tool that allows teams to collaborate in areas known as ‘spaces’. Team members can text chat, share files and make video calls.

The Everbridge integration allows users to link spaces to Everbridge Incidents so those in the control room and staff on the ground can share knowledge in a space that’s linked to the incident. Content from the space is then posted to the Everbridge incident so incident managers and org admins can see what happened without having to log in to Cisco Spark.

To configure a Cisco Spark integration with Everbridge Suite, follow the steps below:

Add to Spark
  1. Log in to the Manager Portal and select the appropriate organization from the upper right-hand corner.
  2. Click on the Settings tab.
  3. Click on ITA on the left.
  4. Click Smart Channel Integration in the drop-down menu.
  5. Click the radio button next to Cisco Spark.
  6. Click the Add to Spark button.
Cisco Spark Login
  1. A prompt will open and enter credentials to log in to Cisco Spark.
  2. Click Accept.
Once the integration is complete the page will redirect to the Everbridge Suite settings.

With the integration set up, follow the steps below to create a 'space' for an incident:

ITA
  1. Click on the ITA tab.
  2. Click on the Operations sub-tab.
  3. Find the desired open incident and click Create under the Channel column.
Created Space
  1. A space will then appear in Cisco Spark. The name of the space will be the Incident Name(Incident ID).

NOTE: It is encouraged that the Incident ID is used as a visible variable in the incident template. This helps identify 'spaces' for incidents in Cisco Spark if there are multiple open incidents. It is also recommended that users install the Cisco Spark mobile app to collaborate in the field.

Was this article helpful?
0 out of 1 found this helpful

Comments

0 comments

Article is closed for comments.