This procedure requires administrative access to OpenMethods Experience Cloud and Genesys PureCloud.
...
First 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.
View file |
---|
name | OpenMethods ScreenPop.script |
---|
|
Step-by-Step
Image Removed Log in to Genesys PureCloud and select Collaborate / Communicate
Image Removed Navigate to the Admin screen by clicking Admin in the top bar (highlighted in red)
Image Removed Find the Contact Center section of the Admin screen and click Scripts (highlighted in red) to list current scripts
Image Removed Click the Create button to create a new script. This will script creation process
Image RemovedImage Removed Give this script a name to indicate it’s purpose, such as OpenMethods ScreenPop. Make sure the Blank Script template is selected and click the Create button to open the script editor
Image Removed Open the Actions tab of the tool box panel on the right side of the screen
Image Removed Click the “+” button to the right of Actions to add a new custom action to the script and bring up the Action editor screen
Image Removed Provide the action with a name, for example “Call Connect API” and click the Add Step button to add a step to the custom action
Image Removed Click the downward pointed arrow next to Scripter to expand the section
Image Removed Scroll down in the popup panel and click Open URL from the list to add the step to the action editor screen
Image Removed In the Open URL step section of the action editor screen, enable Open in New Window and change the default width and height of the window to something small. In the example we use 50x50. This window will automatically close as part of the screen pop process
Image Removed Image Removed Add the jwt parameter to the url with the API Key obtained during the first step as the value. Keep in mind your API Key will be very long
Image Removed Add the event parameter to the url with “On+Answer” as the value (Don’t forget to put the ‘&' in front of 'event’
Image Removed Add the agentId parameter to the url. The value will be added in the next steps
Image Removed Click on the Insert Variable button above the text area to bring up the variable selection popup panel. Make sure the text cursor is located after the '=' for the agentId parameter or the value will be put in the wrong place
Image RemovedImage Removed Scroll down to and select Scripter.Agent Email from the list to automatically add the value to the url field
Image Removed Add the ANI parameter to the url. The value will be added in the next steps
Image Removed Click on the Insert Variable button above the text area to bring up the variable selection popup panel. Make sure the text cursor is located after the '=' for the ANI parameter or the value will be put in the wrong place
Image RemovedImage Removed Scroll down to and select Scripter.Agent Email from the list to automatically add the value to the url field
Image Removed Click the Save button to save the custom action
Image Removed Click the Script menu button at the top of the script editor page to bring up the Script menu
Image Removed Select the Script Properties menu item to bring up the Script Properties panel on the right side of the script editor
Image Removed Click on Inbound to expand the options for Inbound calls
Image RemovedImage Removed Click the Disabled slider to enable this script for inbound calls
Image Removed Click the Script menu button again to bring up the script menu
Image Removed Click the Save menu option to save the script
Image Removed A notification will display in the upper right corner of the script editor to indicate the script was saved
Image Removed Click the Script menu button again to open the script menu and click Publish to publish the script to make it available for use in call flows
Image Removed As with Save, a notification will be displayed when the script has finished being published
Log out of the PureCloud application
Add Set Screenpop to Inbound Call Flow
Image Removed Log in to PureCloud as an administrator and click Architect to open the PureCloud Architect application
Image Removed Click on the inbound call flow that will trigger the OpenMethods screenpop to open the call flow editor
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.
Image Removed Locate the Task category in the Toolbox panel and click it to expand the category
Image Removed Click on Task and drag it into the menu that contains the transfer action
Image Removed Click on the vertical ellipse button to the right of the action to bring up the action menu
Image Removed Click Copy button to copy the existing transfer action to the clipboard
Image Removed Click on the newly add Task under the menu to show the task editor panel
Image Removed Click the Add action here button in the task editor to bring up the menu
Image Removed Click the Transfer to ACD menu option to add the action to the task. If the menu option isn’t available, perform steps 3 & 4 and try again
Image Removed Click on the Disconnect category in the toolbox panel to expand the category
Image Removed Click and drag the Disconnect action to the Add action here block below the Failure result for the Transfer to ACD action. You may want to add different behavior for failures but that is outside the scope of this document
Image Removed Click the vertical ellipse button to the right of the transfer action to bring up the menu
Image Removed Click the delete menu option to remove the original transfer action from the menu
Image Removed Click the new task to bring up the task editor
Image Removed Click the DTMF button to bring up the dtmf menu
Image Removed Click the number button corresponding to the original transfer action
Image Removed Click the task name at the top of the task editor to edit the task name
Image Removed Provide a name for the task and click the done button to save the name
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.
Image Removed Click on the task action that contains the transfer action to open the task editor
Image Removed Locate the Flow category in the toolbox panel and click it to expand the category
Image Removed Click and drag the Set Screen Pop action onto the Start block of the task action. You can also drag the action onto other blocks to insert it there as long as the Set Screen Pop is before the transfer action
Image Removed In the Set Screen Pop action details panel on the right side of the task editor, click the Screen Pop Script dropdown, locate the screen pop script you created earlier, and select it
Image Removed Click the Save button to save your changes
Image Removed ...
Child pages (Children Display) |
---|
depth | 3 |
---|
allChildren | true |
---|
style | h1 |
---|
sortAndReverse | |
---|
excerptType | rich content |
---|
first | 0 |
---|
|