Jump to: navigation, search
(Created target blank page For Version: PSAAS:Public)
 
(Update with the copy of version: draft)
Line 1: Line 1:
−
<!-- Creation of the target page -->
+
= Callback Scenarios =
 +
<font color="#B24DE7">'''Corinne's Note:''' This page includes some content that is commented out.</font>
 +
<!-- This page should eventually include:'
 +
* ''In-Queue Callback: description of standard flow, end-to-end, with key logic of what Designer module does, link to Callback V2 module (text from CE03 use case might be helpful)''
 +
* ''Mobile/Web Callback''
 +
** ''Using the Callback APIs''
 +
** ''Genesys Widgets''
 +
* ''Click-To-Call-In'' -->
 +
 
 +
It does not matter how a callback originates, the voice interaction is always converted to a virtual call and added to the queue where it is monitored so the system can provide information &ndash; such as the Estimated Wait Time (EWT) for the queue &ndash; to future callers.
 +
 
 +
This page describes the callback scenarios that Genesys supports with the Callback application.
 +
 
 +
===Immediate Callbacks===
 +
An ''Immediate'' callback is a callback that is set in motion when your customer (an ''end user'') makes a request to be called back as soon as an agent who can provide assisted service becomes available. A customer can request an Immediate callback in the following ways:
 +
* While the customer is in-queue on an IVR:
 +
** A customer's call arrives and the caller is offered Immediate callback. If the caller accepts, he or she confirms the phone number for the callback.
 +
* Through an API call; in other words, the customer makes the request from a mobile app or website:
 +
** A customer is using your company's or organization's mobile app or website and encounters a situation where he or she requires assisted service by voice. The customer taps or clicks a button to request a callback, confirms or provides the number at which he or she would like to receive the call, and receives a confirmation message that the request was received.
 +
** Because user/context data might be attached to the API request for a callback, key components of the customer's app or web journey can be preserved for agent or reporting use.
 +
<!-- * Using a Genesys Widget for Callback:
 +
** Similar to integrating a company's or organization's Web site with our API directly, using the Genesys Callback Widget on a Web site allows for a reduced time to deployment and less impact on developer resources. -->
 +
 
 +
No matter how the immediate callback is requested, when an agent who satisfies the required skill expression is ready, then the customer is called and the call is routed to the agent.
 +
 
 +
===Scheduled Callbacks===
 +
A ''Scheduled'' callback is a callback that is set in motion when your customer (an end user) makes a request to be called back in the future, at an approximate time that works for the customer's schedule. A customer can request a Scheduled callback in the following ways:
 +
* While in-queue on an IVR:
 +
** A customer's call arrives and the caller is offered the option to schedule a callback for some time in the future. If the caller accepts, he or she confirms the phone number for the callback and is prompted to input the time at which he or she would like to receive it. Using the caller's requested time, the system searches for the closest-matching available time to connect with an agent.
 +
* Through an API call (from a mobile app or website):
 +
** A customer is using your company's or organization's mobile app or website and encounters a situation where he or she requires assisted service by voice. The customer taps or clicks a button to request a callback, confirms or provides the number at which he or she would like to receive the call, interacts with a date/time picker to search for availability, and receives a confirmation message that the request was received.
 +
** Because user/context data might be attached to the API request for a callback, key components of the customer's app or web journey can be preserved for agent or reporting use.
 +
<!-- * Through the Genesys Widget for Callback:
 +
** Similar to integrating a company's or organization's Web site with our API directly, using the Genesys Callback Widget on a Web site allows for a reduced time to deployment and less impact on developer resources. -->
 +
 
 +
No matter how the scheduled callback is requested, if an agent who has the required skill set is ready at the specified time, then the customer is called and the call is routed to the agent.
 +
 
 +
<!--
 +
<font color="#B24DE7">'''Corinne's Note:''' The following was original content; keeping for reference, especially since Click-to-Call-In is not yet implemented.</font>
 +
 
 +
