Notifications¶
The DW supports various Notification Channels, such as Emails, Webex Teams, Microsoft Teams, various SMS providers, and more.
The guides below focus on some of the most commonly used options.
DW Local - Browser/Toaster Notifications¶
Requirements¶
Administrator Role in the DW
Business Unit(s) Configuration¶
The DW Local is available by default.
Set up Notifications/Alerts¶
Notification Rules/Alerts can be configured on various calculation-based Segments. See more details for KPI Notifications or Grid Alerts.
During the setup, you need to select the DW Local Channel.
Recipient¶
The DW Local Notification Channel does not utilize any recipients – the configured Notifications/Alerts will be sent to every user who is actively displaying the DW Layout where these were configured.
Limitations & Control¶
While in edit mode, local (toast) notifications can be suppressed by clicking on the . It can be useful when the user wants to avoid being interrupted by notifications while editing the layout.
For grid local (toaster) notifications, there is a limit of 5 notifications. If more than 5 grid notifications (from all grids combined) are triggered at the same time, only 5 will be displayed. Additionally, a special 6th notification will appear, indicating additional hidden ones.
Email¶
Requirements¶
Tenant Administrator Role in the DW
Business Unit(s) Configuration¶
Add the new Email Notification Channel to the Business Unit (BU).
To make the Channel available on all BUs, perform this action in the Shared BU.
To make the Channel available only on a specific BU, perform the following action on the desired BU.
This is configured within the Admin Tool, under Business Units > intended BU > Notification Channels
In this instance, Channel Type will be Email.
This needs to be performed just once.
Set up Notifications/Alerts¶
Notification Rules/Alerts can be configured on various calculation-based Segments. See more details for KPI Notifications or Grid Alerts.
During the setup, you need to select the Email Channel.
Recipient¶
The Email Notification Channel requires an email address in the Recipient field. These can be either specific addresses set by you, or, in the case of Grid Alerts, the Recipient can be dynamically populated from the email value if it is available on the Connector (most commonly within the User Attributes calculation), which is usually used for personal notifications.
Microsoft Teams - Personal¶
Requirements¶
Microsoft Teams App: The “2Ring DW Notifications” app needs to be enabled for your organization. If your Microsoft Teams administrators do not see the app available, please reach out to 2Ring Support to provide files and instructions for manual import.
Entra ID integration: For more information, please see Entra ID integration documentation.
Tenant Administrator Role in the DW
Business Unit(s) Configuration¶
Add the new Microsoft Teams - Personal Notification Channel to the Business Unit (BU).
To make the Channel available on all BUs, perform this action in the Shared BU.
To make the Channel available only on a specific BU, perform the following action on the desired BU.
This is configured within the Admin Tool, under Business Units > intended BU > Notification Channels
In this instance, Channel Type will be Microsoft Teams - Personal. This channel requires the “Entra Tenant Name”, which is configured during the “Entra ID integration”.
This needs to be performed just once.
Set up Notifications/Alerts¶
Notification Rules/Alerts can be configured on various calculation-based Segments. See more details for KPI Notifications or Grid Alerts.
During the setup, you need to select the Microsoft Teams - Personal Channel.
Recipient¶
The Microsoft Teams – Personal Notification Channel requires an email address (= MS Teams username) in the Recipient field. These can be either specific addresses set by you, or, in the case of Grid Alerts, the Recipient can be dynamically populated from the email value if it is available on the Connector (most commonly within the User Attributes calculation), which is usually used for personal notifications.
Cisco Webex Teams¶
Requirements¶
Webex Chat Bot: For more information, please see Cisco Webex Teams chapter.
The Access Token is visible only once – capture the Access Token for later use.
Tenant Administrator Role in the DW
Business Unit(s) Configuration¶
Add the new Cisco Webex Teams Notification Channel to the Business Unit (BU).
To make the Channel available on all BUs, perform this action in the Shared BU.
To make the Channel available only on a specific BU, perform the following action on the desired BU.
This is configured within the Admin Tool, under Business Units > intended BU > Notification Channels
In this instance, Channel Type will be Cisco Webex Teams. After selecting this Channel Type, you are required to fill in the Access Token (this is done under “Settings…”), which was generated during the setup of the Chat Bot.
This needs to be performed just once.
Set up Notifications/Alerts¶
Notification Rules/Alerts can be configured on various calculation-based Segments. See more details for KPI Notifications or Grid Alerts.
During the setup, you need to select the Cisco Webex Teams Channel.
Recipient¶
The Cisco Webex Teams Notification Channel requires a Room/Space ID in the Recipient field. The steps to obtain this ID are described in the Cisco Webex Teams configuration chapter.
Webex Connect - SMS¶
Webex Connect offers connectivity to various systems, and while some of the steps below are applicable across these systems, the focus here is on sending SMS.
Requirements¶
Webex Connect Service Official documentation
We will need the Service Key for the API Connection from the configured Connect Service. For more information, see https://help.webexconnect.io/docs/service-key-and-jwt-authentication-tokens. No extra Connect Service configurations are required.
A valid From Number/Short Code in Connect - the number that will be sending the SMS and is configured to do so. For more information, see https://help.webexconnect.io/docs/phone-numbers
Tenant Administrator Role in the DW
Business Unit(s) Configuration¶
Add the new Webex Connect SMS Notification Channel to the Business Unit (BU).
To make the Channel available on all BUs, perform this action in the Shared BU.
To make the Channel available only on a specific BU, perform the following action on the desired BU.
This is configured within the Admin Tool, under Business Units -> intended BU -> Notification Channels. For more information see Notification Channels chapter.
In this instance, Channel Type will be Webex Connect - SMS. After selecting this Channel Type, you are required to fill in the Service Key, From Number/Short Code (this is done under “Settings…”), which was generated during the setup of the Chat Bot.
This needs to be performed just once.
Set up Notifications/Alerts¶
Notification Rules/Alerts can be configured on various calculation-based Segments. See more details for KPI Notifications or Grid Alerts. During the setup, you need to select the Webex Connect - SMS Channel.
Recipient¶
The Webex Connect - SMS Notification Channel requires a phone number in the Recipient field. These can be either specific phone numbers set by you, or, in the case of Grid Alerts, the Recipient can be dynamically populated from the email value if it is available on the Connector (most commonly within the User Attributes calculation), which is usually used for personal notifications.
WhatsApp (for Business)¶
Requirements¶
WhatsApp Business Account
Meta Developer Account
WhatsApp Business Application (WABA) - follow the steps described here to create a new Meta App.
On the Use Case setup (after selecting “Connect with customers through WhatsApp”), we require only the “Step 1. Try it out”, which allows for up to 5 registered Phone Numbers that can receive the Notifications. This “Step 1” is where you can also test that the messages can be sent & received. If you would like to send alerts to more numbers, you need to complete the full setup of the Use Case, but please keep Meta’s rules & pricing in mind.
The permanent Access Token (configured in step 5 of the linked guide) will be required for the connection from your DW tenant to the WhatsApp API.
Phone Number ID – obtained on the “Use Case” page.
Message Template – WhatsApp limits sending messages from Business accounts/numbers with a 24-hour rule (see more at Facebook - WhatsApp documentation). To bypass this limitation, you must use a Message Template approved by Meta (see more at Facebook - WhatsApp documentation).
Tenant Administrator Role in the DW
Business Unit(s) Configuration¶
Add the new WhatsApp Notification Channel to the Business Unit (BU).
To make the Channel available on all BUs, perform this action in the Shared BU.
To make the Channel available only on a specific BU, perform the following action on the desired BU.
This is configured within the Admin Tool, under Business Units > intended BU > Notification Channels chapter.
In this instance, Channel Type will be WhatsApp. After selecting this Channel Type, you are required to fill in the Access Token and Phone Number ID (this is done under “Settings…”), which was generated during the setup of the Chat Bot.
This needs to be performed just once.
Set up Notifications/Alerts¶
Notification Rules/Alerts can be configured on various calculation-based Segments. See more details for KPI Notifications or Grid Alerts.
During the setup, you need to select the WhatsApp Channel.
Recipient¶
The WhatsApp Notification Channel requires a phone number in the Recipient field.
These can be either specific phone numbers set by you, or, in the case of Grid Alerts, the Recipient can be dynamically populated from the email value if it is available on the Connector (most commonly within the User Attributes calculation), which is usually used for personal notifications.