Source
Documentation (escalation policies) — Xurrent IMR (Zenduty)
Checked for Xurrent IMR (Zenduty) on 7 Nov 2026
- Page
- https://www.xurrent.com/imr-help/escalation-policies
- Checked
- 7 Nov 2026, 03:34 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:f2795ebd6ad51565581eb72bfcd0bf75181d4ba7fa0d76c49a150d6c4970f255
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Escalation policy service mapping Report an error
“Each service in Xurrent IMR is mapped to an escalation policy. Escalation policies dictate how an incident created within a service escalates within your team.”
-
Escalation policy composition Report an error
“Escalation policies can comprise of both on-call schedules and individual users.”
-
Escalation timeout acknowledgement Report an error
“If the on-call for S1 does not respond to the incident(by acknowledging the incident) within 5 minutes, the escalation policy can escalate it to the backup schedule S2. If the person(s) in S2 don’t acknowledge the incident within 10 minutes, then you can escalate it to the engineering manager, and so on.”
-
Unassigned incident integration disable Report an error
“However, after a certain number of non-assignee incidents for the same integration, Xurrent IMR will disable the integration, post which you will have to manually enable it.”
-
Escalation rule notify targets Report an error
“You can pick who to notify when an incident is created. It can be specific people, or the person on call from your team's schedule or a combination of them.”
-
Escalation delayed notify Report an error
“You can pick when someone else should be notified. For eg: the Team Lead can automatically be notified 15 minutes later.”
-
Escalation repeat cycle Report an error
“To put your escalation chain in a loop, change the Repeat Escalation Cycle value and add the number of time you'd like to run the escalation chain in a loop.”
-
Escalation move next rule option Report an error
“By default, Xurrent IMR moves to the next escalation rule if the current rule(which only has a single on-call schedule) has no user on-call. To stop Xurrent IMR from automatically moving to the next rule, unselect/deactivate the Move to next rule if no user found in current rule slider option.”
-
Notification rules per user Report an error
“How each person is notified depends on the notification rules they or their team managers/admins have set up.”
-
Escalation policy crud Report an error
“To create a new escalation policy, simply click the Create Escalation Policy button as shown above.”
-
Cross team escalation member requirement Report an error
“If a user that falls within escalation policy E is not a member of Team B, then the member will receive the incident alerts on SMS, Phone, Email, Slack, Teams, Android/iOS push but will not be able to read the incident or update the incident.”
-
Empty escalation assignee Report an error
“If no one is in the escalation cycle, Xurrent IMR will create the incident, but the Assignee will be blank.”
-
Oncall scheduling 24x7 Report an error
“On-Call Scheduling provides the ability to set up on-call schedules, rotations, and escalation policies allowing 24x7 support coverage to be provided based on business needs.”
Scores citing this record
- The Engineering Manager On-call schedules, rotations & escalation
- The Engineering Manager Alert delivery, routing & noise reduction
- The ICT Risk Officer On-call schedules, rotations & escalation
- The ICT Risk Officer Alert delivery, routing & noise reduction
- The IT Operations Manager On-call schedules, rotations & escalation
- The IT Operations Manager Alert delivery, routing & noise reduction
- The MSP NOC Lead On-call schedules, rotations & escalation
- The MSP NOC Lead Alert delivery, routing & noise reduction
- The Skeptic On-call schedules, rotations & escalation
- The Skeptic Alert delivery, routing & noise reduction
- The SRE Lead On-call schedules, rotations & escalation
- The SRE Lead Alert delivery, routing & noise reduction