The following scenarios describe sample call flows for immediate and scheduled callbacks:
 +
*Immediate callbacks
 +
** A customer's call arrives and the caller is offered immediate (or in-queue) Callback. If the caller accepts, he or she confirms the phone number of the Callback. The voice interaction is converted to a virtual call and added to the queue where it will be monitored to provide statistics, such as the Estimated Wait Time (EWT).
 +
** When an agent that satisfies the required skill expression is ready, the customer is called and the call is routed to the agent.
 +
* Scheduled callbacks
 +
** A customer's call arrives and the caller is offered a scheduled Callback. If the caller accepts, he or she confirms the phone number of the Callback, along with the date and time of the Callback.
 +
** At the scheduled date, the customer is called and the call is routed to an agent.
 +
* <font color="fuchsia">Click-to-Call-In</font>
 +
** <font color="fuchsia">A customer initiates a Click-To-Call-In request using an app or a website to retrieve the inbound call instructions such as the number to dial and an optional pin.</font>
 +
** <font color="fuchsia">The system responds with a phone number and an optional verification code.</font>
 +
** <font color="fuchsia">The customer calls in and optionally enters the verification code on the call.</font>
 +
**  <font color="fuchsia">After the customer is matched to the previously-initiated session, the call is routed to an agent.</font>
 +
**: {{NoteFormat|To implement this scenario, you need to use the corresponding API to initiate the Click-To-Call-In request. }}
 +
-->
 +
 
 +
[[Category:V:PSAAS:Public]]

Revision as of 18:55, April 17, 2019

Callback Scenarios

Corinne's Note: This page includes some content that is commented out.

It does not matter how a callback originates, the voice interaction is always converted to a virtual call and added to the queue where it is monitored so the system can provide information – such as the Estimated Wait Time (EWT) for the queue – to future callers.

This page describes the callback scenarios that Genesys supports with the Callback application.

Immediate Callbacks

An Immediate callback is a callback that is set in motion when your customer (an end user) makes a request to be called back as soon as an agent who can provide assisted service becomes available. A customer can request an Immediate callback in the following ways:

  • While the customer is in-queue on an IVR:
    • A customer's call arrives and the caller is offered Immediate callback. If the caller accepts, he or she confirms the phone number for the callback.
  • Through an API call; in other words, the customer makes the request from a mobile app or website:
    • A customer is using your company's or organization's mobile app or website and encounters a situation where he or she requires assisted service by voice. The customer taps or clicks a button to request a callback, confirms or provides the number at which he or she would like to receive the call, and receives a confirmation message that the request was received.
    • Because user/context data might be attached to the API request for a callback, key components of the customer's app or web journey can be preserved for agent or reporting use.

No matter how the immediate callback is requested, when an agent who satisfies the required skill expression is ready, then the customer is called and the call is routed to the agent.

Scheduled Callbacks

A Scheduled callback is a callback that is set in motion when your customer (an end user) makes a request to be called back in the future, at an approximate time that works for the customer's schedule. A customer can request a Scheduled callback in the following ways:

  • While in-queue on an IVR:
    • A customer's call arrives and the caller is offered the option to schedule a callback for some time in the future. If the caller accepts, he or she confirms the phone number for the callback and is prompted to input the time at which he or she would like to receive it. Using the caller's requested time, the system searches for the closest-matching available time to connect with an agent.
  • Through an API call (from a mobile app or website):
    • A customer is using your company's or organization's mobile app or website and encounters a situation where he or she requires assisted service by voice. The customer taps or clicks a button to request a callback, confirms or provides the number at which he or she would like to receive the call, interacts with a date/time picker to search for availability, and receives a confirmation message that the request was received.
    • Because user/context data might be attached to the API request for a callback, key components of the customer's app or web journey can be preserved for agent or reporting use.

No matter how the scheduled callback is requested, if an agent who has the required skill set is ready at the specified time, then the customer is called and the call is routed to the agent.

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