Creating a Script to Display UUI
Last updated
Last updated
Now that we configured Parloa to send back UUI, we need to configure Genesys to display this information to the agent receiving the call. We do this with Scripts.
In the Genesys Cloud admin interface, go to Contact Center > Scripts.
Click "+ Create" to create a new script.
Enter a name for your script.
For simplicity, select the "Default Inbound Script" template. This template is a good starting point for displaying call data.
After creating the script, you'll see that it already contains some default information.
To extend this script to display additional data, click on Script > Script Properties.
Enable the option for UUI (User-to-User Information). This allows the script to access and display UUI data, which may include information not directly related to the call.
Modify an existing row in the script or add a new row to display UUI data and other relevant call data. Your script might look something like this:
Don't forget to click Save to save your script.
Create a new flow in Architect. You can name it based on its purpose, for example, "UUI Data and Call Routing."
In this workflow, you'll include the following blocks:
Data -> Set UUI Data: In this block, set the expression to assign UUI data to the call. Specifically, set Call.UUIData
to your outgoing UUI data.
Flow -> Set Screen Pop: Configure this block to trigger a screen pop-up. Select the script you created earlier that displays UUI and call data to agents.
Transfer -> Transfer to ACD: Use this block to route the call to one of the queues you've created.
Arrange the blocks in your workflow as needed. Your flow should resemble the diagram you provided. On a very basic flow, it looks like this:
After configuring the flow and transfer to ACD settings, click Save to save your Architect flow.
Validate the flow to check for any errors or inconsistencies.
Once validation is successful, click Publish to finish setting up your call flow.
Depending on your specific use case, UUI might not be enough and you might need to use our Call Data service, which involves making an HTTP request from Genesys Cloud. Follow these steps to configure Genesys Cloud to get the items from our database.
After you successfully configured your bot to store data in our Call Data API, we can set up Genesys to get this data.
Navigate to Integrations within Genesys Cloud and create a new integration if one does not already exist. For custom data actions, search for Web Services Data Action and follow the setup steps.
Go to Integrations -> Actions to add and configure your action. Here you will:
Contracts: Define your input and output schemas under this section.
Configuration: Input the endpoint and pass the arguments corresponding to your schemas.
And a typical output schema might look as follows:
Construct the associated request based on the input schema and endpoint configurations. This request will facilitate the data fetching process from the database.
Before routing the call to the agent, insert a Call Data Action node within your Architect flow. This node is responsible for triggering the data action.
Add Variables for Input and Output: Populate the Call Data Action node with variables that match those defined in your schema during the initial setup. This action will get the data from our API and return all the values, make sure to save them as Output variables.
In the Set Screen Pop block, make sure you pass these variables to the Script.
Create a new script by navigating to to Admin -> Contact Center -> Scripts and creating a script. In the upper-left corner, go to Script -> Script Properties and enable features like Data Actions and UUI.
Under the Variables section, add custom variables tailored to your use case. These should correspond with the variables you previously used in the Architect flow.
Ensure Input
is toggled for the variables
Upon successful implementation, each call forwarded by Parloa will populate the call agent's screen with the relevant data. This enhances the efficiency and quality of your customer service operations.