UseCases/Current/GenesysCloud/CE03 - Revision history

Shlandy93: Redirected page to UseCases/Current/GenesysCloud/CE43

2020-10-14T15:21:16Z

Redirected page to UseCases/Current/GenesysCloud/CE43

Shlandy93 at 11:55, September 17, 2020

2020-09-17T11:55:14Z

Shlandy93 at 12:57, August 11, 2020

2020-08-11T12:57:19Z

WikiSysop: Text replacement - "PureCloud" to "Genesys Cloud"

2020-07-15T12:05:26Z

Text replacement - "PureCloud" to "Genesys Cloud"

WikiSysop: Text replacement - "manual=PureCloud" to "manual=GenesysCloud"

2020-07-15T11:32:39Z

Text replacement - "manual=PureCloud" to "manual=GenesysCloud"

WikiSysop: WikiSysop moved page UseCases/Current/PureCloud/CE03 to UseCases/Current/GenesysCloud/CE03: Text replacement - "PureCloud" to "GenesysCloud"

2020-07-15T11:30:54Z

WikiSysop moved page UseCases/Current/PureCloud/CE03 to UseCases/Current/GenesysCloud/CE03: Text replacement - "PureCloud" to "GenesysCloud"

Shlandy93 at 15:10, May 27, 2020

2020-05-27T15:10:47Z

Shlandy93 at 11:14, April 20, 2020

2020-04-20T11:14:35Z

Shlandy93 at 12:42, March 27, 2020

2020-03-27T12:42:07Z

Show changes

Shlandy93 at 12:36, March 27, 2020

2020-03-27T12:36:37Z

Show changes

