Difference between revisions of "Solution/ChatSolutions"
m (Text replacement - "Genesys Cloud" to "Genesys Cloud CX") |
|||
(21 intermediate revisions by 8 users not shown) | |||
Line 1: | Line 1: | ||
{{Article | {{Article | ||
|Standalone=Yes | |Standalone=Yes | ||
− | |DisplayName= | + | |DisplayName=Genesys Predictive Engagement with advanced chat routing |
− | |TocName= | + | |TocName=Genesys Predictive Engagement with advanced chat routing |
+ | |Context=Genesys Cloud CX and Genesys Predictive Engagement offer advanced routing, auto-response, and AI capabilities that provide customized chat solutions to customers. | ||
+ | |Dimension=WebChat | ||
|ComingSoon=No | |ComingSoon=No | ||
− | | | + | |Platform=GenesysCloud |
|Section={{Section | |Section={{Section | ||
+ | |alignment=Vertical | ||
+ | |structuredtext=<br />{{NoteFormat|This guide only applies to customers using {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_web_chats|display text=web chat}}. If you are a Genesys Cloud CX customer, we encourage you to use the new {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_web_messaging|display text=web messaging}} feature to replace web chat.|}}<br /> | ||
+ | |Status=No | ||
+ | }}{{Section | ||
|sectionHeading=Solution overview | |sectionHeading=Solution overview | ||
− | |||
− | |||
|alignment=Horizontal | |alignment=Horizontal | ||
− | |||
|Media=Image | |Media=Image | ||
− | |structuredtext=The advanced chat solution is a fully customizable and flexible solution that | + | |image=GPE_chat_solution_overview_diagram.png |
+ | |AltText=Advanced chat has the combined benefits of predictive engagement, architect, advanced routing, auto-responses, and chat bots. | ||
+ | |structuredtext=The advanced chat solution is a fully customizable and flexible solution that allows you to send targeted and tailored chat offers to your customers. | ||
'''Highlights:''' | '''Highlights:''' | ||
− | * '''Advanced routing capabilities''' | + | |
− | ** Make routing decisions based on the needs and profile of the customer | + | *'''Advanced routing capabilities''' |
− | ** Update routing decisions dynamically, even within a chat flow | + | **Make routing decisions based on the needs and profile of the customer |
− | ** Define the circumstances, such as business hours and schedules, in which a chat is routed to either a chatbot or | + | **Update routing decisions dynamically, even within a chat flow |
− | * '''Auto-response capabilities''' | + | **Define the circumstances, such as business hours and schedules, in which a chat is routed to either a chatbot or a human agent |
− | ** Send an automatic notification to the customer - ''Thanks for contacting us; we will be with you shortly'' | + | |
− | ** Send a standard bot-generated message - ''Thanks for waiting.'' ''How | + | *'''Auto-response capabilities''' |
− | + | **Send an automatic notification to the customer - ''Thanks for contacting us; we will be with you shortly.'' | |
− | + | **Send a standard bot-generated message - ''Thanks for waiting.'' ''How may we help you today?'' | |
− | ** Call on a chatbot to handle interactions | + | |
− | ** Use | + | *'''Powered by AI''' |
+ | **Call on a chatbot to handle interactions | ||
+ | **Use the predictive engagement features to monitor engagements, predict behavior, and respond according to configured action maps | ||
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
|sectionHeading=How it works | |sectionHeading=How it works | ||
− | | | + | |alignment=Horizontal |
− | | | + | |Media=Image |
− | | | + | |image=GPE_chat_solution_how_it_works_diagram.png |
− | |structuredtext=[[ | + | |AltText=The advanced chat features ensure the customer is routed to the right agent at all times, no matter their journey. |
+ | |structuredtext=To illustrate how these advanced chat features can enhance the customer journey, let's look at a typical customer journey. For the purposes of this article, let's say the customer is shopping online. We'll break the journey down into five stages: | ||
+ | |||
+ | *'''[[#Stage1|Stage 1:]]''' Customer visits a website configured with Genesys Predictive Engagement. | ||
+ | **'''Task:''' Add the Genesys Predictive Engagement snippet to your website and configure web tracking in Predictive Engagement. | ||
− | + | *'''[[#Stage2|Stage 2:]]''' Customer receives a chat offer. | |
− | + | **'''Task:''' Add a web chat widget to your website and configure Genesys Predictive Engagement. | |
− | + | *'''[[#Stage3|Stage 3:]]''' Customer accepts the chat offer and receives a welcome message. | |
− | * '''[[#Stage2|Stage 2]]''' | + | **'''Task:''' Configure auto-responses. |
− | ** ''' | + | *'''[[#Stage4|Stage 4:]]''' Customer interacts with a chatbot. |
− | * '''[[#Stage3|Stage 3]]''' | + | **'''Task:''' Configure the chat flow, link a chat flow to a web chat widget, and call on a chatbot. |
− | ** ''' | + | *'''[[#Stage5|Stage 5:]]''' Customer escalates to an agent. |
− | * '''[[#Stage4|Stage 4]]''' | + | **'''Task:''' Define the routing strategy. |
− | ** ''' | + | |structuredtextwide=The following sections describe these pivotal stages of the journey, and reference the steps and procedures required to complete that stage of the journey. |
− | * '''[[#Stage5|Stage 5]]''' | ||
− | ** ''' | ||
− | |||
− | |structuredtextwide= | ||
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
− | |sectionHeading=Stage 1 | + | |sectionHeading=Stage 1: Customer visits the website |
|anchor=Stage1 | |anchor=Stage1 | ||
− | |||
− | |||
|alignment=Horizontal | |alignment=Horizontal | ||
− | |||
|Media=Image | |Media=Image | ||
− | |structuredtext=In the first stage of the customer journey, the customer visits the website, which is configured with | + | |image=GPE_customer_visits_website_diagram.png |
− | + | |AltText=Genesys Predictive Engagement monitors the engagement | |
− | To | + | |structuredtext=In the first stage of the customer journey, the customer visits the website, which is configured with Genesys Predictive Engagement. Predictive Engagement monitors the customer's engagement and decides how and when to engage the customer to achieve a defined desired outcome. |
+ | |structuredtextwide=To allow Genesys Predictive Engagement to monitor the customer journey, complete the following tasks: | ||
− | + | *{{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=Tracking_snippet|display text=Add the Genesys Predictive Engagement snippet to your website}} | |
− | + | *{{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=Web_tracking|display text=Configure web tracking in Genesys Predictive Engagement}} | |
− | + | {{NoteFormat|1=First, ensure that you meet all [https://help.mypurecloud.com/articles/?p=195855Genesys Predictive Engagement prerequisites].|2=}} | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | {{ | ||
− | |||
− | |||
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
− | |sectionHeading=Stage 2 | + | |sectionHeading=Stage 2: Customer receives a chat offer |
|anchor=Stage2 | |anchor=Stage2 | ||
− | |||
− | |||
|alignment=Horizontal | |alignment=Horizontal | ||
− | |||
|Media=Image | |Media=Image | ||
− | |structuredtext=For this example, let's say your customer browses through the promotional offers on your website and | + | |image=GPE_customer_receives_chat_offer_diagram.png |
+ | |AltText=Predictive Engagement determines if it's time to offer a chat interaction. | ||
+ | |structuredtext=For this example, let's say your customer browses through the promotional offers on your website and then adds items to the cart. The customer leaves the shopping cart and continues to browse the website. The customer continues browsing for several minutes, but doesn't adding anything else to the shopping cart. The likelihood of the customer abandoning the shopping cart and leaving the website increases, so a popup window appears on-screen, inviting the customer to chat with an agent. | ||
− | For this scenario to happen, create a widget (Version 2) for web chat and configure | + | For this scenario to happen, create a widget (Version 2) for web chat and configure Genesys Predictive Engagement. |
− | |||
|structuredtextwide====Widget configuration=== | |structuredtextwide====Widget configuration=== | ||
− | To add the widget | + | To add the widget (Version 2) for web chat to your website, complete the following tasks: |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | = | + | *[https://help.mypurecloud.com/articles/?p=195772 Create the widget and route it to a chat flow] ( Follow the Version 2 widget procedures to complete this task.) |
− | + | *[https://developer.genesys.cloud/api/webchat/widget-version2.html#configuration Add the deployment key to your website] | |
+ | ===Genesys Predictive Engagement configuration=== | ||
+ | To configure Genesys Predictive Engagement, complete the following tasks: | ||
− | + | *{{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=Manage_segments|display text=Create a segment in Genesys Predictive Engagement}} | |
− | + | *{{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=Manage_outcomes|display text=Create an outcome in Genesys Predictive Engagement}} | |
− | + | *{{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=Action_maps|display text=Create an action map in Genesys Predictive Engagement}} {{NoteFormat|1=Ensure that you select web chat as the engagement method.|2=}} | |
− | + | *{{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=Apply|display text=Apply an action map to your website}} | |
− | + | *{{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=Route|display text=Route to a target queue}} {{NoteFormat|1=If chatbots will handle interactions, do not enable '''Route if agents available'''.|2=}} | |
− | + | *{{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=Chat_offers|display text=Design the chat offer and chat window}} | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | {{ | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | {{ | ||
− | |||
− | |||
− | |||
− | |||
− | |||
===Resources=== | ===Resources=== | ||
− | * [https://help.mypurecloud.com/articles/ | + | *[https://help.mypurecloud.com/articles/?p=169697 About Genesys Predictive Engagement] |
− | * [https://help.mypurecloud.com/articles/ | + | *[https://help.mypurecloud.com/articles/?p=196175 Widgets feature comparison] |
− | * [https://help.mypurecloud.com/articles/ | + | *[https://help.mypurecloud.com/articles/?p=194115 About widgets for web chat] |
− | * [https://help.mypurecloud.com/articles/ | + | *[https://help.mypurecloud.com/articles/?p=3441 Work with web chat interactions] |
− | * [https://help.mypurecloud.com/articles/ | + | *[https://help.mypurecloud.com/articles/?p=195871 Genesys Predictive Engagement quick start guide] |
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
− | |sectionHeading=Stage 3 | + | |sectionHeading=Stage 3: Customer accepts the chat offer and receives a welcome message |
|anchor=Stage3 | |anchor=Stage3 | ||
− | |||
− | |||
|alignment=Horizontal | |alignment=Horizontal | ||
+ | |Media=Image | ||
|image=ChatOffers_Stage3.png | |image=ChatOffers_Stage3.png | ||
− | | | + | |AltText=Customer accepts the chat offer and receives a welcome message. |
− | |structuredtext=The customer accepts the chat offer, the chat window opens, and the customer sees | + | |structuredtext=The customer accepts the chat offer, the chat window opens, and the customer sees an auto-response notice. For example, "''Hello, we will be with you shortly."'' Auto-response notices appear as a system message to the customer. |
− | A few seconds later, | + | A few seconds later, a standard auto-response message appears, which is bot-generated. For example, "''Thanks for waiting - how can we help you today?''" This time, a bot avatar appears next to the message. The purpose is to extract preliminary information from the customer. |
− | + | |structuredtextwide=You can send responses from the chat flow, with the content coming from Genesys Cloud CX's canned responses. Alternatively, you can write the response directly into the flow. <h3>Resources</h3>For more information about the response options, see the following: <ul><li>[https://help.mypurecloud.com/articles/?p=190600 Inbound chat flows overview]</li><li>[https://help.mypurecloud.com/articles/?p=51965 About canned responses]</li><li>[https://help.mypurecloud.com/articles/?p=181977 Send Response action]</li></ul> | |
− | |structuredtextwide=You can send responses from the chat flow, with the content coming from | ||
− | <h3>Resources</h3><ul><li>[https://help.mypurecloud.com/articles/ | ||
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
− | |sectionHeading=Stage 4 | + | |sectionHeading=Stage 4: Customer interacts with a chatbot |
|anchor=Stage4 | |anchor=Stage4 | ||
− | |||
− | |||
|alignment=Horizontal | |alignment=Horizontal | ||
− | |||
|Media=Image | |Media=Image | ||
+ | |image=GPE_customer_interacts_with_chatbot_diagram.png | ||
+ | |AltText=Customer interacts with chat bot. No agent involved. | ||
|structuredtext=In this stage of the journey, the customer begins interacting with a chatbot. | |structuredtext=In this stage of the journey, the customer begins interacting with a chatbot. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
+ | *'''Chatbot:''' Thanks for waiting - how can we help you today? | ||
+ | *'''Customer:''' I'm wondering about the return policy on these shoes in my shopping cart. I can't find the information on your website. | ||
+ | *'''Chatbot:''' You have 30 days from the purchase date to return any item purchased on our website. | ||
+ | *'''Customer:''' OK, thanks. One more question; I want to purchase a loyalty card. Can you help me with that? | ||
+ | *'''Chatbot:''' Please hold while I transfer you to an agent. | ||
+ | |structuredtextwide=To allow this type of interaction, complete the following tasks: | ||
+ | |||
+ | *[https://help.mypurecloud.com/articles/?p=3792 Create a flow in Architect] {{NoteFormat|1=Ensure that you link the flow to the widget for web chat. For more information, see stage 2.|2=}} | ||
+ | *[https://help.mypurecloud.com/articles/?p=207068 Call on a chatbot for a supported chatbot integration] | ||
===Resources=== | ===Resources=== | ||
− | * [https://help.mypurecloud.com/articles/ | + | *[https://help.mypurecloud.com/articles/?p=53682 About Architect] |
− | * [https://help.mypurecloud.com/articles/ | + | *[https://help.mypurecloud.com/articles/?p=190600 Inbound chat flows overview] |
− | * [https://help.mypurecloud.com/articles/ | + | *[https://help.mypurecloud.com/articles/?p=20587 Task and state editor actions] |
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
− | |sectionHeading=Stage 5 | + | |sectionHeading=Stage 5: Customer escalates to an agent |
|anchor=Stage5 | |anchor=Stage5 | ||
− | |||
− | |||
|alignment=Horizontal | |alignment=Horizontal | ||
− | |||
|Media=Image | |Media=Image | ||
− | |structuredtext=The chatbot explained the return policy and then asked the customer | + | |image=GPE_customer_escalates_to_agent_diagram.png |
− | * '''Chatbot:''' Do you have any further questions? | + | |AltText=The chat bot transfers the interaction to an agent. |
− | * '''Customer:''' Yes, I want to speak to an | + | |structuredtext=The chatbot explained the return policy and then asked whether the customer had any more questions: |
− | * '''Chatbot:''' Please hold for a customer service associate. | + | |
+ | *'''Chatbot:''' Do you have any further questions? | ||
+ | *'''Customer:''' Yes, I want to speak to an someone about purchasing a loyalty card. | ||
+ | *'''Chatbot:''' Please hold for a customer service associate. | ||
− | At this point, you can decide which queue | + | At this point, you can decide which queue to route the customer to. You have two general options: use the suggested queue or define a queue. |
===Use suggested queue=== | ===Use suggested queue=== | ||
− | + | You can use the queue defined in the Genesys Predictive Engagement {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=Route|display text=Route to a target}} option. If no queue is specified in Predictive Engagement, you can use the default queue specified in the website configuration. | |
===Define a queue=== | ===Define a queue=== | ||
If you don't want to use the suggested queue, you can use data actions to do the following: | If you don't want to use the suggested queue, you can use data actions to do the following: | ||
− | * Perform a | + | |
− | * Choose a queue based on some other pre-defined criteria: | + | *Perform a visitor lookup in Genesys Predictive Engagement and then suggest a queue based on the search results. For example, if the lookup shows the customer is likely ready to buy something, it suggests that you route to a live agent in a sales queue. |
− | ** Data dips allow customers to gather specific metrics about a given queue before making a decision. | + | *Choose a queue based on some other pre-defined criteria: |
− | ** Use schedules to determine which queue to route to. | + | **Data dips allow customers to gather specific metrics about a given queue before making a decision. |
− | + | **Use schedules to determine which queue to route to. | |
− | |structuredtextwide=The tasks required | + | |structuredtextwide=The tasks required for stage 5 depend on your routing choices. |
+ | |||
===Resources=== | ===Resources=== | ||
+ | For more information about routing and queue configuration, see the following: | ||
− | * [https://help.mypurecloud.com/articles/ | + | *[https://help.mypurecloud.com/articles/?p=563 Interaction routing configuration] |
− | * [https://help.mypurecloud.com/articles/ | + | *[https://help.mypurecloud.com/articles/?p=163198 About routing] |
− | * [https://help.mypurecloud.com/articles/ | + | *[https://help.mypurecloud.com/articles/?p=18650 Create and configure queues] |
− | * [https://help.mypurecloud.com/articles/ | + | *[https://help.mypurecloud.com/articles/?p=41705 Schedules] |
|Status=No | |Status=No | ||
}} | }} | ||
}} | }} |
Latest revision as of 21:28, November 9, 2021
Contents
Genesys Cloud CX and Genesys Predictive Engagement offer advanced routing, auto-response, and AI capabilities that provide customized chat solutions to customers.
Solution overview
The advanced chat solution is a fully customizable and flexible solution that allows you to send targeted and tailored chat offers to your customers.
Highlights:
- Advanced routing capabilities
- Make routing decisions based on the needs and profile of the customer
- Update routing decisions dynamically, even within a chat flow
- Define the circumstances, such as business hours and schedules, in which a chat is routed to either a chatbot or a human agent
- Auto-response capabilities
- Send an automatic notification to the customer - Thanks for contacting us; we will be with you shortly.
- Send a standard bot-generated message - Thanks for waiting. How may we help you today?
- Powered by AI
- Call on a chatbot to handle interactions
- Use the predictive engagement features to monitor engagements, predict behavior, and respond according to configured action maps
How it works
To illustrate how these advanced chat features can enhance the customer journey, let's look at a typical customer journey. For the purposes of this article, let's say the customer is shopping online. We'll break the journey down into five stages:
- Stage 1: Customer visits a website configured with Genesys Predictive Engagement.
- Task: Add the Genesys Predictive Engagement snippet to your website and configure web tracking in Predictive Engagement.
- Stage 2: Customer receives a chat offer.
- Task: Add a web chat widget to your website and configure Genesys Predictive Engagement.
- Stage 3: Customer accepts the chat offer and receives a welcome message.
- Task: Configure auto-responses.
- Stage 4: Customer interacts with a chatbot.
- Task: Configure the chat flow, link a chat flow to a web chat widget, and call on a chatbot.
- Stage 5: Customer escalates to an agent.
- Task: Define the routing strategy.
The following sections describe these pivotal stages of the journey, and reference the steps and procedures required to complete that stage of the journey.
Stage 1: Customer visits the website
To allow Genesys Predictive Engagement to monitor the customer journey, complete the following tasks:
- Add the Genesys Predictive Engagement snippet to your website
- Configure web tracking in Genesys Predictive Engagement
Stage 2: Customer receives a chat offer
For this example, let's say your customer browses through the promotional offers on your website and then adds items to the cart. The customer leaves the shopping cart and continues to browse the website. The customer continues browsing for several minutes, but doesn't adding anything else to the shopping cart. The likelihood of the customer abandoning the shopping cart and leaving the website increases, so a popup window appears on-screen, inviting the customer to chat with an agent.
For this scenario to happen, create a widget (Version 2) for web chat and configure Genesys Predictive Engagement.Widget configuration
To add the widget (Version 2) for web chat to your website, complete the following tasks:
- Create the widget and route it to a chat flow ( Follow the Version 2 widget procedures to complete this task.)
- Add the deployment key to your website
Genesys Predictive Engagement configuration
To configure Genesys Predictive Engagement, complete the following tasks:
- Create a segment in Genesys Predictive Engagement
- Create an outcome in Genesys Predictive Engagement
- Create an action map in Genesys Predictive Engagement ImportantEnsure that you select web chat as the engagement method.
- Apply an action map to your website
- Route to a target queue ImportantIf chatbots will handle interactions, do not enable Route if agents available.
- Design the chat offer and chat window
Resources
Stage 3: Customer accepts the chat offer and receives a welcome message
The customer accepts the chat offer, the chat window opens, and the customer sees an auto-response notice. For example, "Hello, we will be with you shortly." Auto-response notices appear as a system message to the customer.
A few seconds later, a standard auto-response message appears, which is bot-generated. For example, "Thanks for waiting - how can we help you today?" This time, a bot avatar appears next to the message. The purpose is to extract preliminary information from the customer.Resources
For more information about the response options, see the following:Stage 4: Customer interacts with a chatbot
In this stage of the journey, the customer begins interacting with a chatbot.
- Chatbot: Thanks for waiting - how can we help you today?
- Customer: I'm wondering about the return policy on these shoes in my shopping cart. I can't find the information on your website.
- Chatbot: You have 30 days from the purchase date to return any item purchased on our website.
- Customer: OK, thanks. One more question; I want to purchase a loyalty card. Can you help me with that?
- Chatbot: Please hold while I transfer you to an agent.
To allow this type of interaction, complete the following tasks:
- Create a flow in Architect ImportantEnsure that you link the flow to the widget for web chat. For more information, see stage 2.
- Call on a chatbot for a supported chatbot integration
Resources
Stage 5: Customer escalates to an agent
The chatbot explained the return policy and then asked whether the customer had any more questions:
- Chatbot: Do you have any further questions?
- Customer: Yes, I want to speak to an someone about purchasing a loyalty card.
- Chatbot: Please hold for a customer service associate.
At this point, you can decide which queue to route the customer to. You have two general options: use the suggested queue or define a queue.
Use suggested queue
You can use the queue defined in the Genesys Predictive Engagement Route to a target option. If no queue is specified in Predictive Engagement, you can use the default queue specified in the website configuration.
Define a queue
If you don't want to use the suggested queue, you can use data actions to do the following:
- Perform a visitor lookup in Genesys Predictive Engagement and then suggest a queue based on the search results. For example, if the lookup shows the customer is likely ready to buy something, it suggests that you route to a live agent in a sales queue.
- Choose a queue based on some other pre-defined criteria:
- Data dips allow customers to gather specific metrics about a given queue before making a decision.
- Use schedules to determine which queue to route to.
The tasks required for stage 5 depend on your routing choices.
Resources
For more information about routing and queue configuration, see the following: