Categories: Uncategorized

OnPage: Escalation Policy and Failover

OnPage has a zero tolerance policy when it comes to undelivered messages and alerts, which is why we added Failover Redundancy to our critical alerting platform. Failover Redundancy is, simply put, a part of our Escalation Policy.

What is the OnPage Escalation Policy?

An Escalation Policy makes sure that if an incident is not acknowledged or resolved within a pre-determined amount of time, it will be escalated to the correct user(s). You can customize who you want to receive the alert, the amount of time to wait before escalating to the next user(s), and which user(s) the alert should be escalated to.

fig1: Escalation Policy

When is an escalation policy useful? Imagine that you have an on-call team, monitoring critical systems. In the event of an incident, an alert is sent out either by a fellow team member or one of the monitoring tools connected to the hundreds of end points being monitored. If this alert is not acknowledged, what happens to it?

This is a general scenario in which OnPage is used, especially by our MSP customers. Our Scheduler allows you to schedule on-call teams and allows for precautionary steps to be taken that automate the alert going forth to an escalation team.

Below you will see how one can set an Escalation Interval and Escalation Factor which determines who gets the alert next.

fig2: setting up an Escalation Group

What is a Failover?

In the event a message is sent to an escalation group and does not reach anyone in the escalation group, OnPage offers two new configuration options:

  • Failover To OnPage ID’s: Inform OnPage users (refer to fig1: “Failover OPID(s):”) of the failed message escalation. Failover recipients are sent a modified copy of the original message which includes “FO:” in the subject and the name of the group the message was sent to.
  • Escalation Failover Report: Specify an email address (refer to fig1: “Fail report to email:”) which will receive a report including the message tracking information for the failed escalation. Including the original message subject and body in the report is optional.

fig3: Example of Failover Report

The failover makes sure that the right person is notified when the Escalation Policy does not reach an end user.

Contact OnPage to learn more .

OnPage Corporation

Share
Published by
OnPage Corporation

Recent Posts

PagerDuty vs Opsgenie vs OnPage (2025): Which On-Call & Alerting Tool Is Right for Your Team?

Disclosure: This comparison is based on my experience working closely with on-call workflows, incident alerting…

2 weeks ago

Top Incident Alerting and On-Call Management Software (2026 Buyer’s Guide)

Disclosure: This comparison is written by our product marketing team that works closely with IT…

2 weeks ago

AI Reliability, Part 2: When the Datacenter Becomes the Bottleneck

In Part 1, we talked about all the hidden complexity inside AI systems: the pipelines,…

3 weeks ago

OnPage Introduces Multi-Language Mobile App Localization on iOS & Android

As organizations continue to adopt OnPage across regions and operational environments, providing an experience that…

1 month ago

AI Infrastructure Is Creating a New Wave of Incidents, And Why Enterprises Need a Modern On-Call Strategy

Over the past couple of months, my entire world has felt flooded with AI breakthroughs.…

1 month ago

Manual Call Forwarding vs. Schedule-Based Call Routing: What’s the Better Way to Handle On-Call Support?

When your team shares one support number, someone has to decide who gets the calls…

2 months ago