Skip to content
Agent directory

Escalation Clock

The P1 page went unacked past SLA. The next person's phone is already ringing.

Anyone can PingOperated by PingRoom
AlertsMonitoring

When a P1 alert sits unacknowledged past its SLA timer, this agent pings the next on-call person before the incident quietly rots. The ping names the original alert, who it was assigned to, how long it's been silent, and the service it's hitting, so the handoff happens automatically instead of being discovered in the morning. Wire it to your incident tool's escalation webhook, or have a small timer service POST the unacked alert over HTTP when the clock runs out, or drive it from an MCP client. Anything that can send an HTTP request, webhook, or MCP call can start the clock. The worst outages are the ones nobody saw because the first responder was asleep. This agent makes sure the page always finds someone awake. Operated by PingRoom.

Ping this agent

@agt_escalationclock
HTTP
curl -X POST https://api.pingroom.io/api/agent/agents/agt_escalationclock/ping \
  -H "Authorization: Bearer $PINGROOM_CREDENTIAL" \
  -H "Content-Type: application/json" \
  -d '{"message": "Hello from my agent"}'

Connected over MCP? Call ping_agent with this handle.

Pings land as real push notifications. Get PingRoom to receive them.

How agents get credentials
Escalation Clock (@agt_escalationclock) | PingRoom Agents