Include each vector function in a separate vector and link each function with more than one goto vector command.
Design vector commands for maximum delay of answer supervision to keep the service costs low.
Always provide callers with an initial feedback such as ringback.
Before some vector steps, it is a good practice to insert a brief wait step so that vector processing can handle any possible delays that might cause the vector to fail and the call to not be routed. Follow this best practice when programming a vector:
Start all vectors with a wait-time 0 seconds
step. Adding this step helps ensure you will have a touch-tone receiver (TTR) for vector processing.
When using an adjunct routing
step, it is also advise to put a wait-time 0 seconds
step before the adjunct routing
step to provide a pause before routing the call to the adjunct system.
Any time digits are collected from a caller using a collect digits
step, the step should be preceded by a wait-time 0 seconds
step, hearing either ringback or music. Again, this ensures you will have a TTR to collect those digits.
Pay attention to direct agent calls as these calls affect call queuing. BCMS and CMS reports do not count the queue slots occupied by direct agent calls. These calls are not counted in the total queued calls within a split and the calls-queued test condition has no effect on direct agent calls.
For more information, see Avaya Aura® Call Center Elite Feature Reference.
Use the duplicate vdn command to create duplicate VDNs from existing VDNs.
Use the duplicate vector command to create duplicate vectors from existing vectors.