Alert Channels & Team Routing
Pingzo delivers downtime notifications in under 15 seconds. Connect your preferred chat platforms, configure tag-based routing for team escalation, and correlate outages with external cloud dependencies.
Channel & Plan Availability Matrix
| Alert Channel | Supported Plans | Delivery Latency | Key Highlights |
|---|---|---|---|
| Email Alerts | Free, Starter, Pro, Agency | ~30 seconds | Primary and secondary team email inboxes with HTML summary. |
| WhatsApp (Official) | Starter, Pro, Agency | < 15 seconds | Direct WhatsApp Business notifications with OTP phone verification. |
| Telegram Bot | Starter, Pro, Agency | ~5 seconds | Instant alerts to personal Telegram or group channels via @Pingzoappbot. |
| Slack App | Starter, Pro, Agency | ~5 seconds | 1-click workspace OAuth integration with rich incident block embeds. |
| Discord App / Webhook | Starter, Pro, Agency | ~5 seconds | 1-click server authorization or custom incoming Discord webhooks. |
| Microsoft Teams | Starter, Pro, Agency | ~10 seconds | Office 365 / Microsoft Teams Incoming Webhook connector. |
| Custom HTTP Webhooks | Pro, Agency | Instant | Raw structured JSON POST payloads with automated retry policies. |
Tag-Based Alert Routing for Teams (Pro & Agency)
Eliminate alert fatigue by routing notifications to the right engineers
Instead of blasting every channel when a single service fails, Pingzo allows you to assign tags to monitors (e.g. #database, #frontend, #payments, #critical) and configure each alert channel to only receive alerts matching specific tags.
Only receives alerts for monitors tagged #database.
Receives alerts for #web and #marketing monitors.
Receives high-priority alerts for #critical services 24/7.
On-Call Duty & Shift Scheduling Guide
Route critical alerts only to responders who are currently on duty
On-call scheduling ensures engineers aren't pinged outside their shift hours or during off-days. Pingzo automatically evaluates each team member's active days, working hours, and local timezone during incident dispatch.
24/7 Always Active
Standard 24/7 alerting mode. Channels with this schedule receive alerts around the clock whenever an incident triggers for their configured stage and tags.
Custom Shift Rotations
Select specific active days (e.g. Mon–Fri) and active working windows (e.g. 09:00 to 18:00) with automatic browser timezone detection. Off-duty channels are silently skipped.
Key Features of On-Call Routing:
- Named Responders: Assign team member names (e.g.
Alex (DevOps Lead)) to channels. Alerts are personalized (“Hey Alex, your monitored service is DOWN”). - Live Duty Badges: The dashboard displays real-time
🟢 On-Duty Nowor⚪ Off-Dutybadges based on the user's current local time. - Seamless Handoffs: When an engineer goes off-shift, the next scheduled engineer seamlessly receives the next alert with zero manual toggles.
- Incident Attribution: Incidents record the active on-call responder in the audit trail, visible under
/dashboard/incidents.
Multi-Stage Automated Escalation Guide
Progressive incident escalation with user-configurable delays
When an outage goes unacknowledged or persists beyond initial resolution times, Pingzo automatically climbs the escalation ladder to alert secondary responders, team leads, or executives.
Immediate First Responder (0m Delay)
Starter • Pro • AgencyDispatched immediately (< 15 seconds) upon confirmed multi-region outage to all on-duty Stage 1 team members.
Secondary Lead Escalation (5m – 60m Configurable)
Pro • AgencyIf the outage is still active after your chosen threshold (e.g. 10m, 15m, 30m, or 60m), Stage 2 channels are automatically notified with an escalation notice.
Multi-Team & Executive Escalation (15m – 120m Configurable)
AgencyFor major prolonged outages, Stage 3 dispatches emergency alerts to secondary teams, engineering directors, or broadcast incident channels.
How to Set Up Escalation Rules:
- Go to Alert Channels and click Add Alert Channel (or edit an existing one).
- In the Escalation Stage dropdown, choose Stage 1 (Immediate), Stage 2 (Escalation), or Stage 3 (High-Priority).
- Select your desired Escalation Delay (e.g., 10 mins or 30 mins) before this channel is notified.
- Assign the team member name and on-call shift schedule, then save.
3rd-Party Dependency Outage Tracker
Correlate downtime with upstream vendor incidents
When an alert fires, the biggest question is: "Is our code broken, or is a vendor down?" Pingzo monitors external service health and attaches vendor incident context directly to your alert payload.
Supported Cloud Dependencies:
Stripe, OpenAI (ChatGPT & API), AWS (Amazon Web Services), Cloudflare, Vercel, Supabase, Neon Postgres, MongoDB Atlas, Upstash (Redis & QStash), GitHub, Twilio SendGrid, Postmark, Resend, and custom public status URLs.
Email Alerts (All Plans)
Email alerts are automatically enabled for your primary account email. To add secondary team member inboxes or distribution lists:
- Navigate to Alert Channels > click Add Alert Channel.
- Select Email and input the target recipient address.
- Click Save Channel. Pingzo will send a test alert confirmation.
WhatsApp Alerts (Starter, Pro, Agency)
Pingzo hooks directly into the official WhatsApp Business API for sub-15 second downtime notifications:
- Navigate to the Alert Channels tab in your dashboard.
- Click Add Alert Channel and select WhatsApp.
- Enter your phone number including country code (e.g.
+919876543210). - Click Send Verification Code to receive an instant OTP via WhatsApp.
- Enter the code to verify and activate the recipient.
Telegram Bot Alerts (Starter, Pro, Agency)
Deliver alerts to your personal Telegram or group chat:
- Select Telegram in the Add Alert Channel modal.
- Open the official bot: @Pingzoappbot.
- Click Start (or send
/start). - Copy the Chat ID returned by the bot, paste it into Pingzo, and save.
Slack & Discord Integrations (Starter, Pro, Agency)
Slack App (1-Click OAuth)
Click Add to Slack, select your team workspace and target notification channel. Webhooks are managed automatically.
Discord App & Webhooks
Click Add to Discord or paste a custom incoming Discord webhook URL to deploy rich embed downtime and recovery cards.
Microsoft Teams Webhook (Starter, Pro, Agency)
In your Microsoft Teams channel, open Connectors > add an Incoming Webhook > copy the webhook URL and paste it into Pingzo under MS Teams.
Custom HTTP POST Webhooks (Pro & Agency)
Pingzo sends a structured JSON payload to custom HTTP POST endpoints whenever a monitor goes down or recovers:
{
"event": "monitor.down",
"timestamp": "2026-09-29T04:20:00Z",
"monitor": {
"id": "cmq_monitor_123",
"name": "Production Database",
"url": "db.internal.mybrand.com",
"type": "port_tcp",
"port": 5432,
"tags": ["database", "prod"]
},
"incident": {
"id": "inc_987654",
"error": "TCP Socket Connection Timeout (10000ms)"
}
}