Hi,

I apologize in advance, but you will likely see a few messages like this from me in the next day or two. I want to keep each message thread separate!

Many of you may not realize that Genesys has an Ideas website (Aha!) which, whilst not perfect (see various posts from me and others on THAT subject!) is the main method we have for requesting features / enhancements. If you don't frequent the site, you may miss some of the cool ideas that get proposed.

In this post, I'd like to draw your attention to this idea. Many parts of call centers can be governed by the work day and having a central source of truth for all scheduling would be helpful. Architect can access Schedules / Schedule Groups, but adding an API endpoint that will return the "Open"/"Closed"/"Holiday"/"Emergency" information would allow the same Scheduling process to be used by external systems (like web pages etc.)

Thank you.

Believe me, you are not alone in this request.  There are so many ways this could be used, but mostly, I see it needed for website code to check schedules for turning on and off the messaging deployment.  I will push again on this with the PMs. 

Hi,

I apologize in advance, but you will likely see a few messages like this from me in the next day or two. I want to keep each message thread separate!

Many of you may not realize that Genesys has an Ideas website (Aha!) which, whilst not perfect (see various posts from me and others on THAT subject!) is the main method we have for requesting features / enhancements. If you don't frequent the site, you may miss some of the cool ideas that get proposed.

In this post, I'd like to draw your attention to this idea. Many parts of call centers can be governed by the work day and having a central source of truth for all scheduling would be helpful. Architect can access Schedules / Schedule Groups, but adding an API endpoint that will return the "Open"/"Closed"/"Holiday"/"Emergency" information would allow the same Scheduling process to be used by external systems (like web pages etc.)

Thank you.

Hi,

I apologize in advance, but you will likely see a few messages like this from me in the next day or two. I want to keep each message thread separate!

Many of you may not realize that Genesys has an Ideas website (Aha!) which, whilst not perfect (see various posts from me and others on THAT subject!) is the main method we have for requesting features / enhancements. If you don't frequent the site, you may miss some of the cool ideas that get proposed.

In this post, I'd like to draw your attention to this idea. Many parts of call centers can be governed by the work day and having a central source of truth for all scheduling would be helpful. Architect can access Schedules / Schedule Groups, but adding an API endpoint that will return the "Open"/"Closed"/"Holiday"/"Emergency" information would allow the same Scheduling process to be used by external systems (like web pages etc.)

Thank you.