Adjunct routing attempts are stored in the ADJATTEMPTS database item and are reported as Adjunct Routing Attempts in the standard reports. If the call is queued to a split/skill when the adjunct routing link command is encountered, the step is skipped and no messages are sent to Call Management System (CMS). The adjunct routing attempts are not reported for such calls.

When the server successfully executes a routing response from the adjunct, the success action is tracked in the ADJROUTED and ADJROUTTIME database items and is shown as Adjunct Routing Completions in the standard reports.

Additional tracking of the adjunct routing link command is based on the destination successfully routed-to and varies as follows.

Routed to station or attendant
Database item	Report heading	Notes
OUTFLOWCALLS/ OUTFLOWTIME	Vector flow out
INTIME	Average time in vector
CONNECTCALLS/ CONNECTTIME	Other calls connect	Answered calls on R5

Routed to trunk
Database item	Report heading	Notes
OUTFLOWCALLS/ OUTFLOWTIME	Vector flow out VDN flow out
INTERFLOWCALLS/ INTERFLOWTIME	VDN flow-interflow
INTIME	Average time in vector

Routed to Vector Directory Number (VDN)
Database item	Report heading	Notes
OUTFLOWCALLS/ OUTFLOWTIME	Vector flow out VDN flow out
INTIME	Average time in vector
INFLOWCALLS	Vector flow in VDN flow in	New vector new VDN

Routed to split or hunt group
Database item	Report heading	Notes
CALLSOFFERRED		New split
LOWCALLS/MEDCALLS		No priority/priority

The standard reports display information about split/skill calls based on the final disposition of the call. A calls that is processed by vectors is vector-directed when the adjunct routing link command is in a vector. When such a call is answered by an agent, the call is tracked as ACDCALLS/ANSTIME and is reported as ACD calls, split/skill ACD calls, and the Average Speed of Answer (ASA). A call that is abandoned after the command routes the call to a station or an attendant is tracked in the VDN tables as ABNCALLS/ABNTIME.