Communication Preferences allow you to control how Teamgage notifications are delivered to users across your organisation.
For each communication channel, you can choose from one of the following settings:
On - When a channel is set to On, Teamgage will always attempt to send notifications using that communication method.
- Example - If Email is set to On, the user will receive Teamgage notifications via email
Off - When a channel is set to Off, Teamgage will never send notifications using that communication method.
- Example - If SMS is set to Off, the user will not receive Teamgage notifications by SMS.
Fallback - When a channel is set to Fallback, Teamgage will only use that communication method if the primary notification method is unsuccessful. This helps improve delivery rates while avoiding duplicate notifications.
- Example - If Microsoft Teams is set to On and Email is set to Fallback, Teamgage will first attempt to deliver the notification through Microsoft Teams. If delivery is unsuccessful, Teamgage will then send the notification via Email.
Why Use Fallback Channels?
Some communication platforms rely on additional configuration or user setup.
For example:
- A user may not have the Teamgage app installed in Microsoft Teams
- A Slack integration may not be configured correctly
- A user may no longer be active on a particular platform
By configuring a fallback channel, you can help ensure important Teamgage notifications still reach users even if the primary delivery method fails.
Best Practice
For most organisations, we recommend configuring:
- Microsoft Teams or Slack as the primary communication channel
- Email as a fallback communication channel
This approach provides a seamless user experience while maintaining a reliable backup method for notification delivery.
Related Articles