Groups per monitor
Bundle channels into a group and attach it to any monitor. Change the recipients once and every monitor using the group follows.
13 channels, from email and SMS to Slack, Microsoft Teams and PagerDuty. Group them, attach a group to each monitor, and the right people hear about it.

Monitor alerts in Site Qwality are routed by notification group. A group bundles destinations, and each monitor picks the groups it alerts. A failure on your payment API can text the engineer who owns it, post to #sre in Slack and call a webhook in your incident tool, while the blog health check only sends an email.
Bundle channels into a group and attach it to any monitor. Change the recipients once and every monitor using the group follows.
Wait a set number of minutes before the first alert, and repeat it while the monitor stays down.
Acknowledge an outage from the monitor page or the link in the alert email, and the repeats stop. The recovery alert still arrives.
Incidents on a service reach responders through its escalation policy and on-call schedules. Each responder sets how they are contacted (email, SMS or a Slack direct message) for high and low urgency.
Put a shared Slack channel and one engineer’s mobile number in the same group, so the team sees the alert and one person is texted directly.
See what was sent where, and whether it arrived, failed or was skipped, with the reason.
Not every monitor deserves the same urgency. Give the monitors that matter most a group that texts and posts to Slack, and give the rest a group that only emails, so real outages wake people up and minor ones wait for the morning standup.
Every plan, including the free tier, includes every channel with no add-on charge. Put Slack, SMS and webhooks in the same group without upgrading.
notification channel types included on every plan
no add-on charge for any notification channel
fastest check interval
longest delay or repeat interval you can set on a group
Email, SMS, Slack, Microsoft Teams, Discord, Telegram, Google Chat, Mattermost, outbound webhooks, PagerDuty, Jira Service Management (Opsgenie), Pushover and Pushbullet, all included on every plan.
Yes. A notification group can hold several destinations, and a monitor can use several groups. Every destination in those groups is sent the alert, for example an SMS to the engineer who owns the service and a Slack message to the #sre channel.
Yes. Give critical monitors a group that texts and posts to Slack, and the rest a group that only emails. For incidents, each responder sets separate rules for high and low urgency.
SMS is built in, with no Twilio account required. Every plan includes free credits each month, and you can buy packs for more. See pricing.
A notification group is a reusable bundle of channels and recipients. Assign the group to any monitor and update its members in one place. All monitors using that group are updated automatically.
That channel sends through Opsgenie, which Atlassian will shut off on April 5, 2027. If you are moving, send alerts to Slack, email, SMS, PagerDuty or a webhook instead, or use Site Qwality’s own on-call. The Opsgenie migration guide has the steps.
Uptime, cron, synthetic, logs, RUM, incidents, and status pages. Free tier on every product.