What Is ACD (Automatic Call Distribution)?

Automatic call distribution is the oldest idea in the contact center and still the one everything else is built around. A call arrives on a number, the system works out which group of people should handle it, places it in a queue if nobody is free, and then gives it to an agent the moment one becomes available. The caller experiences this as a short wait with an announcement. The business experiences it as the difference between a team that answers calls in a defined order and a team where the loudest phone wins.

The distinction that matters is between an ACD and a plain hunt group. A hunt group rings extensions in a configured sequence. It has no memory, no queue and no notion of fairness, so the first extension in the list absorbs most of the volume and there is nothing to report on afterwards. An ACD keeps the waiting calls as a queue, applies a strategy to choose the recipient, and produces a record of what waited how long and who took it.

How Routing Strategies Differ

Every ACD queue carries a strategy, and the choice changes both fairness and speed:

• FIFO. First in, first out. The caller who has waited longest is served next. This is the strategy people assume is in use, and it is the one that keeps the worst individual wait down.
• Round-robin. Calls are handed around the agent group in turn, which spreads volume evenly and stops one agent absorbing the queue because they answer fastest.
• Longest-idle. The call goes to whoever has been available longest. This levels out talk time across a shift rather than levelling out call count.
• Skills-based. The call is matched to an agent attribute, typically language, product or seniority. It gives the best fit at the cost of a smaller pool for each call, which pushes waits up when the matching group is thin.

The Settings That Decide Caller Experience

A queue is more than a strategy. Max wait sets how long a caller may hold before the call is handled another way. Wrap-up seconds give the agent time to finish notes before the next call arrives. An answer target and a breach threshold turn the queue into something measurable. Announcements can tell the caller their position and estimated wait rather than leaving them guessing, and hold audio fills the gap in between. After-hours handling decides what happens to the calls that arrive when nobody is there, which for most businesses is where the quiet losses are.

How DialerBee Handles ACD

In DialerBee, each queue in the inbound contact center picks the next agent by FIFO, round-robin or longest-idle, and carries its own priority so the queue that matters most is served first. Max wait, wrap-up seconds and recording mode belong to the queue rather than the whole tenant, which is how a collections queue and a support queue can behave differently in the same account. Every queue takes an SLA target and the threshold that counts as a breach. FIFO, round-robin and longest-idle routing today; skills-based routing is planned.

Callers can hear their position in the queue and their estimated wait, with music on hold in between, and hold audio is generated by text to speech for your tenant with a voice you preview before it goes live. Inbound numbers live in a DID inventory where each one is routed to a queue, a user, an IVR flow, a campaign or an AI voice agent. Queue depth and queue stats are live on the wallboard, with queue performance and inbound call reports behind them, and a supervisor can listen, whisper, barge or force an agent to log out. Agents handle inbound queues and outbound campaigns from one desktop; automatic blending is planned. All of it is available across 11 languages.

Frequently Asked Questions

What is the difference between ACD and IVR?

An IVR talks to the caller and collects a choice, by keypress or by speech. An ACD takes the call the IVR hands over and decides which agent receives it. They are usually deployed together: the IVR qualifies and segments, the ACD queues and distributes. A small operation can run an ACD with no IVR at all, and a self-service line can run an IVR that never reaches an agent.

What routing strategies does an ACD use?

The common strategies are FIFO, where the longest-waiting caller is served first, round-robin, which spreads calls evenly across the agent group, and longest-idle, which sends the call to whoever has been free the longest. Larger deployments add skills-based routing, which matches the call to an agent attribute such as language or product knowledge.

Does an ACD handle outbound calls?

Not directly. An ACD distributes inbound contacts. Outbound work is paced by a dialer instead. Many platforms let the same agent pool serve both, so an agent moves between an inbound queue and an outbound campaign from one desktop, which is how teams keep seats busy across an uneven day.

What is queue priority in an ACD?

Queue priority decides which queue is served first when several queues are waiting for the same free agent. A collections queue set above a general enquiry queue will take the agent first. Priority is a property of the queue, so it applies to every call that lands in it rather than being decided call by call.

How does an ACD measure whether it is working?

The core measures are average speed of answer, service level against a stated answer target, abandon rate before an agent picks up, and occupancy across the agent group. Queue depth in the moment tells you whether to intervene now; the reports afterwards tell you whether the staffing plan was right.

Related terms: IVR, service level and SLA, average speed of answer, skills-based routing and wallboard.