Automatic call distribution (ACD)

What is automatic call distribution?

Automatic call distribution is a telephony system that routes inbound calls to agents based on a set of pre-configured rules, rather than sending every call to whoever happens to be free first. An ACD typically works alongside an IVR system, which gathers information from the caller, and then applies routing logic to determine which agent or queue should handle the call.

The specific logic an ACD uses to make that decision is called a distribution method. Longest idle, round robin, and skills-based routing are all distribution methods; the ACD is the system running them.

How does ACD routing work?

When a call comes in, it typically moves through a few stages before it reaches an agent:

1. The caller reaches an auto attendant or IVR system, which may ask them to select a department, enter an account number, or answer a few prompts.

2. The IVR passes the call, along with whatever information it collected, to the ACD.

3. The ACD applies your configured distribution method to determine which agent or queue should receive the call.

4. If no agent is available, the call moves to a hold queue or a fallback option, such as voicemail or a callback request.

The rules an ACD applies aren't limited to agent skill or availability. Many systems can also factor in customer profile data, priority status, or time of day, so a VIP caller or an urgent issue can be routed differently than a routine one.

What are the different ACD distribution methods?

Most ACDs support several distribution methods, and which one you use can vary by queue, time of day, or call type:

• Longest idle: Calls go to the agent who's been waiting the longest since their last call.

• Fixed order: Calls are assigned to agents in the same set order every time.

• Round robin: Agents are rung in a rotating order; if an agent is reordered, added, or removed, the rotation resets.

• Random: Calls are assigned from a randomized list of agents that reshuffles once the list is completed.

• Skills-based: Calls go to the agent best equipped to handle them, based on ranked proficiency in areas like language or product expertise.

• Priority-based: Calls are weighted by factors like customer value, sentiment, or service-level urgency, so higher-priority calls can jump ahead in the queue.

Most contact centers don't rely on just one method. It's common to combine skills-based or priority-based routing with a fallback like longest idle, so calls still move efficiently even when the primary rule doesn't clearly apply.

ACD vs. IVR: what's the difference?

ACD and IVR are often mentioned together, but they handle different parts of the call. An IVR is what the caller actually interacts with: the menu prompts, the "press 1 for support," the account lookup. An ACD is the backend system that takes what the IVR collected and decides where the call goes next.

Think of the IVR as the front door and the ACD as the routing logic behind it. A call can technically reach an agent without an IVR, but pairing the two lets the ACD make a more informed routing decision based on what the caller already told the system.

ACD vs. skills-based routing: how do they fit together?

Skills-based routing is one of the distribution methods an ACD can run, not a separate system. The ACD is like a radio, and skills-based routing is one of the stations you can tune it to: a rule based specifically on which agents have the right expertise for a given call, rather than who's simply next in line or idle the longest.

You can also combine skills-based routing with other ACD rules. For example, a contact center might use skills-based routing during business hours and fall back to round robin or longest idle overnight, when fewer agents with specialized skills are on duty.

Why does ACD matter for customer experience?

An ACD's main job is making sure callers reach the right person quickly, and the effects of that show up across the whole contact center:

Faster resolution, fewer transfers: When calls land with the right agent the first time, callers spend less time being bounced between departments, which directly supports better first call resolution.

Shorter wait times: Even when no agent is immediately free, an ACD can queue callers with a clear wait estimate or a callback option, instead of leaving them on hold with no information.

Lower cost per call: Fewer misrouted calls means less time spent on manual transfers, which brings down the time (and cost) associated with each interaction.

A better agent experience: Agents spend less time listening to a caller's issue only to realize it belongs to another team. They can focus on the calls that actually match what they're equipped to handle.

What should you look for in an ACD system?

Not all ACDs are built the same way, and the right one depends on how your contact center actually operates. A few things worth prioritizing:

Flexibility across distribution methods: A system that only supports one rigid routing rule won't adapt well as your team or call volume grows. Look for one that supports multiple methods, including skills-based and priority-based routing, and lets you combine them.

Integration with the tools you already use: An ACD that connects to your CRM or ticketing system can route calls with more context, and give agents a fuller picture of the caller before they even pick up.

Built-in analytics: You'll want visibility into call volume, wait times, and routing performance without having to request a custom report every time.

Routing options beyond the human queue: Some interactions don't need a person at all. A flexible ACD can route straightforward requests to self-service or an AI receptionist first, reserving human agents for the calls that genuinely need one.

Dialpad's contact center brings these together in one platform: flexible routing across multiple distribution methods, native integrations with tools like Salesforce and Slack, and built-in analytics you can access without waiting on a separate reporting tool.

ACD and AI-driven routing

Distribution methods used to be limited to rules about human agents: who's idle, who's next, who has the right skill. That's changing. An AI receptionist can now sit ahead of the traditional ACD, handling routine requests on its own or gathering context before a call ever reaches a queue. When a caller does need a person, that context travels with the call, and the ACD can route it to the agent whose skills best match what the AI receptionist already learned.

This doesn't replace the distribution methods above so much as extend them earlier into the call, giving contact centers another lever for reducing wait times and freeing up agents for the interactions that need them most.