HI Lisa,

I don't actually know the reason, but my assumption is that allowing that field to be edited once you are using the tool will likely result in some disruption or inaccuracy in the existing forecasts and schedules.

As a reminder to those that may be following this thread, for Operations (and therefore schedules) that span timezones, users i,e, agents, WFM admins, Sups, etc. will see the information in their local timezone regardless of the BU setting.

HI Lisa,

I don't actually know the reason, but my assumption is that allowing that field to be edited once you are using the tool will likely result in some disruption or inaccuracy in the existing forecasts and schedules.

As a reminder to those that may be following this thread, for Operations (and therefore schedules) that span timezones, users i,e, agents, WFM admins, Sups, etc. will see the information in their local timezone regardless of the BU setting.

https://help.mypurecloud.com/articles/add-a-business-unit/ has the following two notes:

Note: After you create the business unit, you cannot change the start day of the week or the time zone. If you need to modify a business unit for these parameters, create a new business unit and configure it to match the previous one.

Note: The default time zone is the current location's time zone.

The reason we do not allow a change here is because of forecasts and schedules that were created based on a specific time zone and/or start date. Allowing a change to either could result in a wide range of ramifications. Just for time zone it could be, in the most extreme case, a change of 26-hours; for start day of week it could be 7 days.

I will put an enhancement request in our backlog to add some informational text on the BU create dialog noting that these two fields cannot be changed after creation to at least give the end-user a pause.

You can see another thread along with my two replies regarding work plan start times accounting for time zone differences between agent(s) and business unit here.

HI Lisa,

I don't actually know the reason, but my assumption is that allowing that field to be edited once you are using the tool will likely result in some disruption or inaccuracy in the existing forecasts and schedules.

As a reminder to those that may be following this thread, for Operations (and therefore schedules) that span timezones, users i,e, agents, WFM admins, Sups, etc. will see the information in their local timezone regardless of the BU setting.