You configure channels once at the project level, and they cover every monitor type: cron checks, uptime monitors, port monitors, SSL watches, domain expiration, blocklist monitors. Connect Slack to a project, and every monitor in that project can use it. No copy-pasting webhook URLs into each check one by one.

01 — 22 channel types, plan controls how many#
Every plan has access to the same core set of channel types: email, Slack, Telegram, Discord, Microsoft Teams, webhooks, PagerDuty, OpsGenie, Mattermost, Rocket.Chat, Matrix, Signal, Zulip, Pushbullet, and Trello. What changes between plans is how many channels you can create and whether premium delivery types are available.
Free gives you 3 channels. Pick any three from the list above. A solo developer might choose email, a Slack channel, and a Telegram bot. That covers most setups. Starter raises the limit to 10, enough for a small team routing different monitors to different rooms. Pro goes to 25, Business removes the cap entirely.
SMS opens on Pro. Voice calls and WhatsApp open on Business. We grouped the expensive delivery types on higher tiers because each SMS or call has a real carrier cost behind it, and absorbing that on a free plan would mean metering by volume instead. The plan price is the whole price. A rough week with a hundred SMS alerts doesn't move the bill.
One thing we didn't want to copy from competitors: per-alert billing. Cronitor and Better Stack meter SMS and voice by credit or by volume tier. Here, if your plan includes SMS, every alert is included. No credits to run out of at 3 AM.
02 — How alerts route to the right channel#
Channels live at the project level, not per monitor. You connect a Slack workspace or paste a Telegram bot token once, and every monitor in that project can use it. Each monitor then picks which of the available channels it should alert through. A database backup might notify Slack and email. A payment-critical uptime check adds SMS and PagerDuty on top.

When a monitor flips from Up to Down (or moves through Grace into Down, for cron checks), the alert fires to every active channel assigned to that monitor. Recovery notifications go the same way: when the monitor comes back, the same channels get a resolution notice. No manual closing required.

Each channel type carries the right information for that medium. A Slack message includes the monitor name, the new status, how long it was down, and a direct link back to the dashboard. An SMS keeps it to one line: what failed and when. A PagerDuty event maps to an incident with the right severity so your existing escalation policies take over from there.
03 — Webhooks as the escape hatch#
Webhooks turn WatchCron into a trigger for any system that accepts HTTP. The payload is a JSON object with the monitor ID, name, old status, new status, and a timestamp. Straightforward enough to pipe into Zapier, n8n, a Lambda function, or a short script on your own server. Webhooks count toward your channel limit like any other type, but they're available on every plan, including Free.
Common uses: opening Jira tickets on downtime, flipping a feature flag when a dependency stops responding, posting to internal chat instances that don't have a native integration. The payload format is stable and documented, so building automation on top of it is safe.
04 — What multi-channel alerts don't replace#
Multi-channel alerts notify your team. They don't notify your customers. Different audiences, different tools. For customer-facing communication during outages, pair alerting with a public status page and incident management, both included on every plan.
Alert deduplication and on-call rotation are also outside scope. If your team runs formal on-call schedules with escalation windows, the PagerDuty and OpsGenie integrations on Business hand the incident off to those systems. We trigger the alert. They manage who gets paged and when.
Route alerts through 22 channel types. Free plan: 3 channels (your choice of type), 20 checks, no credit card. No per-alert charges on any plan.