Notification channels are where alerts go. Alerts and recovery notices go to every enabled channel, unless a rule picks specific ones. Channels with an escalation delay only hear about alerts nobody acknowledged. Add as many channels as you need.
Supported channels
| Channel | What you need |
|---|---|
| Any email address. Each alert includes an Acknowledge this alert link. | |
| Slack | An incoming webhook URL (https://hooks.slack.com/…). |
| Microsoft Teams | A Teams workflow webhook URL (Workflows app → "Post to a channel when a webhook request is received"). |
| Discord | A channel webhook URL (Channel settings → Integrations → Webhooks). |
| Telegram | A bot token from @BotFather, and the chat ID or @channel name where the bot is a member. |
| A WhatsApp Cloud API phone number ID, a permanent access token, and the recipient phone with its country code. For alerts outside a recent chat, add a utility template that has one body variable. | |
| Push | An ntfy topic URL, plus an access token for protected topics. Install the ntfy app to get alerts on your phone. |
| Webhook | Any public HTTPS URL. Alertly.Net posts JSON. Add a Signing secret (16+ characters) to get an X-Alertly-Signature header. See Webhooks. |
Slack and Telegram messages get an Acknowledge button; other channels include the acknowledge link.
Webhook URLs and bot tokens are stored encrypted and never shown again after you save them. Leave a secret field empty when editing to keep the current value.
Test a channel
Use Send test on any channel. A test message is sent straight away, and you'll see an error if the service rejected it. The channel list shows when each channel was last used.
Quiet hours
Set From, Until and a Time zone, such as 22:00 to 07:00. Ranges can cross midnight. Warnings and recovery notices aren't sent during quiet hours; they're still on the alerts page in the morning. Tick Still send critical alerts (on by default) so emergencies get through. Grouped outage summaries are always sent.
Escalation
Under When to notify, choose an escalation delay (5 minutes to 2 hours) and the channel changes role: it only hears about an alert if nobody has acknowledged it within that time. See Escalation and on-call.
Grouping during outages
Once 5 alerts have gone out within 5 minutes (a network outage, for example), Alertly.Net holds new ones back. Each channel gets one summary a minute instead, listing up to 20 of them. Alerts that recover before the summary goes out are marked "already resolved". Recovery notices for other alerts are still sent one by one.
No channels yet?
While no channel is turned on, alerts and recovery notices are emailed to the team's owner and admins, so nothing slips through.