An email alert can carry an acknowledge button. One click says someone has it, and the escalation stops. If nobody clicks, the flow keeps going and finds the next person.
Enable it on an email notify step and the alert arrives with a button the recipient can click straight from their inbox or phone.
Once claimed, the policy stops chasing. Repeat alerts and further escalation steps behind an acknowledgement branch no longer fire.
An if / else branch can test whether the incident has gone unacknowledged for N minutes and take a different path if it has.
Combine that branch with a repeat alert step and the page fires on an interval until it is claimed or the service recovers.
Most missed incidents are not missed because nobody was alerted. They are missed because everyone assumed somebody else had it.
A channel with five people in it can be read by all five and acted on by none. An acknowledgement makes ownership explicit.
If the first engineer does not respond, the policy moves to the next one automatically rather than waiting for someone to notice in the morning.
Once one person has claimed it, the rest of the team stops being paged about something already in hand.
The incident history shows how long it took for someone to pick the alert up, which is usually more useful than the outage duration itself.
Add an acknowledge link to your email step and let unclaimed alerts escalate on their own.