A place to ask questions, connect with others, and stay in the know
1. You could tie permissions to be able to add/see the button to the workgroup queue itself, so that only members of the queue can see or add the button. When you press a client button, it sends a few standard attributes through with it (who pressed it, the button name, etc) which are all visible when you initiate a handler via client button.Again, if you're using the "classic" web chat and not Widgets chat, you'd have a closed schedule setup on your workgroup that is deactivated with a timeframe of essentially "Forever". Clicking this button would toggle the activated/deactivated state via directory services entries you'd need to edit. Editing directory services via handlers is advanced and you should have sufficient experience/training with handlers before attempting this and also use a development environment to test first. If you do not know what you are doing, this edits the registry/configuration of your server directly and can cause significant harm.That said, here are a few things I like to do for these types of buttons:
Every year, Genesys® orchestrates more than 70 billion remarkable customer experiences for organizations in more than 100 countries. Through the power of our cloud, digital and AI technologies, organizations can realize Experience as a Service℠, our vision for empathetic customer experiences at scale. With Genesys, organizations have the power to deliver proactive, predictive, and hyper personalized experiences to deepen their customer connection across every marketing, sales, and service moment on any channel, while also improving employee productivity and engagement. By transforming back-office technology to a modern revenue velocity engine Genesys enables true intimacy at scale to foster customer trust and loyalty.