Search the table of all articles in this guide, listed in alphabetical order, to find the article you need.
|Appendix: Supported Encodings
|This topic provides recommendations for keeping your MongoDB database up-to-date and working correctly. It includes sections covering the following:
|Deploy the URS Strategy Subroutines
|Genesys Predictive Routing (GPR) provides subroutines components that are integrated with your Genesys Routing solution. The subroutines are placed within an existing strategy, where they add agent scoring and best-match functionality that enables you to fine-tune the routing of a specific interaction to the agent who can best handle it, based on the KPIs you want to optimize.
This topic explains how to use the pre-configured strategy subroutines with Interaction Routing Designer (IRD) and Universal Routing Server (URS). This topic includes the following information:
For information on how to deploy the Composer Subroutines, see Composer, Orchestration Server (ORS), and URS.
|GPR Glossary Terms (Internal Use-Not for Publication)
|Handling Personally Identifiable Information in Compliance with General Data Protection Regulation (EU)
|Genesys Predictive Routing (GPR) provides you with ability to do the following actions, in compliance with GDPR requirements:
ImportantGDPR compliance is fully managed by the client. GPR provides the necessary endpoints, but compliance requires you to perform the steps required to locate and remove PII.
|How Does GPR Score Agents?
|Install and Configure Predictive Routing
|Integrate with Genesys Routing
|Genesys Predictive Routing (GPR) provides two packages of subroutines that integrate into your Genesys routing environment. They perform the agent scoring and best-match selection functions, enabling you to fine-tune your routing to take advantage of the rich data on agents, customers, and interactions available to you in your environment.
The Composer Subroutines extend the functionality of the URS Strategy Subroutines so that you can use Composer and ORS to manage your routing. However, they are a wrapper around the URS Strategy Subroutines, not an entirely separate set of subroutines. As a result, they require that you also install URS and IRD.
|Operations: Updating, Maintenance, Logging, Troubleshooting
|R—AI Core Services Monitoring and Logging
NOTE: (from Peter Comb) If we can get the top 2-5 messages for:
Also from Peter: "Can we get a table in the docs that details for each functionality where it will appear in the logs - we now have at least 6 log files, and I am unclear when working with Datasets, Predictors, Models, reports, and so on where I should look for activity about that functionality."
|R--Agent State Connector Monitoring and Logging
|The following sections offer ASC-specific operations and user information.
You might also find the ASC-specific section of the following page helpful:
|R--Deploy Agent State Connector
|Agent State Connector (ASC) connects to Configuration Server and (in release 9.0.015.04 and higher, optionally) to Stat Server. It retrieves changes to Person and Agent Group configuration objects and updates to agent login data. It sends that information to the AI Core Services (AICS), which uses it to update agent profiles, agent availability, and (optionally) agent statistics.
Deploying ASC has three main phases:
A substantial rearchitecture of ASC in release 9.0.016.xx is reflected in this topic in the following ways:
If no release number is specified, the information applies to all releases.
ImportantIn a multi-tenant environment, configure one ASC instance for each Tenant.
|R--Deploy AI Core Services on a Single Host
|AI Core Services (AICS) is deployed using Docker containers on hosts running Docker Service. It is required that you deploy Docker Service in your environment, and Genesys provides the AICS installation file, which includes the multiple Docker images packaged as .tgz files. These images are loaded to the Docker Engine during the installation phase and are started in the desired pattern to ensure services are configured properly.
WarningThe instructions on the majority of this topic are intended only for new deployments. In particular, do not run the start.sh -l script if you have an existing version of Predictive Routing running in your environment. It will clear all existing data from your database and would result in data loss. To upgrade an existing deployment of Predictive Routing, following the instructions in Install into an Existing AICS Deployment.
|R--Deploy in High Availability Environments
|All Genesys Predictive Routing components support high availability (HA). However, HA is configured differently for each component:
|R--Deploying the Composer Subroutines
|Genesys Predictive Routing (GPR) provide subroutines components that are integrated with your Genesys Routing solution. The subroutines are placed within an existing Composer workflow, where they add agent scoring and best-match functionality that enables you to fine-tune the routing of a specific interaction to the agent who can best handle it, based on the KPIs you want to optimize.
Genesys Predictive Routing provides pre-configured subroutines for use with either:
These strategy subroutines are static strategies, that is, they run automatically once they have been set up. They respond to configured conditions without needing ongoing adjustments.
|To use Genesys Predictive Routing (GPR), you'll need to install and configure the following products and components:
|R--System Requirements and Interoperability
|Genesys Predictive Routing (GPR) includes several components. This topic provides an overview of the prerequisite hardware and software required to run each component.
It also includes an Interoperability table, showing which versions of the Genesys components required to run an end-to-end GPR solution are compatible.
ImportantIn addition to the prerequisites noted here, see the Genesys Supported Operating Environment Reference Guide, which provides operating system, database, and browser requirements information for most Genesys products.
|Routing Scenarios Using GPR
|R—Introduction to Key Third-Party Software
|This topic provides a brief introduction to the third-party products deployed with AICS. It explains their functionality, highlights the ways they are used in GPR, and links to relevant pages within the third-party user documentation.
|R—Start and Stop All GPR Components
|Use the Excel worksheet linked below to calculate hardware sizing guidelines for all GPR components in your environment. This sizing guide provides guidelines for simple single-server deployments, single-server HA deployments, and multi-server HA deployments.
|Strategy Subroutines Monitoring and Logging
|System Requirements, Pre-Requisites, and Planning