New: the AI firewall watches every module and explains each incident in plain words. See how it works

Channels

The notification channels compared – in-app, e-mail, SMS, push and chat apps, what each needs, who they reach, quiet hours and what is in development.

A channel is one way of reaching a person. Every notification is offered to each of its recipients on every channel that applies, unless the sender restricts the channels. This page compares the channels; each has its own page.

Overview

ChannelIdNeedsQuiet hoursPerson can switch it offSet up by
In-appinappA member accountNoNoAlways on
E-mailmailAn e-mail addressNoYes (Email notifications)Platform sender, or your mail settings
SMSsmsA phone numberYesYes (SMS notifications)Your SMS provider settings
PushpushA registered browser or app installYesYes (Push notifications)Push Settings
Chat appsone id per platformA linked chat accountYesYes (per platform)Chat platforms

Which recipients reach which channels

What a channel can deliver depends on how the recipient is named:

Recipient named asIn-appPushChat appsE-mailSMS
A member (user)YesYes, if they registered a deviceYes, if they linked an accountNoNo
A role (Owners, Admins, Members) or a teamAs for each memberAs for each memberAs for each memberNoNo
An e-mail addressNoNoNoYesNo
A phone number (flows only)NoNoNoNoYes

So in this release:

  • An alarm rule that names a role reaches those people in the bell, by push and in their chat apps. To get e-mail, add the address as an e-mail recipient ({ "kind": "email", "email": "…" }), for example an operations mailbox.
  • SMS is sent only to phone numbers named in a flow’s Notify block. Alarm rules and the Rules card cannot name phone numbers.

See Alarm notifications in depth and Notifications from rules and flows.

Restricting channels

A sender may name channels by their ids, for example ["inapp", "mail"]. Then only those are used. Without it, every channel the recipient allows is used. Chat channels have one id per platform: the platform’s name in lower case.

Switched off for the organisation

An administrator can turn whole channels off:

ChannelSwitch
SMSSettings > SMS > Enable SMS Notifications
PushSettings > Push Settings > Push notifications
Chat appsChat platforms > Disconnect (per platform)

A channel that is off is never used, not even for critical alarms.

Quiet hours

Quiet hours are a window of whole hours (for example 22 to 7) during which SMS, push and chat messages are not sent. They are worked out in each recipient’s own time zone (My Profile > Preferences > Timezone). In-app and e-mail are never held back: a late e-mail would only arrive out of order. A notification held back by quiet hours is not sent later on that channel; it is still in the bell.

Quiet hours are an organisation-wide setting. There is no page for them in this release; they are off unless your organisation has had them set. Critical alarms ignore them by default.

Plans and quotas

E-mail and SMS count toward monthly quotas of your plan (emailSends, smsSends). A plan without SMS sends no SMS. See Usage and quotas. In-app, push and chat messages do not count.

In development

  • The mobile app (notifications on phones, approvals on the phone) is in development. The push settings already mention app installs; nothing is sent to phones until the app is released.
  • Registering a browser for push from the web app is in development. See Browser push.
  • On-call rotations and escalation policies are not connected to IoT alarms. Use roles, reminders and severity rise instead.