On-Call Escalation That Reaches a Human
Turn critical alerts into phone calls, require a human acknowledgement, and escalate automatically when nobody responds.
A notification is not the same as a response.
WakeUp Dev is designed for critical alerts where someone needs to actually acknowledge the incident—not just receive another message on a screen.
- Critical alert
- HTTP webhook
- Phone call
- Press 1 to ACK
- Escalate if unanswered
What is on-call escalation?
On-call escalation is the process of moving a critical alert to another responder when the first person does not acknowledge it within the expected time.
- A monitoring system detects a critical condition.
- The alert reaches the on-call responder.
- The responder receives a phone call.
- The responder presses 1 to acknowledge.
- If nobody answers or acknowledges, the alert moves to the next responder in the on-call cascade.
Why escalation matters
A missed notification can become a missed incident.
Push notifications, email, chat, and dashboards are useful—but critical incidents sometimes require an explicit human response.
For alerts that require a human response, a phone call combined with explicit acknowledgement can provide a clearer escalation path.
How WakeUp Dev handles on-call escalation
Alert arrives
Grafana, UptimeRobot, or another HTTP webhook source sends an alert to WakeUp Dev.
WakeUp Dev calls the responder
WakeUp Dev initiates a phone call to the first target in the configured on-call cascade—active shift phones, roster members, or your verified emergency number.
Human acknowledgement
During the call, the responder hears the alert summary and is prompted to press 1 on the phone keypad to acknowledge (ACK).
Escalation
If the call is not answered, fails, or completes without ACK, WakeUp Dev moves to the next phone number in the cascade until someone acknowledges or the cascade is exhausted.
On-call escalation vs notification
| Aspect | Notification | Escalation |
|---|---|---|
| Goal | Delivers an alert | Seeks a response |
| When nobody responds | May end with a push or email | Continues if nobody acknowledges |
| Confirmation | Depends on someone noticing | Uses an explicit ACK |
| Coverage | Often one notification channel | Can move to the next responder |
Who needs on-call escalation?
- DevOps teams responsible for production systems
- SRE teams monitoring uptime and reliability
- Small engineering teams without a dedicated NOC
- Teams accountable for production uptime
- Developers maintaining critical services
- Teams that need alerts to reach a human outside normal working hours
WakeUp Dev is not limited to these groups—it is built for any team that needs voice-first critical alerting with human ACK and cascade escalation.
Common on-call escalation scenarios
Production outage
Monitoring detects that a critical service is unavailable. The alert triggers a phone call; if nobody ACKs, the on-call cascade continues.
Database failure
A critical database condition fires an alert. WakeUp Dev calls the on-call engineer and waits for press-1 acknowledgement before stopping escalation.
API availability
An uptime monitor detects repeated failures. The webhook becomes a phone call with explicit human ACK and escalation if unanswered.
Infrastructure incident
A monitoring system flags a production infrastructure problem. Alert → call → ACK → escalate if nobody responds.
Voice-first escalation
WakeUp Dev focuses on the point where an alert needs to reach a person. The product combines:
- Phone calls
- Human acknowledgement
- On-call roster and shifts
- On-call cascade escalation
For critical alerts, teams may want a notification path that explicitly asks a human to respond—not merely that a message was delivered.
Pay per alert, not per seat
WakeUp Dev charges based on dispatched alert volume rather than per-seat licensing. Pro plans include 50 monthly alerts; the trial includes 5 free voice alerts with GitHub sign-in. Add on-call users without adding another per-seat license.
Integrations
WakeUp Dev accepts critical alerts from systems that send HTTP webhooks:
- Grafana
- UptimeRobot
- HTTP webhooks