Transfer Queue ID
This data export field displays the unique storm-generated numeric identifier for the queue to which a call was transferred. It is useful for distinguishing between two queues that have the same name.
Historical Data Source |
CONTACT Data Records |
Category |
CONTACT |
Channels |
|
Size (bytes) |
4 |
Filter |
None |
Dimension |
None |
Example
This data export report shows an incoming call, which was answered by an agent and then transferred to two queues. The first was to 'Cust Service' queue (7916), and then to the 'General Hols' queue (7915).
The first row (inbound leg) reports the last transfer queue. Each subsequent outbound leg to an agent reports the queue to which the call was transferred up to that point in the call. Note that the last two transfers were not to queues.
Transfer Queue ID |
||||
2018-08-02 16:30:19 |
I |
01614960654 |
General Hols |
7915 |
2018-08-02 16:30:24 |
O |
iPath_129_cmilliband |
Cust Service |
7916 |
2018-08-02 16:31:20 |
O |
00156527D65C |
General Hols |
7915 |
2018-08-02 16:32:33 |
O |
001565192de5 |
||
2018-08-02 16:33:40 |
O |
00156531972e |
||
2018-08-02 16:34:45 |
O |
020794607654 |
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 |
|
|
The last transfer queue |
EXTERNAL INCOMING CALL (2 legs) |
|
|
OUTGOING CALL dialled directly from deskphone or storm DTA Web iPath (1st leg) |
|
|
or 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) |
||
|