Queue Callback Requested?
This data export field indicates whether a callback was requested by the caller.
Historical Data Source |
CONTACT Data Records |
Category |
CONTACT |
Channels |
|
Size (bytes) |
1 |
Filter |
Queue Callback Requested? |
Dimension |
None |
Possible Values
One of the following values is written to a record (communication leg):
Value |
Description |
1 |
Callback requested |
0 |
Callback NOT requested |
Example
This data export report shows an incoming call where a caller requested a callback after waiting in a queue for 3 minutes, 28 seconds. The request is reported on the inbound leg.
Queue Callback Requested? |
||||||
2018-06-14 14:02:42 |
I |
07700900432 |
01614960654 |
General Hols |
3:28 |
1 |
2018-06-14 14:10:13 |
O |
2007 |
001565192de5 |
General Hols |
0 |
0 |
2018-06-14 14:10:28 |
O |
01344304344 |
07700900432 |
General Hols |
0 |
0 |
Detail
The data export field populates the inbound (I) and outbound (O) legs in interaction scenarios as illustrated below. See also, Communication Legs.
|
External |
storm |
storm user |
|
Deskphone LOG IN and LOG OUT |
Always 0 |
|
|
EXTERNAL INCOMING CALL (1 leg) |
|
OUTGOING CALL dialled directly from deskphone or storm DTA Web iPath (1st leg) |
|
|
or OUTGOING CALL initiated from the agent desktop (DTA) (1st leg) |
|
|
External |
storm |
storm user |
OUTGOING CALL initiated from the agent desktop (DTA) (1st leg) |
Always 0 |
||
Always 0 |
|
Transfer leg (3rd and subsequent legs) |
||
Always 0 |
Note: values of 0 are written to all communication legs of non-voice interactions.
Filter
Select one of the following filters:
Filter |
Equates to |
True |
Field value of 1 |
False |
Field value of 0 |