WhatsApp uptime alerts reach people Slack misses

Your site goes down at 2:14am. Slack posts into a channel nobody has open. Email sits in a promotions tab. The on-call engineer is asleep with a phone that only buzzes for WhatsApp.

That is not a hypothetical in most of the world. WhatsApp has more than two billion users. In Latin America, Africa, India, and Southeast Asia it is the default inbox. Monitoring tools still pretend Slack is universal. It is not.

The channel mismatch

Uptime tools grew up in US and European SaaS. Slack, email, and PagerDuty cover that world well. They cover a founder in São Paulo, Lagos, or Jakarta poorly.

SMS works, but it is expensive, easy to filter, and ugly. Telegram is excellent and Uptrack already supports it. Telegram is still a power-user app. WhatsApp is where the rest of the team already lives.

If the alert does not land in the app people open, it is not an alert. It is a log line.

What Uptrack sends

WhatsApp is now a first-class alert channel, next to email, Slack, Discord, and Telegram. A down event looks like this:

Recovery, degraded (early-warning), and degraded-recovered messages use the same path. Consecutive-check confirmation still applies. A single DNS blip does not wake you on WhatsApp either.

1-minute checks are available on the free plan. HTTP monitors on free actually run every 30 seconds. That is the entry point. WhatsApp is how the result reaches you.

How to turn it on

Three steps. No bot hosting. No webhook URL to copy from a Slack app directory.

1. Send any message to the Uptrack WhatsApp business number. Meta requires this opt-in.
2. In Uptrack, open Dashboard → Alerts → Add Channel, choose WhatsApp, and paste your number in E.164 format (+12025550123).
3. Send a test. You should see a sample down alert on WhatsApp.

If you already run a Meta WhatsApp Cloud API number, you can bring your own credentials. Create the channel with access_token and phone_number_id in the config object. Uptrack will not mix a user token with our phone-number id.

curl -X POST https://api.uptrack.app/api/alert-channels \
  -H "Authorization: Bearer $UPTRACK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "On-call WhatsApp",
    "type": "whatsapp",
    "config": { "phone_number": "+12025550123" }
  }'

Node and Python look the same: POST JSON with type: "whatsapp" and an E.164 phone_number.

await fetch('https://api.uptrack.app/api/alert-channels', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.UPTRACK_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    name: 'On-call WhatsApp',
    type: 'whatsapp',
    config: { phone_number: '+12025550123' },
  }),
})

Where we win, where we don't

Honest comparison. WhatsApp support is new. Some tools have had it longer. Most still skip it.

Where we don't win: Uptrack sends to one phone number per channel, not a WhatsApp group. Meta also requires an opt-in message before the first alert. If you need a 40-person incident room with threads and @here, Slack or Discord is still the better fit.

Use cases

Chat apps we should support next

WhatsApp is the highest-reach consumer chat app. It is not the only gap. If we add more channels, this is the order that matches real on-call behavior:

1. Microsoft Teams. Default chat for companies that standardized on Microsoft 365. Incoming webhooks are well documented. The changelog already promised this; it is not wired yet.
2. Google Chat. Same story for Google Workspace shops. A Chat incoming webhook is a single POST, close to Discord.
3. Mattermost. Self-hosted Slack alternative. Incoming webhooks look like Slack attachments. High overlap with our existing Slack dispatcher.
4. LINE. Dominant in Japan, Taiwan, and Thailand the way WhatsApp is in Brazil. Messaging API is official and bot-based, similar to Telegram.
5. WeCom (WeChat Work). The work chat for China. Consumer WeChat is a harder compliance story; WeCom is the realistic first step.
6. Matrix / Element. For teams that refuse a US-hosted chat vendor. Homeserver bots are more work than a webhook, but the audience is vocal.

We would skip Signal (no stable public bot API), IRC (too few on-call users), and another generic webhook clone of Slack. Rocket.Chat and Zulip are reasonable later, after Teams and Google Chat.

FAQ