Escalation

Escalation that follows how your response team actually works.

1stLine turns a Routing Rule into the right Escalation Chain, then carries the alert through Escalation Line steps, responders, and Communication rules without flattening your team into a roster.

From alert match to response Built around real coverage
  1. 01Routing RuleSend each alert to the Escalation Chain that fits the service.
  2. 02Escalation ChainKeep the next steps clear when ownership spans teams.
  3. 03Escalation LineMove through each response layer in the intended order.
  4. 04Escalation Line MemberPoint one step to Users, Teams, or Schedules.
  5. 05Users / Teams / SchedulesReach the people covered right now, not a stale list.
  6. 06Communication rulesPut SMS, calls, delays, repeats, and actions on the path.
Acknowledge Resolve Escalate further Escalate to Escalate to AI Start incident

Optional AI escalation

AI can help investigate. It should not replace responders.

Escalate an alert to an AI assistant you own, let it use approved context and MCP tools, then review the recommendation before any response action is taken.

More about AI Escalation

Why it wins

More than generic paging.

Escalation follows structure.A Routing Rule can route into an Escalation Chain with clear Escalation Line order, so alerts move through the same response model your team already uses.
Coverage stays flexible.One Escalation Line Member can point to Users, Teams, or Schedules, keeping coverage accurate without rebuilding the path for every service.
Response actions travel with the alert.Communication rules make SMS, calls, and responder actions part of escalation, from Acknowledge and Resolve to Escalate further, Escalate to, and Start incident.
01 Real response paths instead of flat on-call rosters.
02 Communication rules keep channels and timing tied to escalation.
03 Responders can move work forward without leaving the alert.