Through your own SMTP, Resend or Postmark. The one channel that always works.
Where alerts go
Channels are destinations, not decisions. When to send, how often to remind and when to escalate is decided once and applies to all of them, so email and Telegram can never disagree about the same outage.
Available now
Telegram
A bot posting into a chat or a group. Popular with teams that do not live in Slack.
Slack
An incoming webhook into whichever channel you use for this.
Discord
Same, for teams and communities that run on Discord.
Outbound webhooks
Signed POSTs to your own endpoint, so you can put an outage into whatever you already use.
Not built yet
These appear in the channel list, greyed out, with their real settings. You can fill them in now and they will work the day they ship. We would rather show you what is missing than let you find out.
Browser push
Notifications on a desktop or phone without an app.
For teams where WhatsApp is where work actually happens.
SMS
Through UniSMS, for the alert that has to arrive when the internet does not.
And when they do not go
Maintenance windows suppress alerts and can be excluded from your uptime figures — separately, because muting the pager during known-noisy work should not automatically rewrite the number in your client report. Quiet hours hold reminders overnight but never the first alert or an escalation.
Set it up this afternoon
Add your first monitor in about a minute. Add the rest of the portfolio over a coffee.