Alerts

Downtime alerts in Slack, email, and four more channels

Free includes email and Slack. Pro and Business add Discord, Teams, Telegram, and signed webhooks with custom payloads. Pages go out after multi-region consensus confirms an outage — not after one flaky probe.

Six channels

Email, Slack, Discord, Telegram, Microsoft Teams, and signed webhooks.

Programmable payloads

Shape every webhook with a custom payload template. No fixed JSON to wrestle with.

Only when it is real

Alerts fire on a confirmed multi-region incident, deduplicated per event and channel so nothing pages twice.

Test before you trust

Send a test alert to any channel before a real incident ever fires.

Delivery

Connect a channel. Route it through on-call.

Attach channels to escalation policies so the current on-call gets the page. Alerts fire after consensus, then dedupe per event and channel. Failed deliveries retry with backoff.

Connect your channels
Add a channel in a click: Slack, Discord, Telegram, Teams, email, or a signed webhook.
Shape the payload
The webhook channel ships a payload-template editor, so downstream gets exactly the JSON it expects.
Route through policies
Channels attach to escalation policies, so the right people hear about the incidents that matter to them.
Deduped, with retries
Each open, ack, and resolve is sent once per channel. If delivery fails, Tallwatch retries with backoff.

FAQ

Alerting, answered

What teams ask before they route their downtime alerts through Tallwatch.

Go deeper on alerting

How consensus keeps alerts honest, why multi-region matters, and where Tallwatch lands against the field.

How Tallwatch stops false alerts

The consensus model behind alerts that fire only on a real, multi-region incident.

Multi-region monitoring, explained

Why checking from several regions at once is what makes an incident trustworthy.

The best uptime monitoring services in 2026

How Tallwatch compares on alerting, channels, and pricing across the field.

Documentation

Setup guides

Step-by-step docs on docs.tallwatch.com for this part of the product.

Alerts overview

Connect Slack, Discord, Teams, Telegram, email, or webhooks.

A page after regions agree — not after one probe fails.

Start on Free with multi-region consensus. No credit card.

Start free

Agent

Page as markdown

Raw agent-readable copy for this route. Copy it into a model, or browse the site-wide agent index at /llms.txt.

---
title: "Alerts"
description: "Email, Slack, Discord, Telegram, Microsoft Teams, and signed webhooks."
canonical: https://tallwatch.com/services/alerts
url: https://tallwatch.com/services/alerts
llms_url: https://tallwatch.com/llms.txt
updated: 2026-09-02
---
Alerts

# Downtime alerts in Slack, email, and four more channels

## Six channels

Email, Slack, Discord, Telegram, Microsoft Teams, and signed webhooks.

## Programmable payloads

Shape every webhook with a custom payload template. No fixed JSON to wrestle with.

## Only when it is real

Alerts fire on a confirmed multi-region incident, deduplicated per event and channel so nothing pages twice.

## Test before you trust

Send a test alert to any channel before a real incident ever fires.

Delivery
## Connect a channel. Route it through on-call.

Attach channels to escalation policies so the current on-call gets the page. Alerts fire after consensus, then dedupe per event and channel. Failed deliveries retry with backoff.

1. **Connect your channels** — Add a channel in a click: Slack, Discord, Telegram, Teams, email, or a signed webhook.

2. **Shape the payload** — The webhook channel ships a payload-template editor, so downstream gets exactly the JSON it expects.

3. **Route through policies** — Channels attach to escalation policies, so the right people hear about the incidents that matter to them.

4. **Deduped, with retries** — Each open, ack, and resolve is sent once per channel. If delivery fails, Tallwatch retries with backoff.

FAQ
## Alerting, answered

What teams ask before they route their downtime alerts through Tallwatch.

### How does Tallwatch cut down false alerts?

Checks run from multiple regions in the same round. An incident opens only when at least two of those regions agree the target is down. One flaky region alone does not open an incident. Consensus is on every plan, including Free.

### Which alert channels does Tallwatch support?

Six: email, Slack, Discord, Telegram, Microsoft Teams, and signed webhooks. Free includes email and Slack. Paid plans include all six.

### Does Tallwatch send SMS or phone-call alerts?

No. There is no native SMS or voice. Use a webhook into Rootly (or similar) or a chat channel if you need mobile paging.

### Which channels are on the free plan?

Email and Slack. Discord, Telegram, Microsoft Teams, and signed webhooks need Pro or Business.

### Can I customize the webhook payload?

Yes, on Pro and Business. You write a template for the JSON body. Every webhook request is cryptographically signed.

### Will I get duplicate alerts for the same incident?

Tallwatch deduplicates per event (open, acknowledge, resolve) and per channel. Escalation can still notify the next level or another channel if nobody acknowledges in time. Failed deliveries retry with backoff.

### Can I test an alert before a real incident?

Yes. Send a test alert to any channel to confirm the connection and payload before you rely on it.

Related reading
## Go deeper on alerting

How consensus keeps alerts honest, why multi-region matters, and where Tallwatch lands against the field.

- [How Tallwatch stops false alerts](https://tallwatch.com/blog/how-tallwatch-stops-false-alerts): The consensus model behind alerts that fire only on a real, multi-region incident.
- [Multi-region monitoring, explained](https://tallwatch.com/blog/multi-region-monitoring-explained): Why checking from several regions at once is what makes an incident trustworthy.
- [The best uptime monitoring services in 2026](https://tallwatch.com/blog/best-uptime-monitoring-services-2026): How Tallwatch compares on alerting, channels, and pricing across the field.