I would suggest having a landing page on the script that the agent can click a big button that says CONTINUE and that would change the page and do the screen pop. Alternatively, just embed the URL in the script and don't worry about popping. If you really need a delay, then use a data action to a web service or the new Customer Code as a Data Action to delay processing before moving onto the screen pop. All depends on how important that screen pop is.
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.comhttps://www.ttecDigital.comhttps://RobertWC.Blogspot.com------------------------------
Original Message:
Sent: 12-03-2024 13:37
From: Simon Noel
Subject: Screen pop placement.
Hi Robert,
the problem here is that open url is actioned before agents have time to answer a call. Sometime the screen pop will hide the answer button, or if opened in a new tab will navigate the agent to the new tab. By delaying the Open URL when the interaction is connected, we can have the agent answer the call, and the screen pop come up to the screen afterward
------------------------------
Simon Noel
Senior Consultant, Integrations
------------------------------
Original Message:
Sent: 12-03-2024 12:45
From: Robert Wakefield-Carl
Subject: Screen pop placement.
You are talking about two different things here. The script in Genesys is always inside of the Genesys UI, but the Open URL has the ability to change size when opening in a new window, but not location. As for staying on top, I found a few references to ways to do that but may or may not work with your screen pop, but that is outside of Genesys and dependent on what you are popping. I saw a few add-ins for Edge and Chrome that also can look at a URL and make sure it stays on top.
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.com
https://www.ttecDigital.com
https://RobertWC.Blogspot.com