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

From Genesys Documentation
Jump to: navigation, search
(UCC: Updated benefits to align with calculators)
 
(14 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
{{SMART UseCase
 
{{SMART UseCase
 
|ID=CE37
 
|ID=CE37
|Title=Genesys Predictive Chatbots
+
|Title=Predictive Engagement for Customer Service
|Offering=PureEngage
+
|Offering=GenesysEngage-onpremises
 
|SMART_Benefits={{SMART Benefits
 
|SMART_Benefits={{SMART Benefits
 
|UCBenefitID=Improved Customer Experience
 
|UCBenefitID=Improved Customer Experience
|UCBenefit=Offer assistance only when needed to reduce customer annoyance.
+
|UCBenefit=Offer assistance only when in need of reducing customer annoyance.
 
}}{{SMART Benefits
 
}}{{SMART Benefits
 
|UCBenefitID=Reduced Handle Time
 
|UCBenefitID=Reduced Handle Time
 
|UCBenefit=When the engagement requires escalation from self-service to assisted service, the agent is provided context of the journey.
 
|UCBenefit=When the engagement requires escalation from self-service to assisted service, the agent is provided context of the journey.
 
}}{{SMART Benefits
 
}}{{SMART Benefits
|UCBenefitID=Reduced Administration Costs
+
|UCBenefitID=Improved Conversion Rates
|UCBenefit=Improve self-service rates by providing customers with the right information at the right time or proactively offering a chatbot to automate the conversation and prevent contact with an agent.
+
|UCBenefit=Follow individual customer journeys in real time on your website. Identify the moment of struggle or moment of opportunity and launch a chat or voice interaction with a sales agent at the right time to increase lead volume, improve lead qualification and reduce customer churn.
 +
}}{{SMART Benefits
 +
|UCBenefitID=Improved Employee Productivity
 +
|UCBenefit=Representatives are empowered with real time customer journey data which allows them to personalize and prioritize engagements with prospective and existing customers.
 +
}}{{SMART Benefits
 +
|UCBenefitID=Increased Revenue
 +
|UCBenefit=Retain customers by increasing customer satisfaction with faster and more personalized service. Improve the ability to up-sell and cross-sell existing customers with data based on their current interests, online journeys, and prior purchasing behavior.
 
}}
 
}}
|UCOverview=For customers seeking service or support, a company’s website is often the first point of contact, even if it is only to find a phone number to call. But companies are challenged with making sense of and learning to utilize all of the data generated by their website in a way that is both meaningful and actionable. As a result, the intentions and needs of individual consumers are overlooked, and we lose the ability to shape the journey in the moment and identify the customers who need help the most. As a result, customers either end up calling into the contact center (an expensive support channel) or get frustrated with your business because they can’t find the help they need. Genesys monitors website behavior, applies machine learning to determine audience segments and predicted outcomes in real time, and then uses that information to guide customers to a successful outcome – starting with an effective self-service offer of a chatbot to those customers who need the most help. Companies have lots of rich data within their CRM, marketing automation, contact centers and websites, and Genesys enables companies to unlock that data in real-time to engage customers proactively, thereby eliminating the need for a voice call or contact without context. <br /><br />Examples of how the customer experience can be optimized by using context include:
+
|UCIntro=Please be advised that this use case has been merged with Genesys Predictive Engagement (SL09). SL09 has now been decommissioned and all relevant content is displayed in this use case.
* A customer who is recognized to be having trouble submitting a loan application is prompted with a chatbot to automate a conversation about the loan application.
+
|UCOverview=One of the biggest challenges for the modern business is learning to work with the data available in a way that is both meaningful and easy to act on. The data generated by a website often goes unexplored, and as a result, the intentions and reactions of individual customers and prospects can be overlooked. Focus is often placed on the broad strokes–key metrics such as the number of conversions per month–and the ability to identify the potential customers who need engagement is lost. As a result, customers who may be on the verge of signing up for a trial, completing a checkout, searching for information regarding service or support, or any other desirable outcome, fall through the cracks. The high volume of website traffic makes it a challenge to identify the right individuals, best moments, and optimal ways to engage in real time. Expectations for time-to-respond are increasing but growing your staff is costly.     
* A customer needs to activate their new mobile phone, goes to the website, and searches for "device activation". A proactive chatbot is offered to help the customer walk through the steps.
+
 
* A customer is planning a trip abroad and needs to notify their credit card company. They go to the company's website and based on a search related to "travel alert", a chatbot is offered to assist to prevent the need to call the contact center.
+
Genesys Predictive Engagement uses machine learning to observe the progress of website visitors toward defined business outcomes –such as purchase completion or requesting a quote.  The technology enables the business to use real-time observations and predictions rather than static rules, to trigger intervention only at the points when it is needed most.
* A customer is proactively offered self-help options to assist with a transaction, for example providing a link to a video to help with a Return Merchandise Authorization (RMA).
+
 
Understanding and leveraging knowledge of online activities and behaviors can provide context to better handle a follow-up digital or voice interactions. This engagement intelligence can also be utilized for converting service requests to sales opportunities for cross-sell or up-sell. Genesys uses artificial intelligence to track the progress of website visitors towards defined outcomes – service requests, pending transactions, application status - and allows the business to define rules to trigger intervention only at the points when it is needed most.
+
For customers seeking service or support, a company’s website is often the first point of contact, even if it is only to find a phone number to call. But companies are challenged with making sense of and learning to use all the data generated by their website in a way that is both meaningful and actionable in real time. As a result, customers either end up calling into the contact center (an expensive support channel) or get frustrated with your business because they can’t find the help they need. Genesys Predictive Engagement prioritizes engagement with high value visitors and proactively offers chat to better utilize your staff and reduce your costs.
|UCSummary=Genesys monitors each and every individual customer journey on your company website and applies machine learning, audience segments, and outcome probabilities to identify the right moments for proactive engagement via a chatbot. If the consumer needs to interact with an agent, the agent has the customer journey information at their fingertips.
+
 
 +
Examples of how the customer experience can be optimized by using data, context, and website behavior for a predictive engagement:
 +
 
 +
*Use of machine learning to detect the progress of website visitors toward defined outcomes–purchase completion, requesting a quote–and enable the business to trigger intervention only at the points when it is needed most.
 +
*A customer who is recognized to be having trouble submitting a loan application is prompted with a proactive web chat enabling an agent to help the customer walk through the steps.
 +
*A customer needs to activate their new mobile phone, goes to the website, and searches for "device activation." A proactive chatbot is offered to help the customer walk through the steps.
 +
*A customer is planning a trip abroad and needs to notify their credit card company. They go to the company's website and based on a search related to "travel alert," a chatbot is offered to assist to prevent the need to call the contact center.
 +
*A customer is proactively offered self-help options to assist with a transaction, for example providing a link to a video to help with a Return Merchandise Authorization (RMA).
 +
|UCSummary=Understanding and using knowledge of online activities and behaviors can provide context to better handle a follow-up digital or voice interaction to help customers who are shopping, buying, using the company's products across the full customer life cycle. This engagement intelligence can also be used for converting service requests to sales opportunities for cross-sell or up-sell. Genesys uses artificial intelligence to observe and analyze the progress of website visitors toward defined outcomes – service requests, pending transactions, application status.  The technology allows the business to engage with customers using dynamic observations and predictions rather than simple static rules- creating happier customers, smarter employees, and better outcomes.
 +
 
 +
Companies have vast amounts of data within their CRM, marketing automation, contact centers and websites, and Genesys enables companies to unlock that data in real time to engage customers proactively,  eliminating the need for a voice call or contact without context. Genesys Predictive Engagement observes individual customer journeys on your company website and applies machine learning, dynamic (or audience) segmentation, and real-time outcome scoring to identify the right moments for proactive engagement with the right customer via chat, chatbot, or content offer.  
 +
 
 +
Predictive Engagement's real-time engagement sophistication increases customer satisfaction, improves conversion rate, and optimizes the use of agent resources for the highest value customers.  Predictive Engagement leads to improvement of key performance indicators such as call deflection, average order value (AOV), first contact resolution, and conversion rates.
 
|Description=Genesys monitors individual customer journeys on a company website and applies machine learning, dynamic personas, and outcome probabilities to identify the right moments for proactive engagement via a chatbot. If the consumer requires interaction with an agent, the agent has the customer journey information at their fingertips.
 
|Description=Genesys monitors individual customer journeys on a company website and applies machine learning, dynamic personas, and outcome probabilities to identify the right moments for proactive engagement via a chatbot. If the consumer requires interaction with an agent, the agent has the customer journey information at their fingertips.
  
Line 36: Line 54:
 
* Deflect from live agent contact by proactively displaying additional information or offering the most cost-effective channel
 
* Deflect from live agent contact by proactively displaying additional information or offering the most cost-effective channel
 
|BuyerPersonas=Chief Digital Officer, Head of Customer Experience, Head of Customer Service
 
|BuyerPersonas=Chief Digital Officer, Head of Customer Experience, Head of Customer Service
|CloudAssumptionsAdditional_Sales=* Requires Genesys Widgets 9
+
|MaturityLevel=Differentiated
* Requires Workspace Web Edition 9
+
|PremiseAssumptionsAdditional_Sales=*Requires Genesys Widgets 9<br />
|PremiseAssumptionsAdditional_Sales=* Requires Genesys Widgets 9<br />
+
*Requires Workspace Desktop Edition 8.5
* Requires Workspace Desktop Edition 8.5
 
 
|BusinessImageFlow={{SMART BusinessImageFlow
 
|BusinessImageFlow={{SMART BusinessImageFlow
 
|BusinessFlow='''Main Flow'''
 
|BusinessFlow='''Main Flow'''
|BusinessImage=https://www.lucidchart.com/documents/edit/e5d61d16-a4fb-4564-ab6f-2acd8111079a/0
+
|BusinessImage=https://www.lucidchart.com/documents/edit/b5e987d7-954c-4cf7-bbc9-bb8390753f61/0
|BusinessFlowDescription=# The customer starts browsing on the company website.  
+
|BusinessFlowDescription=#The customer starts browsing the company website.
# Genesys determines whether customer is new or returning to website, and associates data from previous journeys. '''[BL1]'''
+
#Genesys determines whether the customer is new or returning to the website, and associates data from previous journeys.
# The combination of segment and variations in outcome score can trigger an offer to chat with a chatbot while customer is browsing the website. '''[BL2, BL3]'''
+
#The combination of segment and variations in outcome score can trigger an offer to chat with an agent or with a chatbot while the customer is browsing the website.
# If the customer accepts the invitation for chat, a registration window will pop up where the customer can enter his data and start the conversation with Genesys Blended AI Bots (CE31 Use Case) will start. In the registration form, customer can either manually enter his contact details (name, email) or contact details will be pre-filled if already known to Genesys. '''[BL4]'''
+
#An algorithm determines the predicted availability of agents to handle the interactions.
 +
#If the customer accepts the invitation for chat, a registration window pops up where the customer can enter his data and the conversation with Genesys Blended AI Bots (CE31 Use Case) will start. In the registration form, customer can either manually enter his contact details (name, email) or contact details will be pre-filled if already known to Genesys.
 +
#In Genesys Routing logic, a decision can be made based using context (for example, customer segment, customer lifetime value) and current agent availability<br />
 +
 
 +
<br />
 +
}}{{SMART BusinessImageFlow
 +
|BusinessFlow='''Routing'''
 +
 
 +
 
 +
This diagram details the routing that takes place before and during the chat.
 +
|BusinessImage=https://www.lucidchart.com/documents/edit/38673dbe-49ce-47b8-aba2-4a876d0d4fd7/0
 +
|BusinessFlowDescription=#Genesys routes the interaction to an agent based on the skills, media, language, and other ACD routing choices.
 +
#An agent and customer are in conversation. The agent has access to full visitor context such as segment, journey information, and outcome score.
 +
#After the conversation ends, the agent sets a disposition code within their desktop to record the outcome of the conversation.
 
}}
 
}}
|BusinessLogic=====BL1 – Customer Identification<br />====
+
|BusinessLogic=====BL1 – Customer Identification====
Returning visitors can be detected using cookies and previous site visits can be associated with them. Identity information provided during the journey (e.g. email address or phone number) will be captured once explicitly submitted from the web page and can be used to identify the customer even across devices. If a customer uses a second device to visit the website the next day and provides a piece of this information, his visit can be associated to the previous journeys across devices. When customer identity cannot be determined, the customer will be handled as an anonymous user and all data tracked will be attached to this anonymous user. Once the customer is identified, all tracking data collected and to be collected will be associated to that specific customer. All customer information collected will be done in a GDPR compliant fashion.
+
The system can use cookies to detect returning visitors and associate them with previous site visits. Identity information provided during the journey (such as email address or phone number) is captured after it is explicitly submitted from the web page and can identify the visitor even across devices. After the customer is identified, all tracking data collected is associated to that specific customer. All customer information collected is done in a GDPR compliant fashion.
 +
====BL2 – Segment and Outcome Configuration====
 +
Segments are a way to categorize visitors on the website based on common behavior and attributes. Segments are configured upfront during system provisioning. A segment can be made up of one or both of these components:
  
====BL2 – Segment and Outcome Configuration====
+
*Attributes, such as browser type, device type, location, marketing campaign they are associated with, UTM parameters, and the referral website.
Segments are a way to categorize visitors on the website based on common behavior and attributes. Segments are configured upfront during the configuration of the system. A segment is made up of two components:
+
*Journey pattern, such as web browsing behavior, searches performed on the website, items clicked, returning users, cart abandoner, and high order value.
* Attributes: e.g. browser type, device type, location, UTM parameters, the referral website.
+
 
* Journey pattern: Web browsing behavior, searches performed on the website, items clicked, returning users, cart abandoner, high order value, etc.  
+
Outcomes or goals are specific tasks you want your visitors to perform on your website. As with segments, these are configured upfront. Typical outcomes include:
  
Outcomes or goals are specific tasks you want your visitors to perform on your website. As with Segments, these are configured upfront. Typical outcomes include:
+
*Check order status or return status
* Check order or return status
+
*Open or check status of a trouble ticket
* Open or check status of trouble ticket
+
*Locate warranty or return policy
* Locate warranty or return policy<br />
+
*Application submission
 +
*Online purchase confirmation
 +
*Submit payment
 +
*Online quote
 +
*Book a demo or appointment
  
 +
Genesys uses predictive analytics to evaluate in real time the probability for a specific outcome to be achieved, based on segment and visitor behavior on the website (the outcome score).
 
====BL3 – Action Map Configuration====
 
====BL3 – Action Map Configuration====
Action Maps determine the way to engage with the website visitor. Within action maps, you define the triggers that will result in an action to the customer. These triggers include:
+
Action maps determine the way to engage with the website visitor. Within action maps, you define the triggers that result in an action to the customer. These triggers can be based on any combination of:
* Segment
+
 
* User Activity
+
*Segment
* Outcome Score (typically, a drop in Outcome Score for a specific Segment can trigger a Chatbot offer)
+
*User activity
 +
*Outcome score (typically, a drop in outcome score for a specific segment can trigger a webchat)
  
 
====BL4 – Customer Invite and Registration Window====
 
====BL4 – Customer Invite and Registration Window====
 
Genesys Widgets will be used for:
 
Genesys Widgets will be used for:
* Invite messages for chatbot
+
 
* Collection of visitor's contact details
+
*Invite messages for webchat
* Engagement over chat session
+
*Collection of visitor's contact details
 +
*Engagement over chat session
 +
|DistributionLogic=The distribution of the interaction is determined by the target expression and virtual queue configured in the Genesys Predictive Engagement rules.
 
|CustomerInterfaceRequirements=Based on Genesys Widgets 9 with standard capabilities to adapt to customer corporate identity.
 
|CustomerInterfaceRequirements=Based on Genesys Widgets 9 with standard capabilities to adapt to customer corporate identity.
|AgentDeskRequirements=* Integration of Altocloud desktop gadgets into Workspace Desktop Edition 8.5 (in case chatbot conversation requires escalation to an agent)<br />
+
 
|RealTimeReporting=Altocloud Analytical Dashboards will be used in this use case for:
+
Predictive Engagement can automatically create leads in Salesforce and any CRM that uses Rest APIs through Action Map orchestration.
* Action Maps Performance with engagement funnel (Qualified, Offered, Accepted)<br />
+
|AgentDeskRequirements=*Integration of Genesys Predictive Engagement desktop gadgets into Workspace Desktop Edition 8.5 (in case chatbot conversation requires escalation to an agent)<br />
* Visits, Segments and Outcomes
+
|RealTimeReporting=An admin can see the Live Now view of current visitors and live tracking information on the site. The views allow admins to make real-time operational decisions.  For example, when a marketing campaign has gone live and drill into individual customer journeys.<br />
|HistoricalReporting=<span style="background-color: rgb(255, 255, 255);" data-mce-style="background-color: #ffffff;">Web Journey reporting from Altocloud will not be accessible via I</span>nfomart / CX Insights
+
|HistoricalReporting=The visitor activity report provides trend analysis and a drill-down by device type.
|GeneralAssumptions=* Genesys Widgets must be used
+
 
* General logic for routing of interactions will be using logic defined within mandatory use cases
+
Reporting on segments matched and outcomes achieved (available through Predictive Engagement).
* Design and configuration of this use should take it into account previous deployment of mandatory use cases
+
 
|CustomerAssumptions=* Customer must deploy both Altocloud and Widgets code snippets on their website / web pages
+
Action map performance of action types; webchat, content offers and architect flow.  It allows a funnel drill-down performance of the key stages which can identify resourcing requirements, queue issues,
|RequiresAll=CE31, CE18
+
 
|SMART_PremiseAssumptions={{SMART PremiseAssumptions
+
*Qualification
|Premise_Assumption=Integration of Altocloud desktop gadgets into Workspace Desktop Edition 8.5
+
*Offer
}}
+
*Acceptance
|SMART_CloudAssumptions={{SMART CloudAssumptions
+
*Engagement
|Cloud_Assumption=Integration of Altocloud desktop gadgets into Workspace Web Edition 9
+
 
}}
+
The Bot Dashboard provides a dashboard-style summary that you can use to evaluate the impact of Chat Bot, including visualizations of session and message volumes, and breaks down sessions based on whether bots, agents, or both, were involved. The dashboard report organizes data on the following tabs:
|SMART_HybridAssumptions={{SMART HybridAssumptions
+
 
|Hybrid_Assumption=1.1.0
+
* The Bot Sessions tab provides an overall view of bot sessions, including information about:
}}
+
* Session durations
 +
* How many sessions were initiated, started, interrupted, or failed
 +
* Information about the number of messages sent and received by bots.
 +
* The Media Sessions tab focuses on media sessions, contrasting the number of media sessions with the number (and percentage) of sessions with bots, and with the number of sessions (and percentage) with bots only.
 +
|DocVersion=v. 1.2.1
 +
|GeneralAssumptions=*Genesys Widgets 9 must be used
 +
*General logic for routing of interactions is defined with logic within the mandatory use cases
 +
*Design and configuration of this use should account for previous deployment of mandatory use cases
 +
|CustomerAssumptions=*Customer must deploy both Genesys Predictive Engagement and Widgets code snippets on their website / web pages
 +
|RequiresOr=CE18, CE31
 
}}
 
}}

Latest revision as of 12:30, February 16, 2021

This topic is part of the manual Genesys Engage On-Premises Use Cases for version Current of Genesys Use Cases.
Important
Please be advised that this use case has been merged with Genesys Predictive Engagement (SL09). SL09 has now been decommissioned and all relevant content is displayed in this use case.
Use AI powered journey analytics to observe website activity, predict visitor outcomes, and proactively engage with prospects and customers via agent-assisted chat, content offer or chatbot.

What's the challenge?

It’s challenging to identify the right individual, the best moments, and the optimal ways to offer assistance online. Companies want to shape their customers’ journeys and drive them towards desirable outcomes, but it’s hard to utilize all of the available data in a way that is meaningful and actionable. In addition, consumers expect fast answers, but it's expensive to always engage an agent.

What's the solution?

Proactively lead customers to successful journeys on your website. Apply machine learning, dynamic personas, and outcome probabilities to identify the right moments for proactive engagement via a web chat or help content screen-pop.

Other offerings:

Use Case Overview

Story and Business Context

One of the biggest challenges for the modern business is learning to work with the data available in a way that is both meaningful and easy to act on. The data generated by a website often goes unexplored, and as a result, the intentions and reactions of individual customers and prospects can be overlooked. Focus is often placed on the broad strokes–key metrics such as the number of conversions per month–and the ability to identify the potential customers who need engagement is lost. As a result, customers who may be on the verge of signing up for a trial, completing a checkout, searching for information regarding service or support, or any other desirable outcome, fall through the cracks. The high volume of website traffic makes it a challenge to identify the right individuals, best moments, and optimal ways to engage in real time. Expectations for time-to-respond are increasing but growing your staff is costly.

Genesys Predictive Engagement uses machine learning to observe the progress of website visitors toward defined business outcomes –such as purchase completion or requesting a quote. The technology enables the business to use real-time observations and predictions rather than static rules, to trigger intervention only at the points when it is needed most.

For customers seeking service or support, a company’s website is often the first point of contact, even if it is only to find a phone number to call. But companies are challenged with making sense of and learning to use all the data generated by their website in a way that is both meaningful and actionable in real time. As a result, customers either end up calling into the contact center (an expensive support channel) or get frustrated with your business because they can’t find the help they need. Genesys Predictive Engagement prioritizes engagement with high value visitors and proactively offers chat to better utilize your staff and reduce your costs.

Examples of how the customer experience can be optimized by using data, context, and website behavior for a predictive engagement:

  • Use of machine learning to detect the progress of website visitors toward defined outcomes–purchase completion, requesting a quote–and enable the business to trigger intervention only at the points when it is needed most.
  • A customer who is recognized to be having trouble submitting a loan application is prompted with a proactive web chat enabling an agent to help the customer walk through the steps.
  • A customer needs to activate their new mobile phone, goes to the website, and searches for "device activation." A proactive chatbot is offered to help the customer walk through the steps.
  • A customer is planning a trip abroad and needs to notify their credit card company. They go to the company's website and based on a search related to "travel alert," a chatbot is offered to assist to prevent the need to call the contact center.
  • A customer is proactively offered self-help options to assist with a transaction, for example providing a link to a video to help with a Return Merchandise Authorization (RMA).

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 Conversion Rates Follow individual customer journeys in real time on your website. Identify the moment of struggle or moment of opportunity and launch a chat or voice interaction with a sales agent at the right time to increase lead volume, improve lead qualification and reduce customer churn.
Improved Customer Experience Offer assistance only when in need of reducing customer annoyance.
Improved Employee Productivity Representatives are empowered with real time customer journey data which allows them to personalize and prioritize engagements with prospective and existing customers.
Increased Revenue Retain customers by increasing customer satisfaction with faster and more personalized service. Improve the ability to up-sell and cross-sell existing customers with data based on their current interests, online journeys, and prior purchasing behavior.
Reduced Handle Time When the engagement requires escalation from self-service to assisted service, the agent is provided context of the journey.
*You can sort all use cases according to their stated benefits here: Sort by benefits

Summary

Understanding and using knowledge of online activities and behaviors can provide context to better handle a follow-up digital or voice interaction to help customers who are shopping, buying, using the company's products across the full customer life cycle. This engagement intelligence can also be used for converting service requests to sales opportunities for cross-sell or up-sell. Genesys uses artificial intelligence to observe and analyze the progress of website visitors toward defined outcomes – service requests, pending transactions, application status. The technology allows the business to engage with customers using dynamic observations and predictions rather than simple static rules- creating happier customers, smarter employees, and better outcomes.

Companies have vast amounts of data within their CRM, marketing automation, contact centers and websites, and Genesys enables companies to unlock that data in real time to engage customers proactively, eliminating the need for a voice call or contact without context. Genesys Predictive Engagement observes individual customer journeys on your company website and applies machine learning, dynamic (or audience) segmentation, and real-time outcome scoring to identify the right moments for proactive engagement with the right customer via chat, chatbot, or content offer.

Predictive Engagement's real-time engagement sophistication increases customer satisfaction, improves conversion rate, and optimizes the use of agent resources for the highest value customers. Predictive Engagement leads to improvement of key performance indicators such as call deflection, average order value (AOV), first contact resolution, and conversion rates.


Use Case Definition

Business Flow

Main Flow

Business Flow Description

  1. The customer starts browsing the company website.
  2. Genesys determines whether the customer is new or returning to the website, and associates data from previous journeys.
  3. The combination of segment and variations in outcome score can trigger an offer to chat with an agent or with a chatbot while the customer is browsing the website.
  4. An algorithm determines the predicted availability of agents to handle the interactions.
  5. If the customer accepts the invitation for chat, a registration window pops up where the customer can enter his data and the conversation with Genesys Blended AI Bots (CE31 Use Case) will start. In the registration form, customer can either manually enter his contact details (name, email) or contact details will be pre-filled if already known to Genesys.
  6. In Genesys Routing logic, a decision can be made based using context (for example, customer segment, customer lifetime value) and current agent availability


Business Flow

Routing


This diagram details the routing that takes place before and during the chat.

Business Flow Description

  1. Genesys routes the interaction to an agent based on the skills, media, language, and other ACD routing choices.
  2. An agent and customer are in conversation. The agent has access to full visitor context such as segment, journey information, and outcome score.
  3. After the conversation ends, the agent sets a disposition code within their desktop to record the outcome of the conversation.

Business and Distribution Logic

Business Logic

BL1 – Customer Identification

The system can use cookies to detect returning visitors and associate them with previous site visits. Identity information provided during the journey (such as email address or phone number) is captured after it is explicitly submitted from the web page and can identify the visitor even across devices. After the customer is identified, all tracking data collected is associated to that specific customer. All customer information collected is done in a GDPR compliant fashion.

BL2 – Segment and Outcome Configuration

Segments are a way to categorize visitors on the website based on common behavior and attributes. Segments are configured upfront during system provisioning. A segment can be made up of one or both of these components:

  • Attributes, such as browser type, device type, location, marketing campaign they are associated with, UTM parameters, and the referral website.
  • Journey pattern, such as web browsing behavior, searches performed on the website, items clicked, returning users, cart abandoner, and high order value.

Outcomes or goals are specific tasks you want your visitors to perform on your website. As with segments, these are configured upfront. Typical outcomes include:

  • Check order status or return status
  • Open or check status of a trouble ticket
  • Locate warranty or return policy
  • Application submission
  • Online purchase confirmation
  • Submit payment
  • Online quote
  • Book a demo or appointment

Genesys uses predictive analytics to evaluate in real time the probability for a specific outcome to be achieved, based on segment and visitor behavior on the website (the outcome score).

BL3 – Action Map Configuration

Action maps determine the way to engage with the website visitor. Within action maps, you define the triggers that result in an action to the customer. These triggers can be based on any combination of:

  • Segment
  • User activity
  • Outcome score (typically, a drop in outcome score for a specific segment can trigger a webchat)

BL4 – Customer Invite and Registration Window

Genesys Widgets will be used for:

  • Invite messages for webchat
  • Collection of visitor's contact details
  • Engagement over chat session

Distribution Logic

The distribution of the interaction is determined by the target expression and virtual queue configured in the Genesys Predictive Engagement rules.

User Interface & Reporting


Agent UI

  • Integration of Genesys Predictive Engagement desktop gadgets into Workspace Desktop Edition 8.5 (in case chatbot conversation requires escalation to an agent)

Reporting

Real-time Reporting

An admin can see the Live Now view of current visitors and live tracking information on the site. The views allow admins to make real-time operational decisions. For example, when a marketing campaign has gone live and drill into individual customer journeys.

Historical Reporting

The visitor activity report provides trend analysis and a drill-down by device type.

Reporting on segments matched and outcomes achieved (available through Predictive Engagement).

Action map performance of action types; webchat, content offers and architect flow. It allows a funnel drill-down performance of the key stages which can identify resourcing requirements, queue issues,

  • Qualification
  • Offer
  • Acceptance
  • Engagement

The Bot Dashboard provides a dashboard-style summary that you can use to evaluate the impact of Chat Bot, including visualizations of session and message volumes, and breaks down sessions based on whether bots, agents, or both, were involved. The dashboard report organizes data on the following tabs:

  • The Bot Sessions tab provides an overall view of bot sessions, including information about:
  • Session durations
  • How many sessions were initiated, started, interrupted, or failed
  • Information about the number of messages sent and received by bots.
  • The Media Sessions tab focuses on media sessions, contrasting the number of media sessions with the number (and percentage) of sessions with bots, and with the number of sessions (and percentage) with bots only.

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

Digital

Self-Service and Automation

None None


General Assumptions

  • Genesys Widgets 9 must be used
  • General logic for routing of interactions is defined with logic within the mandatory use cases
  • Design and configuration of this use should account for previous deployment of mandatory use cases

Customer Responsibilities

  • Customer must deploy both Genesys Predictive Engagement and Widgets code snippets on their website / web pages



Document Version

  • Version v. 1.2.1 last updated February 16, 2021

Comments or questions about this documentation? Contact us for support!