Original Callback Time
This data export field applies to a callback call in an OUTBOUND campaign and displays the date and time at which the callback was originally scheduled.
A scheduled callback time may since have been revised manually or missed. There are a number of reasons for a scheduled callback being missed, the most common being that a record that was queued at the scheduled time was not processed straight away because no agent was available.
|
Historical Data Source |
CONTACT Data Records |
|
Category |
OUTBOUND |
|
Channels |
|
|
Size (bytes) |
8 |
|
Filter |
None |
|
Dimension |
None |
Example
This data export report show a live-agent OUTBOUND campaign.
Rows 1 and 2: The outbound call to the contact where the agent scheduled a callback in 5 minutes (value not shown).
Rows 3 and 4: The callback.
|
Original Callback Time |
|||||
|
2018-10-19 16:28:22 |
O |
00156527D65C |
Adam Carter |
|
|
|
2018-10-19 16:28:34 |
O |
07700900439 |
|
|
|
|
2018-10-19 16:35:39 |
O |
00156527D65C |
Adam Carter |
|
|
|
2018-10-19 16:35:49 |
O |
07700900439 |
Adam Carter |
2018-10-19 16:34:29 |
Detail
Original Outbound Call
The data export field does not populate any calls legs in the original outbound call. See also, Communication Legs.
|
|
External |
storm |
storm user |
|
|
Deskphone LOG IN and LOG OUT |
|
|
|
OUTGOING CALL initiated from the agent desktop (DTA) (1st leg) |
|
|
|
Initial called party leg (2nd leg) |
|||
|
|
|
|
TRANSFER of an INCOMING or OUTGOING CALL Transfer leg (3rd and subsequent legs) |
||
|
|
Callback
The data export field populates the outbound (O) legs in the callback. See also, Communication Legs.
|
|
External |
storm |
storm user |
|
|
OUTGOING CALL initiated from the agent desktop (DTA) (1st leg) |
|
|
|
Initial called party leg (2nd leg) |
|||
|
|
|
|
TRANSFER of an INCOMING or OUTGOING CALL Transfer leg (3rd and subsequent legs) |
||
|
|
