Channels
Always available, with action links to acknowledge and take ownership.
Push
Browser and mobile. The channel that actually wakes someone up.
Slack
A card in the team channel, with actions.
Microsoft Teams
An Adaptive Card in the team channel.
Discord
A message in your server channel, with actions.
Telegram
A message in a group, topic or channel, via your own bot.
When each notification is sent
How the channels combine
The channels do not replace each other — they stack, and each has a role:1
Push is the paging channel
It is the only one that reliably pulls someone out of sleep. It must be active for anyone in the rotation.
2
Email is the record channel
It always arrives, carries the full context and leaves an auditable trail.
3
Slack, Teams, Discord and Telegram are the team channel
They give collective visibility: who else is watching, who already acknowledged, what the status is.
Slack, Microsoft Teams, Discord and Telegram messages go to the configured channel regardless of whether personal recipients were resolved. Even if the schedule fails to point at anyone, the team still sees the incident in the channel.
Organization and teams
Each channel integration has an organization configuration, used by default, and optional team overrides. That way the payments team can get its own channel while everyone else uses the general one. The Test button sends a test message to confirm the destination before a real incident.Delivery record
Every notification attempt is recorded with channel, destination, status, attempt count, error (if any) and send time. That makes “was I paged?” a question with a precise answer. The incident moves tonotified when any channel delivers successfully.