All Genesys software is © Copyright 2016–2018 Genesys Telecommunications Laboratories, Inc. All rights reserved.
Complete information about Genesys proprietary intellectual property, including copyrights, can be found here.
Genesys and the Genesys logo are registered trademarks of Genesys Telecommunications Laboratories, Inc. in the U.S.A. and other countries. Complete information about Genesys proprietary intellectual property, including all trademarks, can be found here.
All other trademarks are the property of their respective owners.
Third Party Software
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. Please contact your customer care representative if you have any questions. The following list describes specific third-party code and functionality for this product:
- This product utilizes MongoDB 3.0.5. The corresponding source code is available here: https://www.mongodb.org/.
- NOTICE OF RESTRICTED RIGHTS FOR ORACLE PRODUCTS LICENSED TO THE US GOVERNMENT Oracle Programs delivered to the United States government subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable license agreement therefor. Otherwise, Oracle programs delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
Genesys Customer Care links:
Information on supported hardware and third-party software is here:
New in Release 9.0.007.01 (01/05/2018)
- The user interface and the documentation have been updated to reflect the product name change from Genesys Predictive Matching to Genesys Predictive Routing.
New in Release 9.0.007.00 (12/22/2017)
- The product name has changed from Genesys Predictive Matching to Genesys Predictive Routing. This change is not yet reflected in the application interface or in the documentation.
- Genesys Predictive Routing now supports both single-site and multi-site HA architectures.
- Genesys Predictive Routing now supports historical reporting, provided by the Genesys Reporting solution. The following reports are available in Genesys Interactive Insights/GCXI: Predictive Routing AB Testing Report, Predictive Routing Agent Occupancy Report, Predictive Routing Detail Report, Predictive Routing Operational Report, and Predictive Routing Queue Statistics Report.
- Two new real-time reporting templates are available for use in Pulse dashboards: Agent Group KPIs by Predictive Model and Queue KPIs by Predictive Model.
- Two new analysis reports have been added to the Genesys Predictive Routing application: Agent Variance and Lift Estimation.
- The Model creation interface now includes additional model quality and agent coverage reporting.
- The Feature Analysis report, the model creation and training functionality, and the dataset import functionality have been improved to handle large datasets.
- You can now combine simple predictors to create composite predictors.
- Health checks and monitoring have been improved for both Journey Optimization Platform (JOP) and Agent State Connector (ASC). ASC now enables you to set alarms if there are persistent connection issues with Configuration Server or Stat Server.
New in Release 9.0.006.00 (09/26/2017)
- You can now deploy the Journey Optimization Platform (JOP) in Docker containers.
- This release includes updates to the Predictive Matching web interface for improved usability and rebranding.
- This release includes context-sensitive Help.
- You can now update and retrain models that have not yet been activated. You can also make changes to activated models by cloning them, editing the parameters, then activating the new model in place of the old one.
- Agent State Connector and the Strategy Subroutines components can be deployed in a high availability configuration.
- Predictive Matching now supports HTTPS.
- Predictive Matching now supports TLS 1.2 encryption. Support for TLS 1.1 has been discontinued.
- Routing using Predictive Matching can now take agent occupancy into account when selecting the best target.
- The workflow for creating Predictors has been made more logical and straightforward.
- Users can now reset their passwords from the Predictive Matching web interface.
New in Release 9.0.005.00 (06/27/2017)
- Predictive Matching now provides REST APIs for scoring, agent profile updates, and customer profile updates.
- Predictive Matching now supports strategies created in Composer and processed by Orchestration Server (ORS). These strategies utilize common Universal Routing Server (URS) subroutines to store scores returned from the scoring server and to set callback functions in URS.
- Schema modification has been extended to enable manual creation of fields not included in an imported dataset. This extended functionality also enables discovery of additional fields by uploading further data and thereby extending the schema.
New in Release 9.0.004.04 (03/28/2017)
- Extended datasets functionality now includes built-in analysis capabilities to make data exploration and feature analysis more straightforward without requiring customers to first build a predictive model.
- Customer profile data can now be loaded to the platform by means of a REST-API and joined at run time for scoring. This simplifies the integration requirements for deploying Predictive Matching, requiring less modification to existing routing strategies or run time CRM integrations.
- Predictive Matching now enables logging of routing decisions, required for accurate A/B testing, to JOP rather than Genesys Info Mart. This simplifies Predictive Matching deployment, by removing the need to make changes to Interaction Concentrator and Genesys Info Mart to support Predictive Matching.
- The new Predictive Matching Help now opens when you click the Help link in the Predictive Matching interface.
New in Release 9.0.003.00
- Improvements to the analytics and reporting functionality:
- Reports can now indicate whether a predictive score was generated (that is, A/B testing), and whether it was interleaved, or time-divided.
- The range of visualization on the Reporting Dashboard page has been improved.
- Predictive Routing can now perform analysis and data discovery on factors driving the KPI that is being optimized.
- You can now upload data sets in CVS format, enabling you to have Predictive Routing analyze the data, define predictors based on it, and report on it. You can use these data sets for model training and testing, and you can calculate statistics for correlation and cardinality from them.
- Self-service predictor management and model creation. Note the following properties of predictors and models:
- You can have multiple models built from one related data set.
- You can only use a predictor to optimize a single metric (that is, a column in the data set); each model under the same predictor optimizes the same metric.
- You can use a subset of features from the data set to define a predictor.
- A predictor can be based on a subset of data (such as a time range, or a subset created by filtering data set column values).
- Once you define a predictor, you can append new data to its underlying data set.
- A predictor can use any source of data matching the source data set schema to retrain and update models.
New in Release 9.0.000.00
- Routing subroutine support to score agents in agent-surplus mode, where there are more agents in ready status than interactions requiring agent handling. Agents can be scored on various criteria you configure so that interactions go to the most suitable agent.
- Routing subroutine support to score agents in customer-surplus mode, where more customer interactions are waiting in queue than there are available agents. Interactions are scored based on criteria you define so that customers you consider highest priority are handled first.
- Logging, monitoring, and alarm capabilities.
- Ability to combine various criteria for scoring agents or interactions for suitability, leading to a more nuanced matching of agents and interactions.
- Fault Tolerance. If Predictive Routing is unavailable, or if a Predictive Routing strategy subroutine takes more than a specified amount of time to process an interaction, the routing strategy defaults back to standard behavior.
Genesys Predictive Routing
Genesys Predictive Routing draws on accumulated agent and interaction data, enabling you to analyze omnichannel interactions and outcomes and generate models to predict outcomes. From this analysis, combined with machine learning, you can determine the best possible match between waiting interactions and available agents, and then route the interactions accordingly.
In addition, you can report on the predicted versus actual outcomes. The actual outcome is also used to further train the machine-learning model, improving the accuracy of predicted outcomes between similar customer profiles and agent profiles.
In addition, Predictive Routing includes an open REST-API for scoring and for providing feedback, enabling continuous or periodic automated improvement of models.
Genesys Predictive Routing is part of 9.0, which can include component releases from both 9.0.x and 8.5.x code streams. Use the table below to check which component releases are part of 9.0.
|9.0||9.0 Genesys Predictive Routing Release Notes|
|Predictive Matching - Agent State Connector|
|Predictive Matching - Composer Strategy Subroutines|
|Predictive Matching - URS Strategy Subroutines|
|Journey Optimization Platform|
Explains how to deploy Genesys Predictive Routing, enable its features, start, stop, and monitor its condition, and understand its functionality.
Explains how to use the Genesys Predictive Routing user interface.
The API Reference for Genesys Predictive Routing.
Records new features and functionality in all 9.0.0 releases, with links to the relevant documentation.