Difference between revisions of "PEC-REP/Current/RPRT/HRCXIPredictiveABTstng"

From Genesys Documentation
Jump to: navigation, search
(Published)
m (Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2")
 
(3 intermediate revisions by 2 users not shown)
Line 5: Line 5:
 
|Context=Evaluate the impact of enabling various predictive models and predictors based on time-sliced A/B testing.
 
|Context=Evaluate the impact of enabling various predictive models and predictors based on time-sliced A/B testing.
 
|ComingSoon=No
 
|ComingSoon=No
−
|Platform=PureEngage
+
|Platform=GenesysEngage-cloud
 
|Role=Administrator, Supervisor
 
|Role=Administrator, Supervisor
 
|Application=Reporting, Reporting GCXI
 
|Application=Reporting, Reporting GCXI
 +
|Prereq=
 
|Section={{Section
 
|Section={{Section
 +
|sectionHeading=
 +
|anchor=
 
|alignment=Horizontal
 
|alignment=Horizontal
 
|Media=Image
 
|Media=Image
 
|image=GCXI_Predictive_ABTesting.png
 
|image=GCXI_Predictive_ABTesting.png
 
|structuredtext=Use the ('''Predictive Routing''' folder) '''Predictive Routing A/B Testing''' Report to compare results for predictive models and predictors based on time-sliced A/B testing. This report includes a First Contact Resolution Rate calculation, which allows you to quickly see how often customer concerns were resolved on the first attempt, and allows you to contrast interactions that were processed when Predictive Routing was switched ON compared to when it was OFF. The report also profiles response time, engage time, wrap time, and other relevant Key Performance Indicators (KPI).
 
|structuredtext=Use the ('''Predictive Routing''' folder) '''Predictive Routing A/B Testing''' Report to compare results for predictive models and predictors based on time-sliced A/B testing. This report includes a First Contact Resolution Rate calculation, which allows you to quickly see how often customer concerns were resolved on the first attempt, and allows you to contrast interactions that were processed when Predictive Routing was switched ON compared to when it was OFF. The report also profiles response time, engage time, wrap time, and other relevant Key Performance Indicators (KPI).
−
 
 
|structuredtextwide=To get a better idea of what this report looks like, view sample output from the report: {{Repository|SamplePredictiveRoutingABTestingReport.pdf||Sample_Predictive Routing_ABTesting_Report.pdf}}
 
|structuredtextwide=To get a better idea of what this report looks like, view sample output from the report: {{Repository|SamplePredictiveRoutingABTestingReport.pdf||Sample_Predictive Routing_ABTesting_Report.pdf}}
  
 
The following tables explain the prompts, attributes, and metrics used in this report:
 
The following tables explain the prompts, attributes, and metrics used in this report:
 +
|FAQHeading=
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 22: Line 25:
 
|anchor=Prompts
 
|anchor=Prompts
 
|alignment=Vertical
 
|alignment=Vertical
 +
|Media=
 +
|image=
 
|structuredtext={{{!}}  
 
|structuredtext={{{!}}  
 
!'''Prompt'''
 
!'''Prompt'''
Line 27: Line 32:
 
{{!}}-
 
{{!}}-
 
{{!}}Pre-set Date Filter
 
{{!}}Pre-set Date Filter
−
{{!}}Choose a date from the list of preset options.  This prompt overrides the Start Time and End Time values. Default: Year to Date
+
{{!}}Choose a date from the list of preset options.  This prompt overrides the Start Time and End Time values. Default: '''Year to Date'''
 
{{!}}-
 
{{!}}-
 
{{!}}Start Date
 
{{!}}Start Date
Line 48: Line 53:
 
{{!}}-
 
{{!}}-
 
{{!}}}
 
{{!}}}
 +
|structuredtextwide=
 +
|FAQHeading=
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 53: Line 60:
 
|anchor=Attributes
 
|anchor=Attributes
 
|alignment=Vertical
 
|alignment=Vertical
 +
|Media=
 +
|image=
 
|structuredtext={{{!}}  
 
|structuredtext={{{!}}  
 
!'''Attribute'''
 
!'''Attribute'''
Line 96: Line 105:
 
{{!}}-
 
{{!}}-
 
{{!}}}
 
{{!}}}
 +
|structuredtextwide=
 +
|FAQHeading=
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 101: Line 112:
 
|anchor=Metrics
 
|anchor=Metrics
 
|alignment=Vertical
 
|alignment=Vertical
 +
|Media=
 +
|image=
 
|structuredtext={{{!}}  
 
|structuredtext={{{!}}  
 
!'''Metric'''
 
!'''Metric'''
 
!'''Description'''
 
!'''Description'''
−
!'''Source or Calculation'''
 
 
{{!}}-
 
{{!}}-
 
{{!}}Offered
 
{{!}}Offered
Line 112: Line 124:
 
*could not be offered because no agent was in the Ready state,
 
*could not be offered because no agent was in the Ready state,
 
*were routed to an agent, accepted, and dropped within a one-second period.
 
*were routed to an agent, accepted, and dropped within a one-second period.
−
{{!}}Calculated as the total of calls with gpmResult=1 plus calls with gpmResult=14
 
 
{{!}}-
 
{{!}}-
 
{{!}}Accepted
 
{{!}}Accepted
 
{{!}}The total number that customer interactions and warm consultations that were accepted, answered, or pulled by an agent, voice-treatment port, IVR port, or nonagent-associated DN (such as contact center resources that can alert) within the reporting interval.
 
{{!}}The total number that customer interactions and warm consultations that were accepted, answered, or pulled by an agent, voice-treatment port, IVR port, or nonagent-associated DN (such as contact center resources that can alert) within the reporting interval.
−
{{!}}Calculated as the total of calls with gpmResult=1 plus calls with gpmResult=14
 
 
{{!}}-
 
{{!}}-
 
{{!}}Avg Handle Time (Fmt)
 
{{!}}Avg Handle Time (Fmt)
 
{{!}}The average amount of time (HH:MM:SS), within the reporting interval, that this agent spent handling interactions that the agent received. Computed as handle time divided by the sum of accepted interactions and received consultations.
 
{{!}}The average amount of time (HH:MM:SS), within the reporting interval, that this agent spent handling interactions that the agent received. Computed as handle time divided by the sum of accepted interactions and received consultations.
−
{{!}}
 
 
{{!}}-
 
{{!}}-
 
{{!}}First Contact Resolution Result
 
{{!}}First Contact Resolution Result
 
{{!}}First Contact Resolution (FCR) measures whether issues were resolved during the first customer attempt. A value of <tt>0</tt> indicates that the customer raised the same issue again within 7 days. FCR data is processed only after 7 days have elapsed, so any FCR data that appears in this report is at least 7 days old.
 
{{!}}First Contact Resolution (FCR) measures whether issues were resolved during the first customer attempt. A value of <tt>0</tt> indicates that the customer raised the same issue again within 7 days. FCR data is processed only after 7 days have elapsed, so any FCR data that appears in this report is at least 7 days old.
−
{{!}}The logic for calculating FCR is as follows:
 
−
 
−
*Interaction data is retrieved from the INTERACTION_FACT table for 7 days before and 7 days after the current date, based on the value in the START_DATE_TIME_KEY column.
 
−
*Interactions are grouped based on the value of CUSTOMER_ID and SERVICE_TYPE user data for each interaction.
 
−
*If the number of interactions within the reporting interval for a given CUSTOMER_ID and SERVICE_TYPE combination is more than <tt>1</tt>, then FCR=<tt>0</tt>.
 
−
*The FCR result for each interaction is stored in a separate table (FCR_ID).
 
 
{{!}}
 
{{!}}
 
{{!}}-
 
{{!}}-
Line 137: Line 140:
 
{{!}}Avg Wrap Time (Fmt)
 
{{!}}Avg Wrap Time (Fmt)
 
{{!}}The average amount of time (HH:MM:SS), within the reporting interval, that this agent spent on customer interactions while in ACW (Wrap) state.
 
{{!}}The average amount of time (HH:MM:SS), within the reporting interval, that this agent spent on customer interactions while in ACW (Wrap) state.
−
{{!}}
 
 
{{!}}-
 
{{!}}-
 
{{!}}Avg Engage Time (Fmt)
 
{{!}}Avg Engage Time (Fmt)
 
{{!}}The average amount of time (HH:MM:SS), within the reporting interval, that this agent was engaged with customers on interactions.
 
{{!}}The average amount of time (HH:MM:SS), within the reporting interval, that this agent was engaged with customers on interactions.
−
{{!}}
 
 
{{!}}-
 
{{!}}-
 
{{!}}Avg Hold Time (Fmt)
 
{{!}}Avg Hold Time (Fmt)
 
{{!}}The average number of seconds, within the reporting interval, that customers spent on hold for interactions. This metric is attributed to the interval in which the interactions were accepted by a resource.
 
{{!}}The average number of seconds, within the reporting interval, that customers spent on hold for interactions. This metric is attributed to the interval in which the interactions were accepted by a resource.
−
{{!}}
 
 
{{!}}-
 
{{!}}-
 
{{!}}Transfer Rate
 
{{!}}Transfer Rate
−
{{!}}The percentage of interactions that were transferred.
+
{{!}}The percentage of interactions that were transferred.
−
{{!}}Calculated as the total number of transferred interactions divided by the total number of interactions.
 
 
{{!}}-
 
{{!}}-
 
{{!}}}
 
{{!}}}
 +
To view more detailed information about the metrics and attributes in this report, and other metrics and attributes that can be used to customize reports, see the [https://docs.genesys.com/Documentation/GCXI/9.0.0/PG/Welcome ''Genesys CX Insights Projects Reference Guide''].
 +
|structuredtextwide=
 +
|FAQHeading=
 
|Status=No
 
|Status=No
 
}}
 
}}
 
}}
 
}}

