|
|
| (12 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| − | {{SMART UseCase
| + | #REDIRECT [[UseCases/Current/GenesysCloud/CE37]] |
| − | |ID=SL09
| |
| − | |Title=Genesys Predictive Engagement
| |
| − | |Offering=PureEngage
| |
| − | |SMART_Benefits={{SMART Benefits
| |
| − | |UCBenefitID=Increased Revenue
| |
| − | |UCBenefit=Increase conversions and revenue closure by engaging the right shoppers at the right time and Accelerate sales cycle and lead conversion rates (MQL to SQL to conversion)
| |
| − | }}{{SMART Benefits
| |
| − | |UCBenefitID=Improved Employee Utilization
| |
| − | |UCBenefit=Engage sales reps only when they can have the most impact on the sale
| |
| − | }}{{SMART Benefits
| |
| − | |UCBenefitID=Improved Customer Experience
| |
| − | |UCBenefit=Give sales reps visibility into the real-time customer journey and personas, allowing the right agent to prioritize their time with the right customer at the right time and no longer disrupt the website visitor experience with unnecessary offers of chat or interaction
| |
| − | }}{{SMART Benefits
| |
| − | |UCBenefitID=Reduced Administration Costs
| |
| − | |UCBenefit=Reduce customer acquisition cost (CAC)
| |
| − | }}
| |
| − | |UCOverview=<span>A large, modern day business challenge is learning how to use all of the available data in ways that are both meaningful and easy to act on. The data generated by a website is often unexplored. 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 monthly page views–and we lose the ability to identify the potential customers who need engagement most. As a result, prospects who may be close to signing up for a trial, completing a checkout, or another desirable outcome, fall through the cracks.</span>
| |
| − | | |
| − | | |
| − | <span>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 inside sales staff is costly. Marketing dollars spent on a wide range of demand generation activities, but it is difficult to connect the dots from lead to contact to opportunity to closed.</span>
| |
| − | | |
| − | | |
| − | <span>With Genesys Altocloud, you can predict and prioritize high-value leads for your sales team. These benefits allow sales representatives to engage and proactively offer a web chat to more efficiently utilize staff and reduce costs. Genesys Predictive Engagement uses machine learning to track the progress of website visitors toward defined outcomes–purchase completion, requesting a quote–and enables the business to define rules to trigger intervention only at the points when it needs it the most.</span>
| |
| − | |UCSummary=<span>Genesys Predictive Engagement monitors individual customer journeys on your company website. It applies machine learning, dynamic segmentation, and real-time outcome scoring to identify the right moments for proactive engagement with the right customer through chat. When the visitor interacts, the sales rep has the customer journey information at their fingertips.</span>
| |
| − | |Description=Predictive Engagement 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 chat. It can instantly notify sales reps about hot leads and their behaviors. When the consumer interacts, the sales rep will have the customer journey information at their fingertips.
| |
| − | | |
| − | Reporting, Callback, SFDC Third-Party Integration and Content Offer capabilities with Altocloud are planned in 2019, for further details please contact your respective Product Manager.
| |
| − | |PainPoints=* Inability to see, understand and engage in real time with customers and prospects across channels.
| |
| − | * Low conversion rate on website.
| |
| − | * Poorly utilized inside sales staff.
| |
| − | * Difficulty in creating and converting qualified online sales opportunities.
| |
| − | * Low optimization of website user journeys of efficient engagement through self- and assisted- service.
| |
| − | |DesiredState=* Use journey analytics to detect where customers or prospects struggle on a website. Use this information to improve their purchasing journeys.
| |
| − | * Identify the visitor's segmentation, monitor their web behavior, and predict their outcome score related to the online purchasing process.
| |
| − | * Use machine learning to profile behavior, predict outcomes, and allow organizations to define rules on when intervention is necessary.
| |
| − | * Proactively engage with prospects via chat or content offer if this score drops below a defined threshold while on the website.
| |
| − | * Engage a sales rep at the critical point in the sales process to increase likelihood of closing the sale, while improving customer experience.
| |
| − | * Identify hot leads on the website via customer browsing behavior and predict customer likelihood to perform a specific action.
| |
| − | * Provide sales rep with context from the customer journey on the website.
| |
| − | * Deflect from live agent contact by proactively displaying additional information or offering the most cost-effective channel for the specific customer segment.
| |
| − | |BuyerPersonas=Chief Digital Officer, Head of Sales, Head of Ecommerce
| |
| − | |MaturityLevel=Differentiated
| |
| − | |CloudAssumptionsAdditional_Sales=<span>Callback, SFDC Third-Party Integration and Content Offer capabilities with Altocloud are planned in 2019, for further details please contact your respective Product Manager.</span>
| |
| − | | |
| − | <span>Historical reporting is planned in 2019, for further details please contact your respective Product Manager.</span>
| |
| − | |BusinessImageFlow={{SMART BusinessImageFlow
| |
| − | |BusinessFlow='''Main Flow'''
| |
| − | | |
| − | | |
| − | The following diagram shows the main flow of the use case, from the point of view of the system.
| |
| − | |BusinessImage=https://www.lucidchart.com/documents/edit/b31f9b5f-7084-4fc4-8129-0bc938776ddf/0
| |
| − | |BusinessFlowDescription=# A visitor starts browsing the company website.
| |
| − | # Genesys determines whether visitor is new or returning to website, and associates data from previous journeys.
| |
| − | # Genesys continues to monitor website behavior and update segment attribution and outcome score as appropriate.
| |
| − | # The combination of segment and variations in outcome score can eventually trigger a web chat offer to the visitor.
| |
| − | # If configured within the Action Map, an algorithm determines the availability of sales reps to handle the interaction.
| |
| − | # If sales reps are predicted to be available to handle chat, a proactive invitation to chat is presented to the visitor.
| |
| − | # If the visitor accepts the invite, a popup registration window enables the visitor to enter their data.
| |
| − | }}{{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 a sales rep based on the skills, priority, language and queue set in Genesys Predictive Engagement.
| |
| − | # Sales rep and prospect are in conversation. The sales rep has access to full visitor context such as segment, journey information, and outcome score. The sales rep can also see attributes of the visitor such as device type, operating system, location and browser type.
| |
| − | # After the conversation ends, the sales rep agent sets a wrap up code record the outcome of the conversation.
| |
| − | }}
| |
| − | |BusinessLogic=====<span class="mw-headline" id="BL1_.E2.80.93_Customer_Identification">BL1 – Customer Identification</span>====
| |
| − | 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 when explicitly submitted from the web page and can identify the visitor even across devices. If a visitor uses a second device to visit the website the next day and provides a piece of this information, their visit can be associated to previous journeys across devices. When visitor identity cannot be determined, the customer is handled as an anonymous user and all tracked data is attached to them. Once the visitor is identified, all tracking data collected and to be collected is associated to that specific visitor.
| |
| − | ====<span class="mw-headline" id="BL2_.E2.80.93_Persona_and_Outcome_Configuration">BL2 – Segment and Outcome Configuration</span>====
| |
| − | Segments categorize visitors on the website into segments, based on common behavior and attributes. Segments are configured upfront during system provisioning. A segment is made up of two 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 that you want your visitors to perform on your website. As with segments, configure outcomes frome the beginning. Typical outcomes include:
| |
| − | * Proceed to checkout with a shopping cart
| |
| − | * Submit payment
| |
| − | * Download a whitepaper
| |
| − | * 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).
| |
| − | | |
| − | ====<span class="mw-headline" id="BL3_.E2.80.93_Action_Map_Configuration">BL3 – Action Map Configuration</span>====
| |
| − | Action Maps determine how to engage with the website visitor. Within action maps, define the triggers that result in an action to the customer. These triggers include:
| |
| − | * Segment
| |
| − | * User activity
| |
| − | * Outcome score. Typically, a drop-in outcome score for a specific segment can trigger an action.
| |
| − | * Invitation to chat<br />
| |
| − | | |
| − | ====<span class="mw-headline" id="BL4_.E2.80.93_Pacing_Service">BL4 – Estimated Wait Time</span>====
| |
| − | Genesys's patented pacing algorithm automatically predicts sales rep availability based on contact center statistics. If no sales rep is predicted to be available for the requested media type, no offer to engage is sent to the visitor.
| |
| − | | |
| − | | |
| − | <span style="font-size: 16.239999771118164px; font-weight: bold;">BL5 – Customer Invite and Registration Window</span>
| |
| − | | |
| − | | |
| − | Genesys Widgets are used to:
| |
| − | * Invite messages for chat
| |
| − | * Optionally collect visitor contact details
| |
| − | * Engage over chat session booking<br />
| |
| − | |DistributionLogic====<span class="mw-headline" id="Distribution_Logic">Distribution Logic</span>===
| |
| − | <span>The distribution of the interaction is determined by the queue configured in the Altocloud Action Map.</span>
| |
| − | |CustomerInterfaceRequirements=* Used with Genesys Widgets only. Not supported with PureCloud Widget.
| |
| − | |AgentDeskRequirements=N/A
| |
| − | |RealTimeReporting=Genesys Altocloud Analytical Dashboards report:
| |
| − | * Live Now: Live activity on the website.
| |
| − | * Visitor Activity report: See visitor historical activity. Filter by segments and outcomes.<brdata-attributes="" />
| |
| − | * Action Map report: View action map performance numbers for qualified, offered, accepted, rejected, errored and timedout actions.
| |
| − | * PureCloud Analytics real-time dashboards. Include Journey values 'Has Customer Journey' and 'Proactive Chat' columns and filters:
| |
| − | ** Interactions
| |
| − | ** Queue Performance
| |
| − | ** Agent Performance
| |
| − | ** Skills Performance
| |
| − | ** DNIS Performance
| |
| − | ** Wrap-up Performance
| |
| − | ** Agent Wrap Up
| |
| − | * Data Export from real-time views supported for Journey data.
| |
| − | |HistoricalReporting=Genesys Altocloud Analytical Dashboards report:
| |
| − | * Live Now. Live activity on the website.
| |
| − | * Visitor Activity report. See visitor historical activity. Filter by segments and outcomes.
| |
| − | * Action Map Report. View action map performance numbers for qualified, offered, accepted, rejected, errored and timedout action.
| |
| − | |GeneralAssumptions=Customer must use Genesys Widgets. Customer must deploy both Altocloud and Widgets code snippets on their website or web pages.
| |
| − | | |
| − | | |
| − | The Genesys Chat Routing CE18 use case is not used here as it is based on PureCloud Widget, which is not used with Altocloud. However chat routing logic used with Genesys Widgets is identical to CE18 use case.
| |
| − | |SMART_HybridAssumptions={{SMART HybridAssumptions
| |
| − | |Hybrid_Assumption=v 1.0.0
| |
| − | }}
| |
| − | }}
| |
