Skip to main content
As your techs transition to using Inbox, they will encounter a number of different notifications from various places. This doc aims to explain the behavior of each type of notification they will encounter.
See Inbox updates in the changelog.
Overview of internal team notifications

Inbox Notifications (Desktop and Web)

When using Inbox, techs by default will get all notifications for all updates on all threads inside Inbox. These alerts are controlled at two levels: global sound toggles (per user) and a per-view notification preference (New threads, owner and mentions / Owner / @ Mentions / Off), configured by each user for each view they’re a member of. For the step-by-step of changing either, see How to Manage Your Inbox Notifications. One behavior worth calling out here: setting a view to Off not only mutes its notifications, it also disables swarm mode for live threads inside that view.

The Notification Banner

The notification Banner appears at the top center of Inbox and comes in 2 variates, Live and Non-Live. Live threads will look like this
Live thread notification banner
And Non-Live threads will look like this:
Non-live thread notification banner
The main difference is the timer, as the Live-Chat request contains an SLA of 5 minutes.
This banner will appear if and only if a new thread comes into Inbox that does not have an assigned owner and is a new thread. It will not appear when the thread gets assigned or someone is mentioned

Desktop Notifications

Desktop notifications will appear based on your Inbox notification settings, as well as your OS notification settings. Desktop notifications will appear the same whether you are using the web version of Inbox, or the desktop version of Inbox. If you wish to mute system notifications entirely for Inbox, you can do that in your OS system settings the same way you do it for any other application.

Admin Panel Controls

Before we go into how Slack and Teams notifications work, it is important to talk about some more global member notification settings that affect both. In the Thread Admin Panel in the members tab, each member has a notification setting that will affect what notifications they will receive from the bot in either Slack or Teams.
Member notification setting in the Admin Panel members tab
  1. All - When this setting is selected, the member will get a notification for ALL threads that they are assigned to in Inbox, regardless if they were sent to MS Teams or Slack via a flow or not
  2. Flow Only - When this setting is selected, the member will only be notified about threads that they are assigned to that are sent to MS teams or Slack via a flow
  3. None - When this setting is selected, the member will not receive any “assigned” notifications from the bot in MS Teams or Slack
Note that this setting only affects the MS Teams or Slack 1 on 1 bot, it will not affect notifications coming from a view configured to receive threads from a flow

Microsoft Teams Notifications

Teams notifications are based on the Teams Companion App that you integrate into your teams tenant. For more info on that integration, please see this doc. Once this integration is setup, your techs will begin to receive system notification from Microsoft Teams. They will be the same weather you are using the web or desktop version of teams.

1. Notifications from the installed Teams Companion App

Once a tech is assigned to a thread as an owner or a member, they will begin to receive Teams notifications from the installed companion app.
Teams notification from the installed companion app
From here, when the thread can be viewed in the 1 on 1 conversation with the bot
Thread shown in the 1-on-1 conversation with the Teams bot

2. Notifications from a public teams channel

Once the Teams integration is setup in your workspace, you have the option to direct threads to a public Teams channel in your tenant via a flow in the thread admin panel. When a new thread is created, it will appear in the channel
New thread appearing in a public Teams channel
But after the thread gets an assigned owner, only that owner will get notifications about that thread.
Assigned-owner notification in Teams

Slack Notifications

Slack notifications are based on the Slack Companion App that you integrate into your Slack tenant. For more info on that integration, please see this doc. Once this integration is setup, your techs will begin to receive system notifications from Slack regarding their thread. These notifications can come from 1 of 2 places.

1. Notifications from the installed Slack Companion App

Once a tech is assigned to a thread as an owner or a member, they will begin to receive Slack notifications from the installed companion app.
Slack notification from the installed companion app
From here, when the thread is updated by the contact or another tech, the owner will be notified.
Slack notification when a thread is updated

2. Notifications from a public Slack channel

Once the Slack integration is setup in your workspace, you have the option to direct threads to a public Slack channel in your tenant via a flow in the thread admin panel. When a new thread is created, anyone in that channel will receive notification for new threads:
New thread appearing in a public Slack channel
But after the thread gets an assigned owner, only that owner will get notifications about that thread.
Assigned-owner notification in Slack

Internal Notification FAQ

The Slack/Teams companion bot can only be added to a public channel. When added to a private channel, the bot is unable to update anything.
If you are getting too many notifications from the Teams/Slack Companion App, you can mute the 1 on 1 conversation with the bot itself in teams, mute the companion app itself in Slack, or you can mute the channel that you have all of your threads routes to in teams
To get rid of these Swarm Modes in Inbox, you can set the view notifications to “none” where these swarm modes are coming from. If the Swarms are coming from multiple views, you will have to mute all of them