| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Panel | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
Setting up a callback enables the caller to hang up their phone rather than waiting for an agent to answer their existing call. When the caller hangs up their phone, NewVoiceMedia does not count the call as abandoned. When an appropriate agent becomes available to handle the call, NewVoiceMedia initiates an outbound call from that agent to the caller. NewVoiceMedia changes the agent's state to Busy Callback.
| Info |
|---|
When the caller hangs up their phone, if NewVoiceMedia has set up a callback, the call is not considered to be abandoned. |
By default, NewVoiceMedia makes the callback to the original CLID.
...
Alternatively, you can configure your interaction plan to overwrite the callback number. For example, you might request that the caller provides an alternative number and use that for the callback. For information about overwriting the callback number, see Setting up queued callbacks.
By default, NewVoiceMedia maintains both the caller's original waiting time and all skills, agreements, and data sources associated with the call. NewVoiceMedia initiates the callback, therefore, at approximately the same time that the original call would have been answered. NewVoiceMedia routes the call to the same queue as the original call.
...
Alternatively, you can also configure your interaction plan
...
such that NewVoiceMedia routes the original call or the callback call through applets that change information associated with the call—skills, data sources, and so on. In such an interaction plan, NewVoiceMedia takes these changes into account when routing the callback. Such changes may result in NewVoiceMedia initiating the callback earlier or later than the original call would have been answered.
...
For information about using a callback initial applet to change associated skills, and so on, see Setting up queued callbacks.
If the agent doesn't answer the callback, the callback automatically returns to the queue.
For information about configuring queued callbacks, see Setting up queued callbacks.
Limitations of queued callbacks
Queued callbacks are not supported in Real Time or Stats and Reports. To report on queued callbacks, you can use Dashboards; the latest Advanced Reporting and Statistics package in Salesforce, which uses the new Stats API; or the Stats API.
If you use Conversation Analyzer, you cannot currently use the queued callbacks feature if you need or want to report on queued callbacks. Conversation Analyzer does not yet fully support the new Stats API which is required when reporting on queued callbacks.
Queued callbacks and Dashboards
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Filter or group the data in your widget by media type to differentiate between live calls and queued callbacks.
For information about filtering or grouping data by media type in your widget to show queued callbacks, see Configuring a widget for queued callbacks.
Queued callbacks and Advanced Reporting and Statistics
If you use the latest Advanced Reporting and Statistics package in Salesforce, which uses the new Stats API, you can search and view queued callback activity. You can connect the callback with the original inbound call, and the subsequent outbound call. For information about using Advanced Reporting and Statistics in Salesforce, see Advanced Reporting and Statistics in Salesforce.
Queued callbacks and Stats API
If you use the Stats API to track NewVoiceMedia activity, you can use an interaction's conversationGuid parameter to connect the original inbound call, the callback, and the outbound call. For information about using the Stats API, see NewVoiceMedia Developer Portal.