Multi-channel alerting features for on-call teams
Route incidents from monitoring tools into Telegram, phone calls, SMS, email, WhatsApp and escalation policies with delivery history.
Five pillars
Built around the same five concerns
Routing, escalation, templates, security and observability — explained in plain language, not buzzwords.
01 · Routing
Multi-channel routing
Send a single alert to Telegram, voice, SMS, email, WhatsApp and Viber in one declarative policy. Channels run in parallel per step.
02 · Escalation
Acknowledgement-aware chains
Chains run until someone acknowledges. Sources that send a resolved hook cancel the chain automatically; manual ack stops it from any channel.
03 · Templates
Reusable alert presets
Define an alert template once, fire it from any service with one POST /from-template/<slug>. Versioned, plan-gated, slug becomes a stable contract between your monitoring stack and WardenPoint.
04 · Security
Scoped keys, multi-tenant
API keys per integration, UUID-only public IDs, SetCurrentCompany middleware on every authenticated route. No cross-tenant leakage in tests.
05 · Observability
Structured audit log
Every dispatch, ack, escalation and resolve writes a JSON line. CSV export per recipient group; linked to application logs via request_id.
Escalation policy
Policies live as code
Express your escalation chain as a declarative array. No UI clicks; test in CI; review in pull requests.
See it in the API examplesResponder UX
Validate your alerting in one click
A guided wizard on the dashboard sends a real alert through the full pipeline so you can prove channels and escalation work for your team before the first incident.
Test alerts in 30 seconds
A guided wizard on the dashboard sends a real alert through the full pipeline — no need to wire up monitoring first. Proof that channels and escalation actually work for your team.
Product proof
See the full alert lifecycle before an outage
WardenPoint shows how a monitoring signal becomes routed delivery, escalation, acknowledgement and audit history instead of disappearing into one inbox.
From signal to accountable response
Received
A webhook, API call or dashboard alert enters WardenPoint with service and severity context.
Routed
Recipient groups, priority and policy rules choose the first responder and channel order.
Delivered
Telegram, email, SMS, voice calls or other channels deliver the alert to the team.
Escalated
If nobody acknowledges, WardenPoint continues to fallback channels and backup responders.
Acknowledged
The escalation path stops when the right person confirms they are handling the incident.
Audited
Delivery attempts, timing and acknowledgement state stay visible for post-incident review.
0 min — Telegram + email
Start with fast channels for the primary on-call responder.
3 min — SMS fallback
If the alert remains unacknowledged, move to a harder-to-miss channel.
5 min — voice call + backup
Wake the backup responder when the primary path still has no response.
Know which channels were attempted and when each one fired.
See why the workflow moved from primary responder to fallback paths.
Keep the final acknowledgement and timing attached to the incident history.
Features FAQ
Common feature questions
- Telegram (text + voice + VoIP) and email are unlimited on free. Voice calls, SMS, WhatsApp and Viber are pay-as-you-go on top of any plan and require a credit balance.
Wire your first escalation chain on the free plan
Telegram alerts, audit log and the REST API are unlimited on free. Add voice and SMS credits only when you need them.
- Free plan forever
- Declarative policy
- Audit log built in