Difference between revisions of "UseCases/Current/GenesysEngage-onpremises/BO06"

From Genesys Documentation
Jump to: navigation, search
m (Text replacement - "\|SMART_HybridAssumptions={{SMART HybridAssumptions \|Hybrid_Assumption=(.*) }}" to "|DocVersion=$1")
Line 1: Line 1:
 
{{SMART UseCase
 
{{SMART UseCase
 +
|ID=
 +
|Title=
 +
|Offering=
 
|SMART_Benefits={{SMART Benefits
 
|SMART_Benefits={{SMART Benefits
−
|UCBenefitID=Improved Customer Experience
+
|UCBenefitID=Improved Net Promoter Score
 
|UCBenefit=Target the best agents to resolve the customer call type by reducing misroutes or repeated transactions to improve customer satisfaction measures (such as Net Promoter Score and Customer Effort Score
 
|UCBenefit=Target the best agents to resolve the customer call type by reducing misroutes or repeated transactions to improve customer satisfaction measures (such as Net Promoter Score and Customer Effort Score
 
}}{{SMART Benefits
 
}}{{SMART Benefits
Line 17: Line 20:
  
 
Service KPIs gather any types of metrics measuring a Customer Experience or Efficiency outcome of an interaction, as opposed to Sales KPIs that measure the Sales Outcome of an interaction. Service KPIs can be of two types:
 
Service KPIs gather any types of metrics measuring a Customer Experience or Efficiency outcome of an interaction, as opposed to Sales KPIs that measure the Sales Outcome of an interaction. Service KPIs can be of two types:
−
* Customer Experience or Service outcome such as Net Promotor Score (NPS), Customer Satisfaction (CSAT),  First Contact Resolution (FCR), and Customer Effort Score (CES)
+
 
−
* Operational efficiency metrics such as Handle Time (AHT), transfers, hold count, hold time, case open/closed, back office tasks opened, and field technical sent
+
*Customer Experience or Service outcome such as Net Promotor Score (NPS), Customer Satisfaction (CSAT),  First Contact Resolution (FCR), and Customer Effort Score (CES)
 +
*Operational efficiency metrics such as Handle Time (AHT), transfers, hold count, hold time, case open/closed, back office tasks opened, and field technical sent
 +
 
 
This use case focuses on improving First Contact Resolution (FCR), captured from Genesys Info Mart or from 3rd-party surveys (for inbound voice interactions, for example) but may also be extended to other service-related KPIs, and other channel types with custom PS effort. Wherever applicable, this use case documents the impacts of choosing another channel type or another KPI, captured from Genesys data or from 3rd-party sources.<br />
 
This use case focuses on improving First Contact Resolution (FCR), captured from Genesys Info Mart or from 3rd-party surveys (for inbound voice interactions, for example) but may also be extended to other service-related KPIs, and other channel types with custom PS effort. Wherever applicable, this use case documents the impacts of choosing another channel type or another KPI, captured from Genesys data or from 3rd-party sources.<br />
 
Predictive Routing also applies to Sales & Marketing KPIs. See [https://repository.docs.genesys.com/Draft:UseCases/Current/PureEngage/SL06 Genesys Predictive Routing for Sales (SL06) for PureEngage]
 
Predictive Routing also applies to Sales & Marketing KPIs. See [https://repository.docs.genesys.com/Draft:UseCases/Current/PureEngage/SL06 Genesys Predictive Routing for Sales (SL06) for PureEngage]
Line 27: Line 32:
 
Predictive Routing has built-in A/B Testing to demonstrate the uplift of the KPI provided through use of machine learning. Predictive Routing leverages a variety of Genesys or third party data sources in order to build high quality predictors. In particular, Predictive Routing supports a native integration with Performance DNA in order to obtain a granular representation of the agent's profile.
 
Predictive Routing has built-in A/B Testing to demonstrate the uplift of the KPI provided through use of machine learning. Predictive Routing leverages a variety of Genesys or third party data sources in order to build high quality predictors. In particular, Predictive Routing supports a native integration with Performance DNA in order to obtain a granular representation of the agent's profile.
 
|UCSummary=The contact center manager wants to increase the percentage of the interactions achieving First Contact Resolution (FCR). The Predictive Routing solution can assist in achieving this objective. FCR can be obtained either from:
 
|UCSummary=The contact center manager wants to increase the percentage of the interactions achieving First Contact Resolution (FCR). The Predictive Routing solution can assist in achieving this objective. FCR can be obtained either from:
−
* Genesys Historical Reporting data, enabling you to define FCR. For example, FCR 7 is defined as the number of customers who didn't make a subsequent contact for the same service type in 7 days.
+
 
−
* A 3rd-party outcome data source (such as a survey).
+
*Genesys Historical Reporting data, enabling you to define FCR. For example, FCR 7 is defined as the number of customers who didn't make a subsequent contact for the same service type in 7 days.
−
* Optionally customers can also attach PDNA strand data to Agent profiles to improve their match with customers and intents based on their performance in trainings.
+
*A 3rd-party outcome data source (such as a survey).
 +
*Optionally customers can also attach PDNA strand data to Agent profiles to improve their match with customers and intents based on their performance in trainings.
  
 
Predictive Routing:
 
Predictive Routing:
−
* Uses machine learning, a subset of Artificial Intelligence, to compare feedback of the actual outcome with the predicted outcome, helping to improve future agent-to-customer matches.
+
 
−
* Ranks agents predicted to resolve the inquiry on first contact.
+
*Uses machine learning, a subset of Artificial Intelligence, to compare feedback of the actual outcome with the predicted outcome, helping to improve future agent-to-customer matches.
−
* Provides the finest-grain match of customer contact with agent to improve FCR.
+
*Ranks agents predicted to resolve the inquiry on first contact.
−
* Provides an FCR uplift using continuous learning to rank the expected FCR for agents servicing customers.
+
*Provides the finest-grain match of customer contact with agent to improve FCR.
−
* In many customer environments, anchoring the optimization on a customer experience metric like FCR, CSAT, or NPS also drives benefits in adjacent KPIs such as a reduction in handle time, transfers, or multi-agent events (MAE) with manageable impact to service levels.
+
*Provides an FCR uplift using continuous learning to rank the expected FCR for agents servicing customers.
 +
*In many customer environments, anchoring the optimization on a customer experience metric like FCR, CSAT, or NPS also drives benefits in adjacent KPIs such as a reduction in handle time, transfers, or multi-agent events (MAE) with manageable impact to service levels.
 +
 
 
The result is that repeat contacts are reduced and FCR improves.
 
The result is that repeat contacts are reduced and FCR improves.
 +
|Description=
 
|PainPoints=* Frustrated customers or repeat interactions – increased number of transfers to identify the right person to resolve the issue​
 
|PainPoints=* Frustrated customers or repeat interactions – increased number of transfers to identify the right person to resolve the issue​
 
* Resource inefficiency and high costs – unable to identify the right agent to quickly solve the issue​
 
* Resource inefficiency and high costs – unable to identify the right agent to quickly solve the issue​
Line 48: Line 57:
 
* Deep integration with Genesys routing and orchestration​​​
 
* Deep integration with Genesys routing and orchestration​​​
 
|BuyerPersonas=Head of Customer Experience, Head of Customer Service, Head of Contact Center(s)
 
|BuyerPersonas=Head of Customer Experience, Head of Customer Service, Head of Contact Center(s)
 +
|QualifyingQuestions=
 
|MaturityLevel=Differentiated
 
|MaturityLevel=Differentiated
 
|SellableItems=At least one Inbound SMART USE Case is required, CIM, CIM HA (Optional), Genesys Infomart, Genesys Infomart - HA (optional)
 
|SellableItems=At least one Inbound SMART USE Case is required, CIM, CIM HA (Optional), Genesys Infomart, Genesys Infomart - HA (optional)
 
|CloudAssumptions=This use case is currently not available in PureEngage Cloud
 
|CloudAssumptions=This use case is currently not available in PureEngage Cloud
 +
|CloudAssumptionsAdditional_Sales=
 +
|PremiseAssumptions=
 
|PremiseAssumptionsAdditional_Sales=* Available on premises (Conditional)
 
|PremiseAssumptionsAdditional_Sales=* Available on premises (Conditional)
 
Pre-requisite:
 
Pre-requisite:
Line 210: Line 222:
 
{{!}} class="confluenceTd" colspan="1"{{!}}New reports needs to be defined to view the PDNA sync information shared with GPR
 
{{!}} class="confluenceTd" colspan="1"{{!}}New reports needs to be defined to view the PDNA sync information shared with GPR
 
{{!}}}
 
{{!}}}
 +
|DistributionImageFlow=
 
|DistributionLogic=The details of the distribution of an interaction to an agent are defined in the underlying inbound use cases. Refer to the flow above to understand how Predictive Routing influences the distribution logic.
 
|DistributionLogic=The details of the distribution of an interaction to an agent are defined in the underlying inbound use cases. Refer to the flow above to understand how Predictive Routing influences the distribution logic.
  
Line 242: Line 255:
 
* Customer identification must be available and stored in Infomart.  
 
* Customer identification must be available and stored in Infomart.  
 
* Significant percentage of interactions require to have a customer id linked. If less than 10 percent interactions have a customer id then building models may not be feasible
 
* Significant percentage of interactions require to have a customer id linked. If less than 10 percent interactions have a customer id then building models may not be feasible
 +
|RequiresAll=
 
|RequiresOr=CE01, CE02
 
|RequiresOr=CE01, CE02
 
|Optional=EE14, CE16, CE18, CE19
 
|Optional=EE14, CE16, CE18, CE19
 
|Exceptions=EE04, CE38, CE12
 
|Exceptions=EE04, CE38, CE12
−
|PremiseAssumptionsAdditional=* FCR 7 is defined as the number of customers who didn't make a subsequent contact for the same service type within 7 days.
+
|SMART_PremiseAssumptions=
 +
|PremiseAssumptionsAdditional=* '''<span class="s1">Predictive Routing solution is offered to On-Premise customers from the Genesys Cloud in a Cloud-only supporting Hybrid Architecture.</span>'''
 +
* '''<span class="s1">Requires PM approval.</span>'''
 +
* <span class="s1"></span>
 +
* FCR 7 is defined as the number of customers who didn't make a subsequent contact for the same service type within 7 days.
 
* The Standard deployment materials address Inbound voice interactions only, Informart data only, including FCR 7.
 
* The Standard deployment materials address Inbound voice interactions only, Informart data only, including FCR 7.
 
* Omnichannel and outbound integrations require Genesys Product Management approval and Genesys Professional Services support.
 
* Omnichannel and outbound integrations require Genesys Product Management approval and Genesys Professional Services support.
Line 255: Line 273:
 
* There is no industry standard definition for FCR. The definition chosen in this use case is intended to be a guideline metric that can be repeated across our customers who have not defined this metric.
 
* There is no industry standard definition for FCR. The definition chosen in this use case is intended to be a guideline metric that can be repeated across our customers who have not defined this metric.
 
* PDNA integration must be evaluated and scoped by PS as part of the implementation effort as every customer may have different types of PDNA data available.
 
* PDNA integration must be evaluated and scoped by PS as part of the implementation effort as every customer may have different types of PDNA data available.
−
|SMART_CloudAssumptions={{SMART CloudAssumptions
+
|SMART_CloudAssumptions=
−
|Cloud_Assumption=This use case is currently not available in PureEngage Cloud
+
|CloudAssumptionsAdditional=
−
}}
+
|SMART_HybridAssumptions=
 +
|Requires=
 +
|Conditions=
 
|DocVersion=v 2.2.0
 
|DocVersion=v 2.2.0
 
}}
 
}}

Revision as of 11:10, April 16, 2020

This topic is part of the manual Genesys Engage On-Premises Use Cases for version Current of Genesys Use Cases.
Important
This use-case is in "Sales-Ready" status, meaning that all capabilities described in the use-case are supported by the Genesys products, but the associated services require a custom quotation. The Predictive Routing product is in Conditional Commercialization status, meaning that some capabilities are still restricted or may require PM approval.
Place CX and agent efficiency at the center of your routing decisions using AI to match each customer interaction with the best agent

What's the challenge?

Today’s contact centers generate large volumes of data and have outgrown legacy skill and queue-based routing for matching customers and agents. It is almost impossible to optimize for metrics such as First Call Resolution (FCR) or Average Handling Time (AHT) because thousands of if-then rules have to be built and managed.

What's the solution?

Genesys Predictive Routing works in real-time, using AI to analyze 100s of data points to discover patterns to match customers to the best agents. With Genesys Predictive Routing, contact centers can improve customer experiences, grow revenue, improve efficiency, and optimize for important KPIs.

Use Case Overview

Story and Business Context

Companies want to improve their business Key Performance Indicators (KPI), capitalize on innovation in Artificial Intelligence and drive business decisions with the abundance of data and context available. Predictive Routing uses machine learning to support optimization of Customer Service KPIs.

Customer Service KPIs are metrics measuring a customer experience or efficiency outcome of an interaction, as opposed to Sales KPIs that measure the sales outcome of an interaction. Service KPIs can be of two types:

  • Customer experience outcome such as Net Promotor Score (NPS), Customer Satisfaction (CSAT), First Contact Resolution (FCR), and Customer Effort Score (CES)
  • Operational efficiency metrics such as Handle Time (AHT), transfers, hold count, hold time, cases open/closed, and back-office tasks opened

This use case illustrates an improvement in First Contact Resolution (FCR), captured from Genesys Info Mart or from 3rd-party surveys (for inbound voice interactions, for example). The use case also illustrates service-related KPIs, where the data for the KPIs is available in Info Mart or another available data source.

Predictive Routing also applies to Sales & Marketing KPIs. See Genesys Predictive Routing for Sales (SL06) for Genesys Engage on-premises

Traditional routing matches customers to agents through skills-based or queue-based logic. The goal is to maintain a service level, rather than to improve a KPI. Predictive Routing differs from traditional routing in that it uses machine learning to detect patterns in historical data from Genesys Info Mart and other third-party data sources. The predictive algorithm then uses these sources to build a model that predicts the business outcome of a customer's interaction when handled by an employee.

The predictive model works to improve KPIs by ranking agents according to their predicted impact on the business outcome. It then assigns the interaction to the highest ranked available agent. A/B testing measures the real-world impact of Predictive Routing on the target KPI by comparing Predictive Routing performance against the existing routing strategy.



Use Case Benefits*

The following benefits are based on benchmark information captured from Genesys customers and may vary based on industry, lines of business or Genesys product line:

Use Case Benefits Explanation
Improved Customer Experience Reduce misroutes or repeated transactions to improve customer satisfaction by targeting the best agents to resolve different types of calls.
Improved First Contact Resolution Improve First Contact Resolution by routing the interaction to the most proficient Agent available to handle it.
Reduced Employee Attrition Improve Employee Experience by routing work to the Agent that they are more efficient or “good” at more often.
Reduced Handle Time Reduce transfers and conferences by routing interactions to the best qualified agent and reduce average handle time by having more efficient workers take each interaction.
*You can sort all use cases according to their stated benefits here: Sort by benefits

Summary

Organizations seeking to improve the level of customer service offered to their customers realize significant benefits from Predictive Routing. Machine learning models configured to optimize metrics such as First Call Resolution are at the core of the solution.

A customer calls the contact center, and Predictive Routing uses the data captured about the customer, their journey, and the current interaction to rank all available agents according to their predicted probability of resolving the call. Configuration options manage and balance the Service Level (speed to answer) with connecting to the most suitable agent. The result is a reduction in repeat contacts and improved FCR.

The outcome data feeds back into the machine learning model to inform future predictions. Impacts on KPIs and the performance of the machine learning models are available via real-time reports.



Use Case Definition

Business Flow

This business flow shows the use case from the perspective of the customer and agent.

Business Flow Description

  1. The customer contacts the company using the inbound voice channel. This inbound interaction can be the result of a proactive rule on a web or mobile application.
  2. One of the Inbound use cases for the corresponding media type handles the interaction and captures interaction context data. The exact data captured depends on the interaction and engagement type.
  3. Based on the interaction context, Genesys selects an initial group of agents with the required skill(s) as possible routing targets to handle the interaction.
  4. Predictive Routing calculates the scores of the agents in the target group using a machine learning model that takes into account the agents' historic performance on similar interactions.
  5. When there are multiple agents available, Genesys attempts to route the interaction to the available agent with a highest score.
  6. If there is an interaction surplus and an agent becomes ready, Genesys selects an interaction from the queue taking into account the priority of each waiting interaction, the score the agent has for each interaction, and the time the interactions were queued.
  7. If no agents are available within the configured timeout, the routing strategy expands the potential target pool of agents by reducing the skill requirements and then repeats the target agent selection using Predictive Routing.
  8. After dealing with the customer call, the agent disconnects the interaction.
  9. The outcome is mapped to Genesys Info Mart attribute (for example, a disposition code or custom key-value pair).
  10. Optional: The customer is offered a survey. The answer to the survey is stored in a third-party system.
  11. Optional: Outcome data, such as case management closure, is produced and stored by a third-party application.

Business and Distribution Logic

Business Logic

Routing Step 1

  • Using a supported channel and media type, the customer creates an interaction. As the interaction is handled and traced through your environment, data is captured that enables you to determine the outcome for the metric you want to optimize.
  • Prerequisite: This use case requires inbound call routing.

Routing Step 2

  • The interaction use case identifies the customer's primary intention (Service Type) and sets the initial target skill expression.

Routing Step 3

  • This step queues the interaction and is designed to cover both agent surplus and customer surplus scenarios. When either one or multiple agents are available (agent surplus scenario), the flow immediately proceeds. Otherwise, Genesys queues the interaction until an agent is available (customer surplus scenario).

Routing Step 4

  • The predictor information along with necessary call information (Customer Profile, Interaction, Agent Profile) passes to Predictive Routing as a scoring request once one or more agents are available. The relevant machine learning model processes the request, resulting in a score for each available agent for that interaction. This process handles both customer surplus and agent surplus scenarios.

Routing Step 5

  • The customer-to-agent matching provides the interaction score for each of the agents to the routing engine to identify the agents that can deliver the highest benefit to the target KPI. In an agent surplus scenario, the model compares the score of the highest ranked agent to the configured minimum score threshold. If the score is below the threshold, then the interaction is held until a higher-ranked agent becomes available or the threshold is reduced.
  • In a customer surplus scenario, where multiple interactions are waiting when an agent becomes available, the agent’s scores for each waiting interaction are compared with the minimum score threshold. If the agent score exceeds the threshold for at least one interaction, the system proceeds to route the highest scoring interaction. If not, then the agent remains unassigned until a lower-scored interaction becomes available or the threshold is reduced.

Routing Step 6

  • The minimum score threshold is reduced over time according to the preconfigured fallback strategy.
  • The checks in Routing Step 5 repeat regularly until an agent-interaction matchup meets the threshold requirements.
    • Normal target expansion, such as relaxing skill level as configured within the underlying distribution strategy, occurs.
    • The continual reprioritization of the interaction also occurs, as do any treatments and the standard queued customer experience.

Routing Step 7

  • The system delivers the interaction, handling any ring on no answer and exception situations as defined in the underlying use case.
  • The customer and the agent connect.

Routing Step 8

  • The interaction ends when the customer or agent disconnects the call.

Routing Step 9

  • The agent workspace or a server-side process captures the interaction outcome. Genesys APIs invoke, either automatically or after an agent action, to map the outcome to a Genesys interaction attribute, which can be custom attached data or a disposition code.
  • Genesys Info Mart captures this attribute in the Info Mart interaction record.

Routing Step 10

  • Optionally, the customer receives a survey.
  • If the customer completes the survey, the system collects and stores the outcome through a 3rd-party application.

Routing Step 11

  • Optionally, a third-party application produces and stores the outcome data.

Distribution Logic

The inbound use case provides details of the distribution of an interaction to an agent. Refer to the flow above to understand how Predictive Routing influences the distribution logic.

User Interface & Reporting


Agent UI

Target agents can review Attached Data/Case Data when an interaction routes to their Agent Workspace.

Reporting

Real-time Reporting

Predictive Routing does not include real-time reports. Operational reports are available in the Predictive Routing UI.

Operational reports include:

  • KPI Outcome
  • Feature Coverage
  • Model Accuracy

Historical Reporting

The historical reports available through GCXI are the following:

  • Predictive Routing Operational Report - tracks Predictive Routing operational statistics.
  • Predictive Routing A/B Testing Report - tracks A/B testing results for Predictive Routing models and predictors.
  • Predictive Routing Agent Occupancy Report - tracks Agent Occupancy while Predictive Routing is being used to optimize routing.
  • Predictive Routing Daily Queue Statistics Report - tracks KPIs for each Queue while Predictive Routing is being used to optimize routing.
  • Predictive Routing Detail Report - interaction-level detail data about Predictive Routing use and its impact on KPIs.

*A/B reports can be developed from any standard or custom Info Mart data. If the outcomes data is NOT integrated with Info Mart, the creation of A/B reports must be evaluated as a separate effort.

Customer-facing Considerations

Interdependencies

All required, alternate, and optional use cases are listed here, as well as any exceptions.

All of the following required: At least one of the following required: Optional Exceptions
None

Inbound

Digital

Workforce Engagement

Digital

Inbound

Outbound

Self-Service and Automation


General Assumptions

  • Requires Product Management approval.
  • Predictive Routing solution is offered to on-premises customers in a hybrid architecture that incorporates core functionality served from the components deployed in your own environment.
  • Predictive Routing is offered as a managed service by Genesys Professional Services, who deal with all aspects of machine-learning model creation and maintenance. A Professional Services package is mandatory for implementation and support of Predictive Routing.
  • The standard deployment materials address Inbound voice interactions based on Genesys Info Mart data only.
  • Integration of additional data sources, whether Genesys or 3rd-party, requires a dedicated assessment and implementation by Genesys Professional Services.
  • Customer must have implemented a use case for one or more channels and have deployed Genesys Info Mart reporting. These use cases populate the data used to build predictors and models, which direct how interactions are routed. Note that the capture and analysis of FCR KPIs is not part of Genesys Info Mart out-of-box statistics and is developed during model creation.

Note the exceptions where Predictive Routing cannot be integrated listed in the interdependencies section:

  • Self-Service use cases
  • Outbound preview and agent reservation used for Predictive and Progressive outbound

Customer Responsibilities

  • Customer has already optimized traditional routing strategies and processes and wants to achieve further improvements.
  • Customer has all compatible versions of URS, IRD, Genesys Info Mart, GCXI, and Pulse; or upgrades have been scoped in to the project plan.
  • Customer has the necessary systems and processes in place to track results and measure impact over the life of the model.
  • Customer identification is available and stored in Genesys Info Mart.



Document Version

  • Version v 2.2.1 last updated April 16, 2020

Retrieved from "https://all.docs.genesys.com/UseCases/Current/GenesysEngage-onpremises/BO06 (2025-06-18 20:59:27)"
Comments or questions about this documentation? Contact us for support!