Overflow Details
This data export field displays the extension number or name of the storm UC/CONTACT treatments that to which calls were directed. This may have been directly, through a transfer, or via an extended configuration (overflow rule)
Note: resulting from matching rules assigned to an ACD queue are not included in this field.
Historical Data Source |
CONTACT Data Records |
Category |
UC |
Channels |
|
Size (bytes) |
532 |
Filter |
None |
Dimension |
None |
Example
This data export report shows two calls.
Rows 1 and 2: An incoming call to an ACD queue call treatment (of extension 407) that was unanswered and then overflowed to a call treatment named 'IT hunt group' (of extension 300). If no extension had been assigned to the hunt group, then 300 would have been replaced with 'IT Hunt Group'.
Row 3: An internal call to a call treatment (of extension 805) for a supervisor listen-in service.
Overflow Details |
|||||
2018-08-06 10:56:45 |
I |
077009004323 |
01614960654 |
407-300 |
IT Hunt Group |
2018-08-02 10:57:28 |
O |
077009004323 |
00156531972e |
407-300 |
IT Hunt Group |
2018-08-06 11:04:02 |
I |
00156527D65C |
805 |
805 |
Listen In Travel |
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 |
|
|
|
EXTERNAL INCOMING CALL (2 legs) |
One or multiple hyphen-separated extensions or names* |
|
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) |
||
One or multiple hyphen-separated extensions or names* |
* The initial destination is displayed first.