Latest revision as of 02:33, July 25, 2020

This topic is part of the manual Work with Genesys CX Insights Reports for version Current of Reporting.

Evaluate the impact of enabling various predictive models and predictors based on time-sliced A/B testing.

Use the (Predictive Routing folder) Predictive Routing A/B Testing Report to compare results for predictive models and predictors based on time-sliced A/B testing. This report includes a First Contact Resolution Rate calculation, which allows you to quickly see how often customer concerns were resolved on the first attempt, and allows you to contrast interactions that were processed when Predictive Routing was switched ON compared to when it was OFF. The report also profiles response time, engage time, wrap time, and other relevant Key Performance Indicators (KPI).

To get a better idea of what this report looks like, view sample output from the report: Sample_Predictive Routing_ABTesting_Report.pdf

The following tables explain the prompts, attributes, and metrics used in this report:

Prompts in the Predictive Routing A/B Testing Report

Prompt Description
Pre-set Date Filter Choose a date from the list of preset options. This prompt overrides the Start Time and End Time values. Default: Year to Date
Start Date Choose the day and time from which to begin collecting data into the report. This prompt has no effect if Pre-set Date Filter is set to anything except None.
End Date Choose the day and time at which to stop collecting data into the report.
Media Type Select one or more media types for which to gather data into the report.
Predictor Select one or more predictors for which to gather data into the report.
Model Select one or more models for which to gather data into the report.
Tenant Select one or more tenants to include in the report.

