Hello everyone. Have your agents been experiencing intermittent issues when trying to export their schedules to a third party calendar? 

One of my colleagues was able to identify the root cause of these issues as the custom URL, which bridges the Genesys schedule to the third party calendar. The problem is that a new URL is created each time a new week of schedules are published, which means that the external calendar will not continue to update automatically. It's worth noting that the newer URL is still able to relay information for older schedules. This issue is not large enough to consider restructuring our entire schedule build/publish process around, but we also don't think it's feasible to expect agents to complete these steps on a weekly basis. 

Please consider voting for the enhancement idea that I have put forward in response to this issue: Enable Initial External Schedule Sync to Apply to Future Schedule Releases (Planning Periods) WESCH-I-334. Thank you!

The shareable link URL will not change week over week or from one schedule to the next. The only way the URL would change is if the agent disables the current link (which would cause any third-party calendars to cease to update that are using that disabled link) and then requests a new link.

We are aware of one escalation where the third-party calendar is not updating - those third-parties poll at inconsistent times of day and some state no more than once per 24h period.

This really is not something that would be addressed in an enhancement request. We are actively working the one support case to pinpoint the underlying issue.

I would suggest empowering your agents by having them use Tempo. That will be a better and more feature rich experience than relying on a third-party outside of everyone's control that does polling infrequently at inconsistent times.

Hello everyone. Have your agents been experiencing intermittent issues when trying to export their schedules to a third party calendar? 

One of my colleagues was able to identify the root cause of these issues as the custom URL, which bridges the Genesys schedule to the third party calendar. The problem is that a new URL is created each time a new week of schedules are published, which means that the external calendar will not continue to update automatically. It's worth noting that the newer URL is still able to relay information for older schedules. This issue is not large enough to consider restructuring our entire schedule build/publish process around, but we also don't think it's feasible to expect agents to complete these steps on a weekly basis. 

Please consider voting for the enhancement idea that I have put forward in response to this issue: Enable Initial External Schedule Sync to Apply to Future Schedule Releases (Planning Periods) WESCH-I-334. Thank you!