Automatic Call Distribution Guide

Automatic Call Distribution is the system that decides which agent should receive each inbound call, based on rules like skills, availability, priority and queue position. It sits behind IVR: IVR collects the caller's intent (Press 2 → Support), ACD picks the specific agent. Without ACD, 'Press 1 for Sales' goes to a single Sales queue; with ACD, it picks the best individual within Sales.

IVR is the menu that collects input; call routing is the generic movement of calls; ACD is the *intelligent* distribution logic that evaluates skills, idle time and priority to pick an agent. In large teams, IVR + ACD together reduce transfer and wait.

Match language, product or certification. Example: Hindi + Billing skill → Finance-trained agent; Tamil + Technical → L2 specialist. Skills can have proficiency levels (e.g., 1–5) and be combined: language fluency + product knowledge. Keep skill definitions simple (5–7 per team) and maintainable—skills drift as teams change, review weekly.

Not all skilled agents are equal. Proficiency weighting (e.g., Billing 5 vs 3) lets ACD prefer higher proficiency when multiple agents match. Use proficiency where certification matters; otherwise, simple skill tags suffice.

Distributes evenly in circular order (Agent A → B → C → A). Simple, fair, but ignores skill and idle time. Good for uniform small teams where every agent handles any call.

Gives the call to the agent waiting longest since last call. Balances load, reduces idle variance. Often combined with skill filtering: among skilled, pick longest idle.

VIP or high-value callers (CRM tag, repeat caller, high LTV) are routed first, or to dedicated queues. Example: Caller with open high-priority ticket → priority queue with shorter SLA. Use priority where business impact justifies queue jumping.

If no suitable agent is free, ACD holds the call in a queue, announces position or wait time, and may offer callback (virtual hold, per Ozonetel). Queue announcements and accurate wait estimates (based on avg handle time) reduce perceived wait. Offer escape: press * to return to IVR.

Queue priority orders waiting calls (VIP ahead). Overflow defines what happens when queue is full or wait exceeds threshold: route to backup queue, voicemail, callback, or alternate location. Business-hours vs after-hours overflow differ; multi-location overflow uses geographic or time-zone rules (e.g., Mumbai 9–6 → Hyderabad after 6).

Route by time: 9 AM–6 PM to Mumbai Sales, after-hours to Hyderabad or voicemail. Multi-location: geographic routing (caller STD code → nearest office) or language-based (Hindi → Delhi, Tamil → Chennai). For Indian teams, consider 12-language support (Kedeyo) and FOLLOW-THE-SUN for 24×7.

Multilingual: detect language via IVR selection or CRM tag, then match agent with that language skill. VIP: tag high-value accounts in CRM, ACD checks tag and routes to dedicated relationship manager. Both require CRM dip before ACD decision.

Before ACD picks, dip into CRM via webhook (caller ID → Salesforce record) to get skills/priority. Agent availability considers status (ready, wrap-up, offline), current workload and business hours. Remote agents via browser/WebRTC are treated same as on-site.

Track: queue length, abandonment (caller hangs up while waiting), Average Speed of Answer (ASA), service level (% answered within X seconds, e.g., 80% in 20s), first-call resolution. Monitor in real time; alert when queue > threshold. Abandonment often correlates with inaccurate wait estimates — improve estimates, offer callback.

Monitor via live dashboards: calls in queue, longest wait, agent states. Review routing weekly: skills change with attrition, new products need new skills, VIP lists update. Keep fallback: if ACD fails, route to simple round-robin or voicemail.

Scenario: 50-seat support, 10 agents Hindi-Billing, 10 Tamil-Technical. Caller: Hindi, Press 2 (Support), CRM shows billing history. ACD: filter Hindi + Support → 10 agents → among them, pick longest-idle with Billing proficiency 5 → connect. If none free, queue position 3, announce 2-min wait, offer callback. If queue >10, overflow to Hyderabad Hindi team.