Difference between revisions of "CE02/Canonical"
From Genesys Documentation
m (1 revision imported) |
(USC: Updated HLF embed code) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 8: | Line 8: | ||
|PlatformChallenge=When your customers call, they expect you to know who they are. If they are connected to employees who don’t have any information about them or their previous interactions — resulting in unnecessary repetition, effort and time — your customer experience scores suffer. | |PlatformChallenge=When your customers call, they expect you to know who they are. If they are connected to employees who don’t have any information about them or their previous interactions — resulting in unnecessary repetition, effort and time — your customer experience scores suffer. | ||
|PlatformSolution=Create an effortless experience by recognizing a repeat customer and prioritizing a connection to the same agent who previously served them. Offer expected wait times and the convenience of self-service or a call back. Genesys Personalized Routing uses context-based routing to direct calls to the best resource. | |PlatformSolution=Create an effortless experience by recognizing a repeat customer and prioritizing a connection to the same agent who previously served them. Offer expected wait times and the convenience of self-service or a call back. Genesys Personalized Routing uses context-based routing to direct calls to the best resource. | ||
| − | |PainPoints=* Unable to use context to enable a finer granularity in matching the customer to the best agent in the target agent group | + | |PainPoints=*Unable to use context to enable a finer granularity in matching the customer to the best agent in the target agent group |
| − | * Calls with long handle times, with customers having to recap previous interactions | + | *Calls with long handle times, with customers having to recap previous interactions |
| − | * Missed service levels within or across channels | + | *Missed service levels within or across channels |
| − | * Increasing interaction abandonment and repeat contacts | + | *Increasing interaction abandonment and repeat contacts |
|DesiredState=*Offer self-service and call back options | |DesiredState=*Offer self-service and call back options | ||
*Inform customers of expected wait/process times | *Inform customers of expected wait/process times | ||
| − | |HighLevelFlowLucid= | + | |HighLevelFlowLucid=c1ead22e-ae68-47ee-8c0b-780473a93ca8 |
|BuyerPersonas=Head of Contact Center(s), Head of Customer Experience, Head of Operations | |BuyerPersonas=Head of Contact Center(s), Head of Customer Experience, Head of Operations | ||
|QualifyingQuestions=# When you get a repeat call within X (configurable) timeframe, are you able to automatically route the customer to the same agent? | |QualifyingQuestions=# When you get a repeat call within X (configurable) timeframe, are you able to automatically route the customer to the same agent? | ||
| Line 48: | Line 48: | ||
|CanonicalBenefitID=Improved Customer Experience | |CanonicalBenefitID=Improved Customer Experience | ||
|CanonicalBenefit=Recognizing a customer and reducing their effort leads to improved satisfaction scores. | |CanonicalBenefit=Recognizing a customer and reducing their effort leads to improved satisfaction scores. | ||
| + | }} | ||
| + | {{SMART Benefits | ||
| + | |CanonicalBenefitID=Increased Revenue | ||
| + | |CanonicalBenefit=Using value-based routing and prioritization of repeat callers helps you to increase revenue. | ||
}} | }} | ||
{{SMART Benefits | {{SMART Benefits | ||
|CanonicalBenefitID=Reduced Handle Time | |CanonicalBenefitID=Reduced Handle Time | ||
|CanonicalBenefit=Matching a customer with their previous or best equipped agent, with context, reduces handle time. | |CanonicalBenefit=Matching a customer with their previous or best equipped agent, with context, reduces handle time. | ||
| − | |||
| − | |||
| − | |||
| − | |||
}} | }} | ||
Latest revision as of 17:11, March 29, 2021
Contents
Important
This information is shared by CE02 use cases across all offerings.Administration Dashboard
Go back to admin dashboard to create and manage platform-specific use cases in the system:
Titles and Taxonomy
| Main Title | Subtitle | Taxonomy | Product Category | Draft | Published | Edit |
|---|---|---|---|---|---|---|
|
Genesys Personalized Routing |
Apply personalized routing to voice interactions |
Customer Engagement |
Inbound |
No draft |
Canonical Information
Platform Challenge and Solution
Platform Challenge: When your customers call, they expect you to know who they are. If they are connected to employees who don’t have any information about them or their previous interactions — resulting in unnecessary repetition, effort and time — your customer experience scores suffer.
Platform Solution: Create an effortless experience by recognizing a repeat customer and prioritizing a connection to the same agent who previously served them. Offer expected wait times and the convenience of self-service or a call back. Genesys Personalized Routing uses context-based routing to direct calls to the best resource.
Platform Benefits
The following benefits are based on benchmark information captured from Genesys customers and may vary based on industry or lines of business:
| Canonical Benefit | Explanation |
|---|---|
| Improved Customer Experience | Recognizing a customer and reducing their effort leads to improved satisfaction scores. |
| Increased Revenue | Using value-based routing and prioritization of repeat callers helps you to increase revenue. |
| Reduced Handle Time | Matching a customer with their previous or best equipped agent, with context, reduces handle time. |
High Level Flow
High Level Flow Steps
- A customer decides to call the company
- Announcements are played, and customer information is collected
- Check availability of the last agent who served the customer
- If previous agent is not available, expand primary target based on customer context
- Customer hears Expected Wait Time, and/or personalized announcements
- Wait time is long, so customer is queued for a secondary target group
- Customer hears updated Expected Wait Time
- The customer is connected to a skilled agent who has journey history
Data Sheet Image
Canonical Sales Content
Personas
- Head of Contact Center(s)
- Head of Customer Experience
- Head of Operations
Qualifying Questions
- When you get a repeat call within X (configurable) timeframe, are you able to automatically route the customer to the same agent?
- Would it positively impact customer satisfaction scores if repeat callers were matched with the same agent?
- Are you able to assign repeat calls a higher priority?
Pain Points (Business Context)
- Unable to use context to enable a finer granularity in matching the customer to the best agent in the target agent group
- Calls with long handle times, with customers having to recap previous interactions
- Missed service levels within or across channels
- Increasing interaction abandonment and repeat contacts
Desired State - How to Fix It
- Offer self-service and call back options
- Inform customers of expected wait/process times
Comments or questions about this documentation? Contact us for support!