Call Vectoring Commands
A-64 Issue 4 September 1995
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, a nd it i s repo rted as ‘‘A C D Calls,’’ ‘ ‘Split
ACD Calls,’’ and ‘‘Avg Sp eed Ans.’ ’
Finally, if the com ma n d directs a call to a split (skill), the BACKUPCALLS
database item i s incremented, and the call is reported as ‘‘Calls Ans in Backup’’
and ‘‘Calls Handled/Backup.’’ The ‘‘Calls Ans in Main’’ report item is calculated
by using the algorithm ACDCALLS - BACKUPCALLS.
A call abandoned after the command routes the call to a station or to an
attendant is tracked as ABNCALLS/ABNTIME for the me ssagi n g split (skill) a nd
in the VDN/vector tables.
R2 CMS: Calls that go to a messaging split (skill) are tracked as OUTFLOW in
the split (skill), vector, an d VDN tables. The messaging split (skill) also receives
an INFLOW. The calls are shown as ‘‘Flow Out’’ and ‘‘Flow In’’ in stan dard split
(skill) reports. VECTIME is recorded for the vector and reported as ‘‘Avg Time in
Vector.’’
BCMS Interactions
A call advanced to another position via the command is tracked as an ‘‘outflow’’
in the VDN Report.