AT&T 555-230-520 manual Routed to Trunk, Routed to VDN, Routed to Split or to Hunt Group

Call Vectoring Commands

Routed to Trunk

Database Item	Report Heading	Notes
OUTFLOWCALLS/	Vector Flow Out
OUTFLOWTIME
	VDN Flow Out
INTERFLOWCALLS	VDN Flow-Interflow
/ INTERFLOWTIME
INTIME	Avg Time In Vector
	Routed to VDN
Database Item	Report Heading	Notes
OUTFLOWCALLS/	Vector Flow Out
OUTFLOWTIME
	VDN Flow Out
INTIME	Avg Time In Vector
INFLOWCALLS	Vector Flow In	new vector
	VDN Flow In	new VDN
Routed to Split or to Hunt Group
Database Item	Report Heading	Notes
CALLSOFFERRED		new split
LOWCALLS/MEDC		no priority/priority
ALLS

Split calls are also shown in the standard reports based on the final disposition of the call.

The presence of the command in a vector enables the calls serviced by the vector to be vector-directed. When such a call is answered by an agent, the call is tracked as ACDCALLS/ANSTIME, and it is reported as ‘‘ACD Calls,’’ ‘‘Split ACD Calls,’’ and ‘‘Avg Speed Ans.’’

A call abandoned after the command routes the call to a station or an attendant is tracked in the VDN tables as ABNCALLS/ABNTIME.

R2 CMS: Adjunct routing attempts are not stored in R2 CMS. Successful adjunct-routed calls are stored in OUTFLOW and FLOWTIME in the Vector and VDN tables. These calls are not shown on standard reports. VECTIME is recorded for the vector and reported as ‘‘Avg Time inVector.’’

A-20Issue 4 September 1995