Avaya ACD: making incoming calls queue sensibly
The ACD is not about making customers wait; it decides who is answered first, who answers, and what happens when the wait grows too long. This page sets out Avaya ACD queues, skill groups, priority and overflow strategy.
What the ACD actually does
In a contact centre the ACD (Automatic Call Distribution) is the layer that distributes calls. It places incoming calls into queues, finds the most suitable available agent according to preset rules, keeps callers waiting when nobody is free, and routes them elsewhere by the overflow rules once the wait exceeds the limit.
Many people treat the ACD and the IVR as one thing. The IVR listens to key presses and triages; the ACD governs how long the queue is and which agent answers. They normally run in series: the IVR establishes what the caller needs, then the call enters the matching queue.
Avaya's queueing capability sits mainly in Aura Contact Center, working alongside call control in Communication Manager.
Four metrics that decide the queueing experience
Service level: X% of calls answered within Y seconds, so 80/20 means 80% of calls answered within 20 seconds. This is the first objective in queue design.
Average wait time: how long customers actually waited. This figure is dragged down by callers who hang up early, so read it together with the abandonment rate.
Abandonment rate: the share of callers who hang up before being answered. A sudden rise usually means the queue is understaffed or the IVR has too many levels.
Average talk time: decides how many calls an agent handles in a day and directly drives scheduling.
How to tune queueing strategy
Skill-group design: split by business (pre-sales, after-sales, complaints), by language or by region. Splitting too finely leaves every queue short-staffed, so three to six main queues is the practical range.
Priority: VIPs, repeat calls after a timeout and ticket call-backs can be given higher priority, but the proportion must be capped or ordinary queues starve.
Overflow and fallback: once a wait exceeds the threshold, route to a standby skill group, a duty mobile or offer a callback, which customers accept far more readily than waiting on the line.
IVR front-end offload: handing repetitive questions such as balance or order status to self-service typically removes 20% to 40% of live-agent volume.
Suggested order of adjustment: use the reports to locate the bottleneck, then change the queue structure, and only then add people.
ACD frequently asked questions
Q: Can we add queueing without touching the existing phone system? A: Yes. SIP trunks connect the existing switch to the new queues, and the numbers stay unchanged.
Q: Customers complain about long waits. Is adding agents the answer? A: Not necessarily. Check first whether the IVR has too many levels, whether skill groups are split too finely, or whether agent states are configured incorrectly.
Q: Can capacity expand automatically at peak? A: A cloud contact centre can scale elastically with concurrency; on-premises deployment depends on licences and trunk capacity, which have to be sized in advance.
Q: Can queue data be exported for performance review? A: Yes. Queue reports, agent states and call details can all be exported, or connected to your own BI.
Queue data not looking good?
Send us your current queue reports and we can help identify whether the problem lies in staffing, routing or IVR structure.

