- ACD (Automatic Call Distribution) is the brain that decides which agent takes the next call instead of ringing at random.
- It works with the IVR and queues: the IVR picks the department, and the queue picks the agent according to a strategy.
- The best-known strategies: ring all, round robin, least recent, fewest calls and fixed order.
- Skills-based routing is applied with specialised queues (language, product, key accounts) and agents in more than one queue.
You call a company, hear "for customer service press 1", then hold music, and a few seconds later an agent answers. Behind those seconds sits a system called ACD that decided: is an agent available? Which one? If all are busy, where do you wait and for how long? And if the wait runs long, where do you go?
This article explains what ACD is in plain language, its components, the automatic call distribution strategies with a comparison table, how to choose the right one for your business, and common mistakes that break distribution even on an excellent system. All of it is available in the Klamna call center.
Even for a small team, understanding ACD pays off: a simple decision like "ring everyone or take turns?" changes answer speed, workload fairness and agent morale, and separates a customer who reaches someone in seconds from one who hangs up and calls someone else.
What exactly is ACD?
ACD stands for Automatic Call Distribution. It is part of the PBX or call center system and distributes incoming calls across a group of agents according to rules you define. Without it you have two bad options: one number ringing one agent (while others sit idle), or every phone ringing at once with everyone racing — or everyone ignoring it.
ACD solves this by answering three questions for every call:
- Which group gets the call? (sales, support, billing) — usually from the caller's IVR choice.
- Which agent in the group? — according to the distribution strategy.
- What happens if nobody is available? — waiting, a message, voicemail or another queue.
Components of a call distribution system
| Component | Role |
|---|---|
| IVR | Greets the caller and routes them to the right department by keypress or working hours |
| Queue | Where calls wait for each department, with music and messages |
| Strategy | The rule that decides which agent rings first |
| Agents | Queue members and their status: available, busy, on break |
| Overflow rules | Where the call goes if it waits too long or there are no agents |
| Reports and wallboard | Service level, waiting, abandoned calls, each agent's performance |
If you are not familiar with IVR, read what is IVR or see Klamna IVR.
Distribution strategies
1. Ring all
All available agents in the queue ring at the same moment and the first to answer takes the call. Very fast for the customer and suitable for small teams (2–5 agents) or urgent lines. The downside: the fastest agent takes most calls and others get used to waiting for them.
2. Round robin
Calls go to agents in order, one after another, and the system remembers who was rung last and starts from the next. Fair in call count and suitable for sales teams where fairness matters.
3. Least recent
The call goes to the agent who has gone longest without a call. One of the fairest strategies for spreading workload, because an agent who just finished a long call gets a short breather before the next. It suits most customer service teams.
4. Fewest calls
The call goes to the agent who has answered the fewest calls today. Useful for balancing counts exactly, but it ignores call length: an agent with 20 short calls counts as busier than a colleague with 10 long ones.
5. Fixed order (linear / priority)
The call always rings the first agent, then the second if unanswered, and so on. Suitable when you have a primary agent and backups, such as a small clinic's reception: reception first, then the clinic manager.
6. Random
A random choice among available agents. Rarely the best option, but simple and it spreads load over time.
Comparison: which strategy fits you?
| Strategy | Answer speed | Fairness | Fits |
|---|---|---|---|
| Ring all | Very high | Low | Small teams, emergencies, reception |
| Round robin | High | High in count | Sales teams, leads |
| Least recent | High | High in workload | Customer service and support |
| Fewest calls | High | Medium | Calls of similar length |
| Fixed order | Medium | Deliberately unequal | Primary agent with backups |
Skills-based routing
Sometimes not every agent suits every call: an English-speaking customer, a technical question about a specific product, or a key account. That is where skills-based routing comes in. The practical way to apply it:
- Specialised queues: "English support", "technical support" and "key accounts".
- The IVR routes: "For English press 9", a product option, or the number the customer dialled (for example a dedicated key-account number).
- Agents in several queues: an English-speaking agent is a member of both the Arabic and English queues and takes calls from both.
- Smart overflow: if no one in the English queue is available within a set time, the call moves to the general queue instead of waiting forever.
- The owner first: if the caller has an assigned rep in the CRM, the call rings that rep before the queue. See the sales team CRM.
Settings that shape the customer experience
- Ring time per agent: 15–20 seconds is enough; if unanswered, the next agent.
- Wrap-up time: a few seconds between calls for the agent to write notes before the next rings.
- Maximum wait: after it the call goes to another queue, voicemail or the IVR.
- Hold music and messages: calm music and a short, useful message, not a long repeated ad. If you upload no music, a default hold music plays.
- Hide caller ID from agents: an option for queues where agents should not see the customer's number, while it stays in records for management.
- Link attendance to queues: with attendance and shifts agents join their queues when the shift starts and leave them on breaks, so calls never ring an empty chair.
Setup examples by business
| Business | Queues | Suggested strategy |
|---|---|---|
| Small clinic | One reception queue | Fixed order: reception then manager; voicemail after hours |
| Online store | Orders + support + returns | Least recent, with overflow from returns to support at peak |
| Real-estate company | Sales per project + owner services | Customer owner first, then round robin across the project team |
| Restaurant with branches | One queue per branch or central orders | Ring all within the branch; the IVR picks the branch |
| Financial services | Arabic + English + key accounts | Skills-based with overflow to the general queue |
In Klamna, ready templates at sign-up build a queue, IVR and working hours for your business, and you then change the strategy, members and wait times from the dashboard without a technician. The difference from a traditional PBX is that all of this is in the cloud: add an agent or queue in a minute, and agents answer from anywhere with no hardware in the office. For a comparison read cloud PBX vs traditional PBX.
How to know distribution is working
Watch four numbers: service level (e.g. 80% within 20 seconds), abandonment rate, how calls are spread across agents, and calls that went to overflow. If a call looks odd, open the call journey: it shows step by step what the caller chose in the IVR, how long they waited, who was rung and did not answer, and who finally answered. For more, read call center KPIs.
Common call distribution mistakes
- An IVR with too many options: callers get lost before reaching the queue. Three or four options are enough.
- A queue with no overflow: the customer waits ten minutes with no alternative.
- Agents logged into the queue who are not there: calls ring empty chairs and the journey gets longer.
- Ring all in a large team: twenty phones ringing together causes chaos and unfairness.
- Ignoring working hours: after-hours calls enter an empty queue instead of a clear message and voicemail.
Want to build your queues and distribution strategies yourself? Build your own package and see the price before paying at sign-up; ready templates set up a queue and IVR for your business from day one. Or talk to us and we will design distribution with you.
FAQ
Is ACD the same as IVR?
No. The IVR decides where the call goes based on the caller's choice; ACD distributes it to an agent inside that department. They work together.
What is the best strategy for customer service?
Usually "least recent", because it spreads workload fairly. For very small teams "ring all" is faster.
Can an agent be in more than one queue?
Yes, and that is the basis of skills-based routing: the agent is a member of every queue they can serve.
What happens if all agents are busy?
The caller waits in the queue with music and messages; after the time you set, the call moves to another queue or voicemail, and the missed call shows a call-back status so the team returns it.
Does distribution work with remote agents?
Yes. Agents take queue calls from the browser, the mobile app or the desktop app, under the same distribution rules.