Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current Restore this Version View Page History

« Previous Version 10 Next »

This procedure requires administrative access to OpenMethods Experience Cloud and Genesys PureCloud.

  1. Obtain the OpenMethods Experience Cloud API Key by following the steps laid out in Obtaining OpenMethods Token

  2. Create the screenpop script in Genesys PureCloud

  3. 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

  1. Log in to Genesys PureCloud and select Collaborate / Communicate

  1. Navigate to the Admin screen by clicking Admin in the top bar (highlighted in red)

  1. Find the Contact Center section of the Admin screen and click Scripts (highlighted in red) to list current scripts

  1. Click the Create button to create a new script. This will script creation process

  1. 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

  1. Open the Actions tab of the tool box panel on the right side of the screen

  1. Click the “+” button to the right of Actions to add a new custom action to the script and bring up the Action editor screen

  1. 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

  1. Click the downward pointed arrow next to Scripter to expand the section

  1. Scroll down in the popup panel and click Open URL from the list to add the step to the action editor screen

  1. 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

  1. Add the base Connect API url into the URL text area (including the '?' at the end)

North America: https://connect.openmethodscloud.com/api/sendmessage/bc/CTI?
Europe/GDPR: https://connect.gdpr.openmethodscloud.com/api/sendmessage/bc/CTI?

  1. 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

  1. Add the event parameter to the url with “On+Answer” as the value (Don’t forget to put the ‘&' in front of 'event’

  1. Add the agentId parameter to the url. The value will be added in the next steps

  1. 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

  1. Scroll down to and select Scripter.Agent Email from the list to automatically add the value to the url field

  1. Add the ANI parameter to the url. The value will be added in the next steps

  1. 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

  1. Scroll down to and select Scripter.Agent Email from the list to automatically add the value to the url field

  1. Click the Save button to save the custom action

  1. Click the Script menu button at the top of the script editor page to bring up the Script menu

  1. Select the Script Properties menu item to bring up the Script Properties panel on the right side of the script editor

  1. Click on Inbound to expand the options for Inbound calls

  1. Click the Disabled slider to enable this script for inbound calls

  1. Click the Script menu button again to bring up the script menu

  1. Click the Save menu option to save the script

  1. A notification will display in the upper right corner of the script editor to indicate the script was saved

  1. 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

  1. As with Save, a notification will be displayed when the script has finished being published

  1. Log out of the PureCloud application

Add Set Screenpop to Inbound Call Flow

  1. Log in to PureCloud as an administrator and click Architect to open the PureCloud Architect application

  1. 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.

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.

  1. Locate the Task category in the Toolbox panel and click it to expand the category

  1. Click on Task and drag it into the menu that contains the transfer action

  1. Click on the vertical ellipse button to the right of the action to bring up the action menu

  1. Click Copy button to copy the existing transfer action to the clipboard

  1. Click on the newly add Task under the menu to show the task editor panel

  1. Click the Add action here button in the task editor to bring up the menu

  1. 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

  1. Click on the Disconnect category in the toolbox panel to expand the category

  1. 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

  1. Click the vertical ellipse button to the right of the transfer action to bring up the menu

  1. Click the delete menu option to remove the original transfer action from the menu

This document may contain confidential and/or privileged information belonging to OpenMethods. If you are not the intended recipient (or have received this document in error) please notify the sender immediately and destroy this document. Any unauthorized copying, disclosure, or distribution of the material in this document is strictly forbidden.