Agent Completion Code
This data export field displays the completion code selected by an agent.
|
Historical Data Source |
CONTACT Data Records |
|
Category |
CONTACT |
|
Channels |
|
|
Size (bytes) |
512 |
|
Filter |
Agent Completion Code |
|
Dimension |
None |
Example
This data export report shows an incoming call, which was answered by agent Craig and then transferred twice, first to Stephen and then to Baz. Baz selected a completion code from a 3-tier completion code form.
|
|
|
Agent Completion Code |
|||
|
2018-09-25 12:01:56 |
I |
07700900432 |
01614960654 |
|
|
|
2018-09-25 12:01:56 |
O |
07700900432 |
iPath_129_cmilliband |
Craig Milliband |
Enquiry - could not help |
|
2018-09-25 12:01:56 |
O |
07700900432 |
001565192de5 |
Stephen Dodd |
Other |
|
2018-09-25 12:01:56 |
O |
07700900432 |
00156527D65C |
Baz Parsons |
Escalation; Open; Refund |
Detail
The data export field populates the inbound (I) and outbound (O) legs in interaction scenarios as illustrated below. See also, Communication Legs.
A value of 1 indicates that an internal transfer was performed.
|
|
External |
storm |
storm user |
|
|
Deskphone LOG IN and LOG OUT |
|
|
|
|
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) |
||
|
|
Filter
Filter by using any of the following relational operators on your chosen value(s):
|
Equal to |
Greater than |
Less than |
|
Not equal to |
Greater than or equal to |
Less than or equal to |