Attributes in the Predictive Routing A/B Testing Report

Attribute Description
Tenant Enables the organization of data by tenant.
Media Type Enables the organization of data by media type.
Day Enables the organization of data by the day/date on which the interaction occurred.
Predictor Switch Enables the organization of data by whether predictive routing is ON or OFF.
Predictor Enables the organization of data by the identifier for the predictor that was used to request scoring for predictive routing.
Model Enables the organization of data by the identifier for the model that was used to calculate agent scores for predictive routing.
Result The result of Predictive Routing processing. If there is an error, this metric displays the error message (gpmMessage) as a value between 1 and 15, where:
  • 1 — Ok
  • 2 — Authentication to scoring engine failed
  • 3 — Scoring request failed
  • 4 — Agent list is empty
  • 5 — URS overload, interaction skipped
  • 6 — Predictor not found
  • 7 — Failed to build scoring request
  • 8 — SetIdealAgent or SetReadyCondition execution error
  • 9 — Interaction log not found in global map
  • 10 —- Unknown error
  • 11 — Channel is not supported
  • 12 — Reserved for future use
  • 13 — Call Abandoned
  • 14 — Call Routing Failed
  • 15 — Predictive Routing is turned off or not used for this interaction

Metrics in the Predictive Routing A/B Testing Report

Metric Description
Offered The total number of customer interactions that entered or began within the contact center during the reporting interval, and were offered to a resource, excluding interactions that were abandoned within the short-abandoned threshold. This count excludes interactions that:
  • were abandoned within the short-abandoned threshold,
  • could not be offered because no agent was in the Ready state,
  • were routed to an agent, accepted, and dropped within a one-second period.
Accepted The total number that customer interactions and warm consultations that were accepted, answered, or pulled by an agent, voice-treatment port, IVR port, or nonagent-associated DN (such as contact center resources that can alert) within the reporting interval.
Avg Handle Time (Fmt) The average amount of time (HH:MM:SS), within the reporting interval, that this agent spent handling interactions that the agent received. Computed as handle time divided by the sum of accepted interactions and received consultations.
First Contact Resolution Result First Contact Resolution (FCR) measures whether issues were resolved during the first customer attempt. A value of 0 indicates that the customer raised the same issue again within 7 days. FCR data is processed only after 7 days have elapsed, so any FCR data that appears in this report is at least 7 days old.
ASA (Fmt) The average amount of time (HH:MM:SS), within the reporting interval, that it took agents to accept, answer, or pull customer interactions
Avg Wrap Time (Fmt) The average amount of time (HH:MM:SS), within the reporting interval, that this agent spent on customer interactions while in ACW (Wrap) state.
Avg Engage Time (Fmt) The average amount of time (HH:MM:SS), within the reporting interval, that this agent was engaged with customers on interactions.
Avg Hold Time (Fmt) The average number of seconds, within the reporting interval, that customers spent on hold for interactions. This metric is attributed to the interval in which the interactions were accepted by a resource.
Transfer Rate The percentage of interactions that were transferred.

To view more detailed information about the metrics and attributes in this report, and other metrics and attributes that can be used to customize reports, see the Genesys CX Insights Projects Reference Guide.

Retrieved from "https://all.docs.genesys.com/PEC-REP/Current/RPRT/HRCXIPredictiveABTstng (2025-07-21 12:38:14)"
Comments or questions about this documentation? Contact us for support!