← Older revision		Revision as of 15:21, October 14, 2020
Line 1:		Line 1:
−	~~{{SMART UseCase~~	+	#REDIRECT [[UseCases/Current/GenesysCloud/CE43]]
−	~~\|SMART_Benefits={{SMART Benefits~~
−	~~\|UCBenefitID=Improved Net Promoter Score~~
−	~~\|UCBenefit=Improve customer satisfaction by announcing wait time and offering callbacks when appropriate~~
−	~~}}{{SMART Benefits~~
−	~~\|UCBenefitID=Reduced Interaction Abandonment~~
−	~~\|UCBenefit=Provide clear wait times and callback options to decrease abandonment~~
−	~~}}{{SMART Benefits~~
−	~~\|UCBenefitID=Reduced Volume of Interactions~~
−	~~\|UCBenefit=Decrease in inbound calls from individual callers repeatedly trying to initiate contact~~
−	~~}}{{SMART Benefits~~
−	~~\|UCBenefitID=Reduced Handle Time~~
−	~~\|UCBenefit=Reduce overall handle time in addition to customer hold time and associated telephony costs~~
−	}}
−	\|UCIntro=Genesys Callback (CE03) will be consolidated into {{Link-SomewhereInThisVersion\|manual=GenesysCloud\|topic=CE43}} and it is set to be decommissioned by end of June 2020. Please use the new use case for new opportunities.
−	\|UCOverview=No one likes to wait on hold. If the system detects an excessive wait time for a caller in a queue, the system offers the caller the option to request a callback. This functional use case enables companies to improve customer experience by improving in-queue treatment ({{#~~mintydocs_link:topic=CE01}}) with configurable wait time announcements and callback offers. When companies enable callbacks within their Genesys environments, benefits can include:~~
−	\|UCSummary=When a customer is waiting to speak to an agent, and the expected wait time to reach an appropriate agent is above a specified threshold, they will be presented with the option to receive a callback. Different treatment can be applied and a different message presented based on the length of the wait. The wait time thresholds can be specified by the business and quickly adjusted if required. Please also see the [~~https:~~//~~help.mypurecloud.com~~/~~articles/callbacks-overview/ Callbacks overview~~].
−	~~\|PainPoints=*Long queue times lead to abandons and missed service levels~~
−
−	*High staffing costs in order to have resources available for peak periods
−	*Unable to obtain view of operational performance through reporting & analytics
−	*Customer dissatisfaction with long waits and lack of options
−
−	~~<br />~~
−	~~\|DesiredState=*When caller requests agent assistance from IVR, the queue times are dynamically checked~~
−	*When queue exceeds threshold set by business, the caller is played a message relaying the current wait time and given callback option
−	*Caller can choose to accept or reject the callback option
−	*When accepted, the callback is registered in the queue
−	*When the callback reaches the top of the queue, it is assigned to an available agent.
−	~~\|MaturityLevel=Consistent~~
−	~~\|SellableItems=Genesys Cloud 2 or greater~~
−	~~\|CloudAssumptionsAdditional_Sales=* This use case is available on Cloud~~
−	~~\|PremiseAssumptions=N/A~~
−	~~\|BusinessImageFlow={{SMART BusinessImageFlow~~
−	~~\|BusinessFlow=(1)~~
−	~~\|BusinessImage=https://www.lucidchart.com/documents/edit/bbaf9a45-8ac4-4644-9ae9-049547b3caf9/0~~
−	~~\|BusinessFlowDescription=1.1 - A customer calls a service line of the company. As described in {{#mintydocs_link:topic=CE01}}<span>, Genesys Cloud transfers the call to a queue.~~
−
−	1.2 - The customer waits for an agent with the requested skills. There are two configurable, messaging-related thresholds: Medium Wait Time and Long Wait Time. If the wait time is below these thresholds, the system transfers the call to the appropriate queue to wait for an agent with the requested skills.
−
−	1.3 - If the wait time is above these thresholds, the system plays the appropriate wait time announcement to the caller. The system may repeat the announcement, depending on the amount of time the call stays in the queue. The announcement is either a generic announcement, or the estimated wait time rounded in minutes.
−
−	~~1.4 - After the announcements, the system offers the option for a callback to the customer.~~
−
−	~~1.5 - If the customer does not accept the callback, the call continues to wait in the queue. If the customer accepts the callback, the system registers the callback.~~
−	~~}}{{SMART BusinessImageFlow~~
−	~~\|BusinessFlow=(2) '''Register Callback'''~~
−	~~\|BusinessImage=https://www.lucidchart.com/documents/edit/8b130009-8a45-42ad-9aae-3fb622b734a6/0~~
−	~~\|BusinessFlowDescription=2.1- Genesys Cloud asks the customer to verify the phone number for the callback.~~
−
−	2.2 - If the phone number is correct, Genesys Cloud registers the callback request in the same queue as the original conversation and ends the call. The callback replaces the original call and maintains the caller's position in the queue.
−
−	~~2.3 - If the phone number is not correct, Genesys Cloud asks the customer to enter an alternate callback number.~~
−
−	~~2.4 - The caller enters the callback number.~~
−
−	2.5 - Genesys Cloud registers the callback request in the same queue as the original conversation and ends the call. The callback replaces the original call and maintains the caller's position in the queue.
−	~~}}{{SMART BusinessImageFlow~~
−	~~\|BusinessFlow=(3) '''Callback'''~~
−	~~\|BusinessImage=https://www.lucidchart.com/documents/edit/3cddc70b-a2c8-41ce-bd7e-06923008f7c2/0~~
−	~~\|BusinessFlowDescription=3.1 - Genesys Cloud assigns the callback interaction to an agent in the queue.~~
−
−	~~3.2 - The agent receives the callback interaction, reviews the information, and manually calls the customer.~~
−
−	~~3.3 - If the customer answers the call, the agent and the customer are connected.~~
−	}}
−	~~\|BusinessLogic=The business can configure the messages played and the wait time thresholds:~~
−
−	*Automated In queue wait time threshold
−	*Wait time playback threshold(s)
−	*In queue waiting prompts could include callback option to customer
−	*Customer can opt in to leave a callback request
−	*Number of times to offer callback option to customers
−
−	~~====<span class="mw-headline" id="Callback_Priority">Callback Priority</span>====~~
−	~~A callback automatically inherits the priority set on the inbound ACD voice call it replaces.~~
−	~~====<span class="mw-headline" id="Callback_Position_in_Queue">Callback Position in Queue</span>====~~
−	~~A callback replaces the original voice conversation in the queue and therefore maintains the customer's position in queue.~~
−	~~===<span class="mw-headline" id="Routing_Logic">Routing Logic</span>===~~
−	~~====<span class="mw-headline" id="Routing_calls_to_agents">Routing calls to agents</span>====~~
−	~~This functionality defined in {{#mintydocs_link:topic=CE01}}.~~
−	~~====<span class="mw-headline" id="Routing_callback_requests_to_agents">Routing callback requests to agents</span>====~~
−	~~When a callback request reaches the top of the queue, Genesys Cloud assigns it to the best-fit agent. That agent initiates the callback to the customer.~~
−	~~\|DistributionLogic=N/A~~
−	~~\|CustomerInterfaceRequirements=N/A~~
−	~~\|AgentDeskRequirements=The agent’s callback interface displays:~~
−	* Type of request
−	* User ID (Optional)
−	* User first name (Optional)
−	* User last name (Optional)
−	* User phone number
−	* Language
−	This use case is in addition to existing inbound voice functionality. Therefore, all agent desktop functionality for inbound voice calls is also available for callbacks. To change some of the information on the agent's callback interface, businesses can modify agent scripts.
−	\|RealTimeReporting=Due to the continuous evolution, the features available in Genesys Cloud rapidly change. Please see the Genesys Cloud Resource Center for latest features at [http://help.mypurecloud.com Genesys Cloud Help]
−
−
−	'''Note:'''<span></span>Callbacks are a media type that users can select on the majority of views and reports.The following are examples of Genesys Cloud Historical and Real-time views that provide relevant insights:
−	* Queue
−	** The Queue Activity view shows real-time queue information. Callbacks are a specific media type.
−	** The Queue Performance Summary and Detail views allow a supervisor to see historical conversations based on media type, including callbacks. Supervisors can filter on skills, languages, DNIS, and so on.
−	** The real-time Queue Activity view and the historical Queue Performance view show outbound calls that agents place to customers.
−	* Agent
−	** The Agent Performance view allows a supervisor to get historical metrics on the number of conversations each agent handles. Because callbacks are a separate media type, supervisors can see how many callbacks agents make and how long an average callback takes. Supervisors can filter on skills, languages, wrap-up codes, and so on.
−	** The Agent Status Summary view provides insight on the availability of specific agents.
−	* Interactions
−	** The Interactions view provides detailed information on both historical and real-time interactions.
−	** It allows supervisors to filter interactions based on metrics including agent names and wrap-up codes.
−	** It allows supervisors to search for interactions by specific media types.
−	* Reports
−	** Genesys Cloud has a full library of canned reports available in PDF and XLSX formats.
−	** Supervisors can filter these reports by dates, users, queues, and so on.
−	** Supervisors can download reports from the Genesys Cloud user interface.
−	** Supervisors can schedule reports to run and download in batch.
−	~~\|HistoricalReporting=Same as Real Time Reporting.~~
−	~~\|DocVersion=v 1.0.3~~
−	~~\|GeneralAssumptions=No integration with third-party systems.~~
−	~~\|CustomerAssumptions=N/A~~
−	~~\|RequiresAll=CE01~~
−	~~\|SMART_PremiseAssumptions={{SMART PremiseAssumptions~~
−	~~\|Premise_Assumption=N/A~~
−	}}
−	~~\|RelatedDocs={{TSSection~~
−	~~\|sectionheading=About Callbacks~~
−	~~\|description=Learn more about callbacks and review frequently asked questions.~~
−	~~\|relatedarticles=[https://help.mypurecloud.com/articles/about-callbacks/ About callbacks~~]
−	}}
−	}}

@@ Line 15: / Line 15: @@
 |UCIntro=Genesys Callback (CE03) will be consolidated into {{Link-SomewhereInThisVersion|manual=GenesysCloud|topic=CE43}} and it is set to be decommissioned by end of June 2020.  Please use the new use case for new opportunities.
 |UCOverview=No one likes to wait on hold. If the system detects an excessive wait time for a caller in a queue, the system offers the caller the option to request a callback. This functional use case enables companies to improve customer experience by improving in-queue treatment ({{#mintydocs_link:topic=CE01}}) with configurable wait time announcements and callback offers. When companies enable callbacks within their Genesys environments, benefits can include:
-|UCSummary=When a customer is waiting to speak to an agent, and the expected wait time to reach an appropriate agent is above a specified threshold, they will be presented with the option to receive a callback. Different treatment can be applied and a different message presented based on the length of the wait. The wait time thresholds can be specified by the business and quickly adjusted if required.
+|UCSummary=When a customer is waiting to speak to an agent, and the expected wait time to reach an appropriate agent is above a specified threshold, they will be presented with the option to receive a callback. Different treatment can be applied and a different message presented based on the length of the wait. The wait time thresholds can be specified by the business and quickly adjusted if required. Please also see the [https://help.mypurecloud.com/articles/callbacks-overview/ Callbacks overview].
 |PainPoints=*Long queue times lead to abandons and missed service levels
@@ Line 113: / Line 113: @@
 ** Supervisors can schedule reports to run and download in batch.
 |HistoricalReporting=Same as Real Time Reporting.
 |GeneralAssumptions=No integration with third-party systems.
 |CustomerAssumptions=N/A
@@ Line 119: / Line 120: @@
 |Premise_Assumption=N/A
 }}
-|DocVersion=v 1.0.2
+|RelatedDocs={{TSSection
 }}

@@ Line 1: / Line 1: @@
 {{SMART UseCase
 |SMART_Benefits={{SMART Benefits
 |UCBenefitID=Improved Net Promoter Score
@@ Line 18: / Line 15: @@
 |UCIntro=Genesys Callback (CE03) will be consolidated into {{Link-SomewhereInThisVersion|manual=GenesysCloud|topic=CE43}} and it is set to be decommissioned by end of June 2020.  Please use the new use case for new opportunities.
 |UCOverview=No one likes to wait on hold. If the system detects an excessive wait time for a caller in a queue, the system offers the caller the option to request a callback. This functional use case enables companies to improve customer experience by improving in-queue treatment ({{#mintydocs_link:topic=CE01}}) with configurable wait time announcements and callback offers. When companies enable callbacks within their Genesys environments, benefits can include:
-|UCSummary=When a customer is waiting to speak to an agent, and the expected wait time to reach an appropriate agent is above a specified threshold, they will be presented with the option to receive a callback - either as soon as possible or at a scheduled future time. Different treatment can be applied and a different message presented based on the length of the wait. The wait time thresholds can be specified by the business and quickly adjusted if required.
+|UCSummary=When a customer is waiting to speak to an agent, and the expected wait time to reach an appropriate agent is above a specified threshold, they will be presented with the option to receive a callback. Different treatment can be applied and a different message presented based on the length of the wait. The wait time thresholds can be specified by the business and quickly adjusted if required.
 |PainPoints=*Long queue times lead to abandons and missed service levels
@@ Line 32: / Line 28: @@
 *When accepted, the callback is registered in the queue
 *When the callback reaches the top of the queue, it is assigned to an available agent.
 |MaturityLevel=Consistent
 |SellableItems=Genesys Cloud 2 or greater
 |CloudAssumptionsAdditional_Sales=* This use case is available on Cloud
 |PremiseAssumptions=N/A
 |BusinessImageFlow={{SMART BusinessImageFlow
 |BusinessImage=https://www.lucidchart.com/documents/edit/bbaf9a45-8ac4-4644-9ae9-049547b3caf9/0
 |BusinessFlowDescription=1.1 - A customer calls a service line of the company. As described in {{#mintydocs_link:topic=CE01}}<span>, Genesys Cloud transfers the call to a queue.
@@ Line 50: / Line 43: @@
 .4 - After the announcements, the system offers the option for a callback to the customer.
-.5 - If the customer does not accept the callback, the call continues to wait in the queue. If the customer accepts the callback, the system registers the callback.</span>
+.5 - If the customer does not accept the callback, the call continues to wait in the queue. If the customer accepts the callback, the system registers the callback.
 }}{{SMART BusinessImageFlow
-|BusinessFlow='''Register Callback'''
+|BusinessFlow=(2) '''Register Callback'''
 |BusinessImage=https://www.lucidchart.com/documents/edit/8b130009-8a45-42ad-9aae-3fb622b734a6/0
 |BusinessFlowDescription=2.1- Genesys Cloud asks the customer to verify the phone number for the callback.
@@ Line 64: / Line 57: @@
 .5 - Genesys Cloud registers the callback request in the same queue as the original conversation and ends the call. The callback replaces the original call and maintains the caller's position in the queue.
 }}{{SMART BusinessImageFlow
-|BusinessFlow='''Callback'''
+|BusinessFlow=(3) '''Callback'''
 |BusinessImage=https://www.lucidchart.com/documents/edit/3cddc70b-a2c8-41ce-bd7e-06923008f7c2/0
 |BusinessFlowDescription=3.1 - Genesys Cloud assigns the callback interaction to an agent in the queue.
@@ Line 73: / Line 66: @@
 }}
 |BusinessLogic=The business can configure the messages played and the wait time thresholds:
 * Automated In queue wait time threshold
-* Wait time playback threshold(s)
+*Automated In queue wait time threshold
-* In queue waiting prompts could include callback option to customer
+*Wait time playback threshold(s)
-* Customer can opt in to leave a callback request
+*In queue waiting prompts could include callback option to customer
-* Number of times to offer callback option to customers
+*Customer can opt in to leave a callback request
 ====<span class="mw-headline" id="Callback_Priority">Callback Priority</span>====
@@ Line 88: / Line 82: @@
 ====<span class="mw-headline" id="Routing_callback_requests_to_agents">Routing callback requests to agents</span>====
 When a callback request reaches the top of the queue, Genesys Cloud assigns it to the best-fit agent. That agent initiates the callback to the customer.
 |DistributionLogic=N/A
 |CustomerInterfaceRequirements=N/A
@@ Line 120: / Line 113: @@
 ** Supervisors can schedule reports to run and download in batch.
 |HistoricalReporting=Same as Real Time Reporting.
 |GeneralAssumptions=No integration with third-party systems.
 |CustomerAssumptions=N/A
@@ Line 127: / Line 119: @@
 |Premise_Assumption=N/A
 }}
-|PremiseAssumptionsAdditional=
+|DocVersion=v 1.0.2
 }}

@@ Line 35: / Line 35: @@
 |QualifyingQuestions=
 |MaturityLevel=Consistent
-|SellableItems=PureCloud 2 or greater
+|SellableItems=Genesys Cloud 2 or greater
 |CloudAssumptions=
 |CloudAssumptionsAdditional_Sales=* This use case is available on Cloud
@@ Line 42: / Line 42: @@
 |BusinessImageFlow={{SMART BusinessImageFlow
 |BusinessImage=https://www.lucidchart.com/documents/edit/bbaf9a45-8ac4-4644-9ae9-049547b3caf9/0
-|BusinessFlowDescription=1.1 - A customer calls a service line of the company. As described in {{#mintydocs_link:topic=CE01}}<span>, PureCloud transfers the call to a queue.
+|BusinessFlowDescription=1.1 - A customer calls a service line of the company. As described in {{#mintydocs_link:topic=CE01}}<span>, Genesys Cloud transfers the call to a queue.
 .2 - The customer waits for an agent with the requested skills. There are two configurable, messaging-related thresholds: Medium Wait Time and Long Wait Time. If the wait time is below these thresholds, the system transfers the call to the appropriate queue to wait for an agent with the requested skills.
@@ Line 54: / Line 54: @@
 |BusinessFlow='''Register Callback'''
 |BusinessImage=https://www.lucidchart.com/documents/edit/8b130009-8a45-42ad-9aae-3fb622b734a6/0
-|BusinessFlowDescription=2.1- PureCloud asks the customer to verify the phone number for the callback.
+|BusinessFlowDescription=2.1- Genesys Cloud asks the customer to verify the phone number for the callback.
-.2 - If the phone number is correct, PureCloud registers the callback request in the same queue as the original conversation and ends the call. The callback replaces the original call and maintains the caller's position in the queue.
+.2 - If the phone number is correct, Genesys Cloud registers the callback request in the same queue as the original conversation and ends the call. The callback replaces the original call and maintains the caller's position in the queue.
-.3 - If the phone number is not correct, PureCloud asks the customer to enter an alternate callback number.
+.3 - If the phone number is not correct, Genesys Cloud asks the customer to enter an alternate callback number.
 .4 - The caller enters the callback number.
-.5 - PureCloud registers the callback request in the same queue as the original conversation and ends the call. The callback replaces the original call and maintains the caller's position in the queue.
+.5 - Genesys Cloud registers the callback request in the same queue as the original conversation and ends the call. The callback replaces the original call and maintains the caller's position in the queue.
 }}{{SMART BusinessImageFlow
 |BusinessFlow='''Callback'''
 |BusinessImage=https://www.lucidchart.com/documents/edit/3cddc70b-a2c8-41ce-bd7e-06923008f7c2/0
-|BusinessFlowDescription=3.1 - PureCloud assigns the callback interaction to an agent in the queue.
+|BusinessFlowDescription=3.1 - Genesys Cloud assigns the callback interaction to an agent in the queue.
 .2 - The agent receives the callback interaction, reviews the information, and manually calls the customer.
@@ Line 87: / Line 87: @@
 This functionality defined in  {{#mintydocs_link:topic=CE01}}.
 ====<span class="mw-headline" id="Routing_callback_requests_to_agents">Routing callback requests to agents</span>====
-When a callback request reaches the top of the queue, PureCloud assigns it to the best-fit agent. That agent initiates the callback to the customer.
+When a callback request reaches the top of the queue, Genesys Cloud assigns it to the best-fit agent. That agent initiates the callback to the customer.
 |DistributionImageFlow=
 |DistributionLogic=N/A
@@ Line 99: / Line 99: @@
 * Language
 This use case is in addition to existing inbound voice functionality. Therefore, all agent desktop functionality for inbound voice calls is also available for callbacks. To change some of the information on the agent's callback interface, businesses can modify agent scripts.
-|RealTimeReporting=Due to the continuous evolution, the features available in PureCloud rapidly change. Please see the PureCloud Resource Center for latest features at [http://help.mypurecloud.com PureCloud Help]
+|RealTimeReporting=Due to the continuous evolution, the features available in Genesys Cloud rapidly change. Please see the Genesys Cloud Resource Center for latest features at [http://help.mypurecloud.com Genesys Cloud Help]
-'''Note:'''<span></span>Callbacks are a media type that users can select on the majority of views and reports.The following are examples of PureCloud Historical and Real-time views that provide relevant insights:
+'''Note:'''<span></span>Callbacks are a media type that users can select on the majority of views and reports.The following are examples of Genesys Cloud Historical and Real-time views that provide relevant insights:
 * Queue
 ** The Queue Activity view shows real-time queue information. Callbacks are a specific media type.
@@ Line 115: / Line 115: @@
 ** It allows supervisors to search for interactions by specific media types.
 * Reports
-** PureCloud has a full library of canned reports available in PDF and XLSX formats.
+** Genesys Cloud has a full library of canned reports available in PDF and XLSX formats.
 ** Supervisors can filter these reports by dates, users, queues, and so on.
-** Supervisors can download reports from the PureCloud user interface.
+** Supervisors can download reports from the Genesys Cloud user interface.
 ** Supervisors can schedule reports to run and download in batch.
 |HistoricalReporting=Same as Real Time Reporting.

@@ Line 16: / Line 16: @@
 |UCBenefit=Reduce overall handle time in addition to customer hold time and associated telephony costs
 }}
-|UCIntro=Genesys Callback (CE03) will be consolidated into {{Link-SomewhereInThisVersion|manual=PureCloud|topic=CE43}} and it is set to be decommissioned by end of June 2020.  Please use the new use case for new opportunities.
+|UCIntro=Genesys Callback (CE03) will be consolidated into {{Link-SomewhereInThisVersion|manual=GenesysCloud|topic=CE43}} and it is set to be decommissioned by end of June 2020.  Please use the new use case for new opportunities.
 |UCOverview=No one likes to wait on hold. If the system detects an excessive wait time for a caller in a queue, the system offers the caller the option to request a callback. This functional use case enables companies to improve customer experience by improving in-queue treatment ({{#mintydocs_link:topic=CE01}}) with configurable wait time announcements and callback offers. When companies enable callbacks within their Genesys environments, benefits can include:
 |UCSummary=When a customer is waiting to speak to an agent, and the expected wait time to reach an appropriate agent is above a specified threshold, they will be presented with the option to receive a callback - either as soon as possible or at a scheduled future time. Different treatment can be applied and a different message presented based on the length of the wait. The wait time thresholds can be specified by the business and quickly adjusted if required.

← Older revision	Revision as of 11:30, July 15, 2020
(No difference)