If I miss the page, can it go to the next person on the list and keep repeating until someone acknowledges?

How a SoloNOC escalation policy pages the next person when the first does not answer, repeats the cycle until someone acknowledges, and what it does not do yet.

Short answer

Yes, and proven on the loop’s real SQL (2026-11-07). An escalation policy pages tier 1 (each person’s iPhone and email, and any channel), then tier 2 after its delay, and with Repeat after set it starts again at tier 1 until someone acknowledges or the alert resolves. It is a fixed list, not a rota with shifts.

Updated 2026-11-07. Every quote links to where it was published.

In admins’ own words

“we are looking for something that will call down the list until someone answers and repeat the cycle until someone acknowledges the alert.”

r/msp post, 2025-09-04 · source

“The manager took vacation and chaos followed.”

r/msp post, 2024-11-21 · source

What it is

A one-person shop still has a second name for the night it cannot answer: a partner, a contractor, the owner of the client. The page has to reach that name by itself, and keep going until somebody owns the problem, because the alert that nobody acknowledged is the one that becomes an outage in the morning.

What breaks in practice is not the first page but the hand-off: a forwarding rule someone set by hand, a manager on holiday, a phone that was on silent. The list has to live in the monitor, next to the alert, and stop the moment anyone acknowledges.

How SoloNOC does it

  • An escalation policy is a list of tiers, each with a delay, the people it pages and the channels it posts to, and an optional Repeat after; an admin creates and edits it on the Escalation Policies page. (pinned by: webFeaturesB.spec.ts)
  • Each tier sends a push to its people’s iPhones and an email to each of them; with Page me and Repeat after the page comes again while the alert is still firing, and stops when it is acknowledged. (pinned by: ruleActions.spec.ts, escalationPageMe.test.tsx, silent_mode_proof.py)
  • An escalation starts once per policy and alert, only for an alert still firing, and a notification rule can name the policy a critical alert starts. (pinned by: alertPolicy.spec.ts, notices.spec.ts)

A worked example

  1. Tier 1 pages you at once; tier 2, ten minutes later, pages your contractor; Repeat after 15 starts again at you. You acknowledge at 2:14 on the phone and nobody else is woken. (pinned by: ruleActions.spec.ts, webFeaturesB.spec.ts)
  2. Proven on a real Postgres with the production schema: three full tier-1 → tier-2 → repeat cycles, each tier reaching only its own person; acknowledge and resolve each ended the escalation on the next pass; a policy with no Repeat after stopped after its last tier. (pinned by: escalationCycle-realdb.mjs)
  3. What that database did, pass by pass, is recorded and held by the test suite that runs without a database — including that nobody else’s phone and no channel the policy did not name was ever reached — and the record carries a fingerprint of the escalation SQL, so the cycle cannot change without being measured again. (pinned by: escalationCycle.spec.ts, escalationCycle-vectors.json)

The bar we measure it against

An escalation policy pages tier 1, then tier 2, and after the last tier starts over every repeat_after_minutes until the alert is acknowledged or resolved; acknowledgement stops it at once; proven by a loop test on the real SQL, on every plan that sells paging.

Where it stands today

The cycle is met, the rota is not. On a real Postgres carrying the production schema, the loop’s own statement paged tier 1 (its person only), tier 2 (its person only), started over at tier 1 after Repeat after, and ran two more full cycles the same way; an acknowledged or resolved alert completed the escalation on the next pass with nobody paged; a policy without Repeat after completed after its last tier; another organisation’s escalation was untouched (deploy/workers-ts/test/escalationCycle-realdb.mjs, 5/5, 2026-11-07). Every one of those passes is recorded and re-run by the test suite on a machine with no database, which refuses a recording older than the escalation SQL (deploy/workers-ts/test/escalationCycle.spec.ts, 7/7). Not yet: an on-call rota, and the Android push page.

Not built or not measured yet

There is no on-call schedule or shift rotation: the list is the same every night, and you change it by editing the policy.

The Android app gets no push page yet: on Android a tier arrives by email and by the app’s optional background check.

What admins report from other tools

MSP owners describe rotas run by hand, a call-forwarding rule or one manager, that fail the week that person is away, and ask for a list that repeats until someone acknowledges.

Questions

Does it stop paging once someone acknowledges?
Yes. An acknowledged or resolved alert ends its escalation; nothing more is sent for it.
Can tier 2 be a different person?
Yes. Each tier names its own people and channels.
Is there a weekly on-call schedule?
No. The list is fixed until you edit it.

Related

See it before you sign up

Open a real SoloNOC dashboard on a sample network — sites, devices, alerts, topology and incidents — without creating anything.

Or start the free plan

No sign-up, no card. A real SoloNOC account with a sample network, read-only — nothing you press changes anything.

More from SoloNOC

SoloNOC is network monitoring for the one-person IT shop and the small MSP: one agent per site, flat plans, a 14-day trial with no card. Start free.