Vector exception tracking starts when a call enters the vector and continues until the call connects to an agent, is abandoned, or is routed to another destination. Vector exceptions can help you identify problems in the following areas:
The amount of time that a call waits in a vector.
The number of calls that are abandoned, disconnected, or receive a forced busy signal while in the vector.
Routing failures.