ReplacesPagerDutyOpsgeniephone trees
Escalations & On-call
vs the IT-incident pager
Severity-routed escalation built for facilities work, not IT incidents. A breached SLA promotes through a per-tenant step ladder to a DST-safe on-call rotation over multiple channels, acknowledgeable from the notification itself — with a non-negotiable statutory-floor clamp on every step timeout.
Why it wins
- A work-order SLA breach drives the escalation — FM-native, not a generic alert
- DST-safe daily/weekly/RRULE on-call rotations with overrides
- Multi-channel delivery, acknowledge from the notification (hashed single-use token)
- Statutory-floor clamp: a step timeout can never exceed the regulated response window
How it compares
Measured on publicly available data against the named market leader(s) it replaces. Every row links its source.
| IMAISA | The market leader | |
|---|---|---|
| Domain fit | A work-order SLA breach promotes through the escalation ladder | IT-incident escalation; not tied to an FM work-order SLA clocksource for the Domain fit comparison |
| Statutory floor | Every step timeout is clamped to the regulated response window | Configurable escalation timeouts; no statutory-floor clamp publishedsource for the Statutory floor comparison |
| Where it lives | On-call, routing and the work it escalates are one platform | A standalone incident tool, integrated to your job systemsource for the Where it lives comparison |
SLA-drivenFM-native escalation
DST-safeon-call rotations
Ackfrom the notification
Clampstatutory-floor timeout
Engineered across 6 architecture decision records (0127, 0134-0137, 0141) — a deliberately-built module, not a checkbox.