Hi Martin
Sorry to correct you, but it does work. I have used the Wait Until for this exact thing. Screen pop external link only when an Agent connects (not the alerting state which, by default any open URL in a custom script action will perform if present)
I am not sure of Muhammed's capabilities with Genesys so I described enough of the requirements, without actually doing a complete step by step guide.
Muhammed.
Set your screen pop URL in your inbound flow, looking at your example you know what the URL should be at this point. You do not need to pass the ID if that is part of the URL, use an expression in the flow to create the ready to go URL.
Make sure your Genesys Agent Script has a variable for the screen pop link and ensure it is marked as INPUT to the script.
In your flow, when you set the Screen pop object, you should see your input for your script variable, put your flow variable there as an expression.
Then in the Agent Script you need a Page load custom action with the WAIT UNTIL I first shared. That will ensure the screen pop will ONLY happen if the Agent answers the call.
Hope that helps
Regards
Simon
------------------------------
Simon Brown
Maintel Europe Limited
Senior Applications Consultant
------------------------------
Original Message:
Sent: 06-29-2026 08:24
From: Martin Boyle
Subject: Genesys Cloud – Is It Possible to Trigger the CRM Screen Pop Only After the Agent Answers the Call?
Hi Muhammed,
I've never implemented something like that myself. Out of the box there is no way to do this, you would need some serious development work to get that working.
My idea that could potentially work is that you have a script with two pages. This will pop up to the agents regardless of whether they are answering it or not (the behaviour you are trying to avoid). On the first page, there is a single button. This button will map to a data action that you have created, that maps to the
post /api/v2/conversations/calls/{conversationId}/participants/{participantId}/replace API. The idea of this button is that the agent will answer the Interaction with this button.
Then, on your Script, you have a Boolean variable set to False by default. You then have an action set up to set this to true when the button is answered. You then have another action on your script that looks for your True/False boolean variable to be set to true, and if it is, then change page to the Script page with the customer details etc.
Once the button is clicked, the Interaction is answered, then your boolean is set to true, and this true triggers a page change to open your customer details.
Best of luck with this build, it's a really interesting one to develop.
------------------------------
Martin Boyle
x
------------------------------