This procedure requires administrative access to OpenMethods Experience Cloud and Genesys PureCloud.
Obtain the OpenMethods Experience Cloud API Key by following the steps laid out in Obtaining OpenMethods Token
Create the screenpop script in Genesys PureCloud
Add Set Screenpop Action in inbound call flow
Creating the Screenpop Script
Screenpops in Genesys PureCloud are performed by scripts created in the Admin console and invoked by the call flows managed in Architect. In this section we will be creating a script capable of triggering an OpenMethods Popflow screenpop from scratch. You may also import the following example script and modify it for your environment.
Step-by-Step
Add Set Screenpop to Inbound Call Flow
There are two likely scenarios you’ll face adding the OpenMethods screenpop logic to an existing call flow: Top Level Transfer to ACD and Add to Existing Task. If the transfer action is already contained in a task, skip down to Add to Existing Task.
Top Level Transfer to ACD
You may find that the Transfer to ACD action is located directly under a menu option. In order to add the OpenMethods screenpop, we’ll first need to move this action into a new Task. When finished, we can continue with Add to Existing Task.
Add to Existing Task
If the transfer action is already contained within a task action, we can simply add our screenpop behavior to the task.
0 Comments