How to prioritize alerting people in the best time zone
Asked by John Baumbach:

We have some members in the team in UST and some members in PST. They are all in the same Team, which has a time zone of PST. The users' time zones are set properly.

An alert went off at 3 AM PST, but it went to all members simultaneously. We want it to go to people in UST first at that time, and then escalate to the PST team if it's not acknowledged after x minutes.

Conversely, if an alarm goes of at 4 PM PST, it should go to the PST team first, and not the UST team until x mins.

It's confusing from the documentation how best to set this up. Is it separate teams? With different escalation policies? But how to swap the team that is alerted first based on when the alert happens?


Answers:
author: Darryl Lee
body: Hi [@John Baumbach](/t5/user/viewprofilepage/user-id/4884492) ,

This is Darryl, I am here to help.

Understand that you would like to have your escalations based on the time an alert is created.

In your case, I would suggest separating those teammates who are based in UST and PST into two different timezones individually and incorporating the 2 different Routing Rules of the team to set up the time constraints and the 2 Escalation Policies to triage.

#### For Schedules {#toc-hId-143660151}

Please add two individual schedules with the timezone set up correctly and add the team members from these 2 different timezones into the right schedules.

For example:

![Screenshot 2022-04-20 at 15.31.40.png](https://community.atlassian.com/t5/image/serverpage/image-id/193736i07691CC6D5EA2918/image-size/large?v=v2&px=999 "Screenshot 2022-04-20 at 15.31.40.png")

#### For Escalation Policy {#toc-hId--1663794312}

Please add 2 different Escalation policies for handling 2 different escalation paths for your descripitons:
> An alert went off at 3 AM PST, but it went to all members simultaneously. We want it to go to people in UST first at that time, and then escalate to the PST team if it's not acknowledged after x minutes.
>
> Conversely, if an alarm goes of at 4 PM PST, it should go to the PST team first, and not the UST team until x mins.

For example:

![Screenshot 2022-04-20 at 15.33.04.png](https://community.atlassian.com/t5/image/serverpage/image-id/193737i76D51EF7E46B8D0E/image-size/large?v=v2&px=999 "Screenshot 2022-04-20 at 15.33.04.png")

#### For Routing Rule {#toc-hId-823718521}

This is where the time constraints are set.

Please add at least 1 Routing Rule to set up the time constraint for 3AM to 4PM PST and route the alerts to the Escalation policy you set up for handling the alerts created at 3AM PST.

For example:

![Screenshot 2022-04-20 at 15.36.17.png](https://community.atlassian.com/t5/image/serverpage/image-id/193738iD89FCD62C1E0D6C3/image-size/large?v=v2&px=999 "Screenshot 2022-04-20 at 15.36.17.png")

At the end of the setup, the screen should be looking like this:

Whenever an alert is created between 3AM-4PM PST and assigned to this team

-\> Opsgenie routes this alert to the 3AM PST escalation policy following the Routing Rule

-\> and this 3AM PST escalation policy will firstly route the alert to the on-call user at 3AM PST Schedule

-\> if not acknowledged within 10 mins, the alert will be escalated to the on-call user in 4PM PST Schedule.

![Screenshot 2022-04-20 at 15.37.11.png](https://community.atlassian.com/t5/image/serverpage/image-id/193739iD9B33A9EC9F405F1/image-size/large?v=v2&px=999 "Screenshot 2022-04-20 at 15.37.11.png")

*** ** * ** ***

The main concept here is to follow this sequence: Routing Rule with time constraints -\> Escalation Policy -\> On-call Schedule for triaging the alerts properly.

Please adjust the details that are close to your actual condition and expectation.

Here I attach some useful documents for your reference:

[Alert Notifications Flow](https://support.atlassian.com/opsgenie/docs/alert-notifications-flow/)

[Configure a team dashboard](https://support.atlassian.com/opsgenie/docs/configure-a-team-dashboard/)

Should you have any further inquiries or issues, please feel free to reach out to [Opsgenie Support Team](https://support.atlassian.com/opsgenie/) and my colleague will help you from there.

comments: author: John Baumbach
body: Hi, thanks for the walkthrough. I was able to get most of it done, but unfortunately hit a snag at the end.

For your last screenshot, I got the "If" part to work ok, but for the "Else" part, I'm unable to select the other escalation I created. It's not available in the drop-down list and there's no way to type it in.

What am I doing wrong?

-JB


author: Darryl Lee
body: Hi [@John Baumbach](/t5/user/viewprofilepage/user-id/4884492) ,

Awesome, you're almost there!

For the **ELSE** part of the Routing Rules, as long as you've created the Escalation policy ++within the same Team++, it should be listed in the dropdown list upon clicking the field.

It could be helpful for having your browser's cache/cookies cleared or try on another browser to see if it works.

If you are still not able to find the escalation policy that you've created for the same team, please reach out to [Opsgenie Support](https://support.atlassian.com/opsgenie/) for further assistance.

Thanks.

Kind regards,   
Darryl Lee  
Support Engineer, Atlassian


author: John Baumbach
body: Ah ha, I created separate UST and PST teams and added THOSE to the schedules. You mentioned:

"Please add two individual schedules with the timezone set up correctly and add the team members from these 2 different timezones into the right schedules."

I couldn't figure out how to do that since you can only add teams to a schedule, not individuals. Any advice about that part?

Also - you don't mention rotations but are those involved somehow?


author: Darryl Lee
body: Hi [@John Baumbach](/t5/user/viewprofilepage/user-id/4884492) ,

From your original description, I thought they are all on the same team.

To simplify the scenario, I would suggest putting them into the same team and using 2 different On-call schedules with different timezone setups to separate them.

*** ** * ** ***

Sorry that I didn't make it clear. By mentioning the configuration related to Schedules, I mean adding the users into Rotation., and you may add the Team as Responders in each of the Rotation.

For example:

![Screenshot 2022-04-22 at 17.42.37.png](https://community.atlassian.com/t5/image/serverpage/image-id/194183iAF75E94F696D0F49/image-size/large?v=v2&px=999 "Screenshot 2022-04-22 at 17.42.37.png")

*** ** * ** ***

In your case, my suggestion is to: {#toc-hId--557319731}
--------------------------------------------------------

1. Put all your users into the same team, which means, one team only.

2. Create 2 On-call Schedules with the correct timezone setup to separate those users.

3. Add 1 Rotation to each of the On-call Schedules, and add the users into the corresponding On-call Schedule's Rotation by timezone.

i.e. Add 1 Rotation into PST_Schedule and 1 Rotation into UST_Schedule, and add those users in the PST timezone into the Rotation of the PST_Schedule, and vice versa.

4. Add 2 different Escalation policies ++within the same team++ for handling the 2 different escalation paths mentioned in your description.

5. Add a Routing Rule to the same team that has the time constraint configured matching one of your expected escalation paths and set it to route alerts to the expected Escalation Policy, while leaving the **ELSE** condition pointing to the other Escalation policy.

*** ** * ** ***

If you are still not able to configure this solution successfully, please reach out to [Opsgenie Support](https://support.atlassian.com/opsgenie/) for further assistance.

Thanks.

Kind regards,   
Darryl Lee  
Support Engineer, Atlassian


author: John Baumbach
body: OK, I think it's working, thanks for your help!


Tags: schedule

timezone