Knowledge base
Choosing where alerts reach you
Email, webhook, Telegram or Slack — and which alerts are worth waking up for.
Help & alerts → Where notifications go, then Help & alerts → Email preferences.
Channels
Email — always available, to any address on the team. Webhook — a URL we POST to, for feeding your own systems. Telegram and Slack — for the ones you want on your phone.
Add a channel, verify it, and it becomes available to route alerts to. A channel that fails verification is not used, so an alert never disappears into a broken webhook.
Preferences
Per alert type, per channel. The types worth putting on a phone channel:
- Site down. The only one most people want to wake up for.
- Payment failed. Because the fix is on your side and time-limited.
- Backup failed twice running. One failure is noise; two is a problem.
Everything else — updates applied, certificates renewed, jobs completed — belongs in email, where it can be read in the morning.
Why it defaults to email only
Because an alerting setup that is too loud gets muted, and a muted channel is worse than no channel: it looks configured. Start with email, and move the two or three that genuinely matter onto your phone.
If you resell, hearing about your clients
You can opt in to receive your clients' alerts as well as your own, per destination — so a client's site going down can reach your on-call phone without your client having to tell you.
⛔ It is additive: your client keeps getting their own alerts exactly as before, and turning this on never replaces or silences them. It is you being added to the list, not you taking it over.
Who gets them
Alerts go to the organisation, and preferences are per person, so one member can take the phone alerts without everybody getting them.
Still stuck?
Support is included on every plan and answers in your own language.
Contact support → All articles →