Each service in a Zenduty team is governed by an Escalation Policy. This Escalation policy combines various schedules and tasks to be performed for the users in the team as a set of rules. When an incident is triggered in the service, alerts are triggered according to the Escalation Policy specified.
To view Escalation Policies of a Team, open the ‘Teams’ section from the side bar and click on the team you want to expand. On the secondary header, select the tab ‘Escalation Policies’.
A list of all the Escalation Policies in a team will be visible to you.
To create a new escalation policy, simply click the ‘Create Escalation Policy’ button as shown above.
Give the escalation policy a name and summary.
- To create Escalation Rules, keep the following in mind:
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.
You can pick when someone else should be notified. For eg: the Team Lead can automatically be notified 15 minutes later. This is shown below:
- How each person is notified depends on the notification rules they or their team managers/admins have set up.
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.
- By default, Zenduty 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 Zenduty from automatically moving to the next rule, unselect/deactivate the Move to next rule if no user found in current rule slider option.
Click on the Escalation policy you’d like to make changes to, edit the configurations as desired and click on Save.
To delete an Escalation Policy, click on the ‘Delete’ button next to the corresponding policy, and confirm.
Global escalation policies allow you to create Escalation policies in one team and map them to services and incidents in other teams.
To make your escalation policy global, navigate to your escalation policy, and toggle the ‘Global Escalation Policy’ switch to the the ON state and Save/Update the escalation policy.
Important - When a service or incident in a team, lets say, Team B, is mapped to an escalation policy(E) in another team, say Team A, the team admins or owners must ensure that all the users that fall within escalation policy E are members of Team B. 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.