An escalation policy controls what happens when a notification isn't acknowledged. Each policy is a list of levels, and each level says "after N minutes, do X." If nobody answers the call, sends the SMS reply, taps the push, or clicks the email link, the policy advances to the next level.
Plan availability: Escalation policies are available on the Starter plan and up. See Plans & Billing.
In JAMS Incident Management, a policy belongs to an on-call rotation. The Support Rotation has its own escalation behavior. The Database Rotation has its own. A flow that targets a rotation automatically inherits that rotation's policy β you don't have to remember to wire it on every flow.
Setup
Open On-Call Rotations, pick the rotation you want to configure, and click Add Escalation (or Edit Escalation if one already exists).
You'll see a modal that lets you build the escalation ladder one level at a time:
Level 1 Mode: Notify current on-call Escalate after: 10 minutes
Level 2 Mode: Re-notify the same person Escalate after: 10 minutes
Level 3 Mode: Next person in rotation Escalate after: 20 minutes
Level 4 Mode: Notify a different rotation β Manager Rotation
Each level has three things to configure:
- a mode: who this level notifies
- an escalate-after timer: how long to wait before moving on if nobody acknowledges
- Notify via: which channels this level uses. Leave it on Flow's channels to keep the usual behavior. See Choosing channels for each level.
Each level's timer is honored independently. A 10 / 10 / 20 ladder advances 10 minutes after Level 1, another 10 minutes after Level 2, then 20 minutes after Level 3 β each wait is measured from when the previous level fired, not from a single flow-wide clock.
The six modes
Notify current on-call
Pages whoever is currently on-call for the rotation. This is the typical Level 1 β the first ping.
Re-notify the same person
Pages the same person who was notified by the previous level. Use this when the failure mode is "did they see it?" β sometimes the first call goes to voicemail, the first SMS gets buried, and a second ping fixes it.
Next person in rotation
Advances to the next member in the rotation order and notifies them. Use this when the failure mode is "they're truly unavailable" β the on-call is in a meeting, on a plane, or asleep, and someone else needs to step in.
Notify a different rotation
Escalates out of the team entirely β e.g., to a Manager Rotation or a Director Rotation. Pick which rotation(s) to escalate to when you choose this mode.
Notify specific people
Pages specific people directly, by name. They don't have to belong to any rotation. Use this for a fixed fallback β a manager or director who should be pulled in if nobody on the team answers.
To add people, choose this mode and use the + Add a person⦠list under it. Each person you add appears as a chip, and you can keep adding more. Everyone on the level is paged at the same time. To remove someone, click the à on their chip.
Notify rotations and people together
Pages the on-call person of one or more rotations and one or more named people, all at the same time on one level. For example: "page the Support on-call and the duty manager together." Splitting this across two levels is not the same thing, because the second level would only fire after the first one's timer runs out.
You'll usually see this mode on policies brought in from PagerDuty, where one rule can target both a schedule and a person.
Choosing channels for each level
By default, every level notifies people on the flow's channels. If the flow uses Call and SMS, every level calls and texts.
Notify via lets a level choose its own channels instead. Two examples:
- Level 1 is Kevin, who only wants SMS. Level 2 is Rob, who should get a Call.
- A level pages a team that works in WhatsApp, and nothing else.
To set it up
- Open the escalation for a rotation (see Setup), or open a policy on the Escalation Policies page.
- On the level, find Notify via under the mode and timer.
- Choose Choose channels, then tick the channels you want: Call, SMS, Email, Push, Teams, Slack or WhatsApp.
- Save the policy.
To go back to the usual behavior, choose Flow's channels. A level with Choose channels selected but nothing ticked also uses the flow's channels.
How it behaves
- The ticked channels replace the flow's channels for that level. They aren't added on top. A level set to SMS sends only an SMS, even if the flow also uses Call and Email.
- It applies to everyone the level notifies. If a level pages a whole rotation or several people, they all get the same channels.
- Other levels are not affected. Each level is set separately, and a level you leave alone keeps using the flow's channels.
- Teams and Slack channel posts don't change. If the flow posts to a shared Teams or Slack channel, that post still goes out once for the alert. Notify via only changes how people are notified.
When a channel can't reach someone
Some channels need the person to have done something first:
| Channel | Needs |
|---|---|
| SMS | A phone number, and the person has opted in to SMS |
| Call | A phone number |
| An email address | |
| A phone number, and the person has verified WhatsApp | |
| Push | At least one device with push turned on |
| Teams / Slack | The person has linked their Teams or Slack account |
You're warned while you set it up. When you tick a channel that can't reach someone on the level, a yellow note under the channels names them and gives the reason, for example "Rob: SMS β not opted in to SMS." For a rotation, we check everyone who could be on call, not just whoever is on call today.
Nobody is skipped. If none of a level's ticked channels can reach a person, that person is notified on the flow's channels instead, and the yellow note says so. If at least one ticked channel reaches them, they get just those. Either way the alert still reaches them, and the escalation timer still runs normally.
To fix a warning, ask the person to complete the missing step: opt in to SMS or verify WhatsApp on their profile, turn on push on their device, or link Teams or Slack. Or tick a channel they can already receive. The note disappears once everyone on the level can be reached.
SMS opt-in is never bypassed. Someone who hasn't opted in to SMS, or who replied STOP, never gets a text β not from a level, and not as a fallback.
Plan and usage
Escalation policies need the Starter plan, and Starter includes every channel, so any plan that has escalation policies can use any channel on a level. SMS, WhatsApp and Call sent by a level count toward your allowance in the usual way. See Plans & Billing.
Example: the classic 3-level support pattern
Support Rotation
Members: Alice, Bob, Charlie (weekly handoff)
Escalation:
Level 1 Notify current on-call β 10 minutes
Level 2 Re-notify the same person β 10 minutes
Level 3 Next person in rotation β 20 minutes
Level 4 Notify a different rotation β Manager Rotation
A flow targeting the Support Rotation now behaves like this:
0:00 Alice gets paged (on the flow's channels, e.g. call + SMS + push)
0:10 Alice gets paged again β same ping, second chance
0:20 Bob gets paged (next in rotation)
0:40 Manager Rotation's current on-call gets paged
If Alice acknowledges at any point, the chain stops immediately. The same goes for Bob, the Manager, or anyone else in the policy.
Manual escalate from the alert
Sometimes the on-call person knows they can't handle this one β they're heads-down on something else, or it's outside their expertise. They don't have to wait for the timer to expire.
When there's a next responder to escalate to, every channel offers a manual escalate option:
- Voice call: "Press 1 to acknowledge, press 2 to repeat, press 3 to escalate"
- SMS: reply
1to acknowledge,3to escalate - Push notification: tap the Escalate action button
- Email: click the Escalate button next to Acknowledge
Hitting escalate jumps straight to the next level β no waiting.
Why this matters: the escalate option only appears when someone is queued after the current recipient. A single-recipient dispatch β the last level of a policy, or a flow that notifies just one person β has nowhere to escalate to, so no channel shows an escalate option for it. You'll still see Acknowledge and Repeat.
What happens after the last level
If the chain runs all the way through every level and still nobody has acknowledged, the policy doesn't give up. It waits the last level's own escalation window β measured from the most recent notification, so the final responder gets their full window β and then starts the whole ladder again from level 1.
There is no round cap. It keeps cycling until one of these ends it:
- Somebody acknowledges. One acknowledgement resolves every channel in the group.
- You deactivate the flow. Pausing the flow cancels the group instead of re-queuing it.
- The flow's cooldown throttles it. See Runaway control for the anti-loop limits that stop a misbehaving source from paging repeatedly.
So an alert nobody answers keeps asking. That is deliberate β an unacknowledged critical alert going quiet on its own is the failure this product exists to prevent β but it does mean a flow pointed at a source that fires constantly needs its cooldown set, not just its escalation policy.
Repeating the whole policy on purpose
A policy has a Repeat setting (1β10, default 1) on the Escalation Policies page. It controls how many times the entire ladder is queued up in one dispatch β the equivalent of PagerDuty's "num loops".
With Repeat set to 3, a two-level policy queues six steps at once: levels 1, 2, 1, 2, 1, 2. This is different from the looping above:
| Repeat | The loop after the last level | |
|---|---|---|
| Set by | You, per policy | Automatic |
| When | Planned up front, at dispatch | Only after every step has been sent |
| How many | Exactly what you chose | Until acknowledged or stopped |
Leave Repeat at 1 unless you specifically want a second pass to arrive faster than the post-ladder loop would deliver it.
No escalation policy: the default
A flow whose recipient has no escalation policy still escalates β it just uses one uniform timer instead of per-level timers. JAMS Incident Management notifies the first recipient, waits the flow's own escalation interval (default 5 minutes), advances to the next recipient, and repeats. Every step uses the same interval. You set this interval when you build the flow; see Core Concepts for where it lives.
The per-level timers described above are a feature of escalation policies specifically. Without a policy, you get the single flow-wide interval.
Wiring it to a flow
You don't. That's the point. Build a flow, pick an On-Call Rotation as the recipient, and the rotation's policy drives delivery automatically. The flow doesn't need to know what the policy is.
If you change a rotation's policy later, every flow that targets that rotation picks up the change immediately β no flow edits needed.
Removing a policy
In the rotation's escalation modal, click Remove Policy. The rotation reverts to legacy round-robin behavior β notify the current on-call, wait the flow's own escalation interval, advance to the next person, repeat.
Advanced: the Escalation Policies page
The standalone Escalation Policies page lets you build policies that aren't owned by any single rotation. This is useful in unusual cases β e.g., a policy where Level 1 targets two different rotations simultaneously. Most teams won't need this; rotation-owned policies cover the common patterns.
On this page, each level can notify:
- one or more on-call schedules, by clicking their chips, and/or
- one or more people, using Notify these people (optional) and + Add a personβ¦
Everything you pick on a level is paged at the same time. Each level also has Notify via, which works exactly as described in Choosing channels for each level.
Policies that belong to a rotation show Edit on On-Call instead of Edit. Their levels mean things like "whoever is on call in this rotation" or "the next person in this rotation", which only make sense in that rotation's editor. Click it to go to On-Call Rotations and edit the policy there.