Non-ACD in-call
Definition
Non-ACD in-call
Non-ACD in-call describes an inbound call routed straight to a named agent without passing through an automatic call distributor (ACD). The caller dials a direct extension, so the switchboard skips the queue entirely and connects both parties one to one.
That distinction matters because most contact center dashboards only measure traffic the automatic call distributor actually saw. Direct dials, warm transfers, and returned voicemails go uncounted in queue reports, which quietly distorts workforce planning.
For outsourcing buyers, the ACD versus non-ACD split is basic hygiene when you read a business process outsourcing (BPO) vendor’s productivity numbers.
Miss it and occupancy looks inflated while 10–25% of an agent’s real workload stays hidden — a quarter of the job at the top of that band.
Key takeaways
- Non-ACD in-call bypasses the ACD and lands directly with a named agent.
- The caller already holds the extension from a business card, a prior interaction, or a warm transfer.
- These calls sit outside ACD skill routing, queue service level, and standard occupancy math.
- Contact centers reconcile the traffic using separate agent state codes and adherence audits.
- Buyers should ask a vendor for the full state-code breakdown, not just the queue view.
How it works
A non-ACD in-call starts when someone dials an agent’s direct extension, so the private branch exchange (PBX) sends it straight to that desk phone or softphone. No skill rules, no hold music, no queue algorithm applies.
Three conditions have to line up before the call connects. The agent’s line needs to be publicly reachable, through a direct inward dial (DID) number or a Session Initiation Protocol (SIP) extension exposed to outside callers.
The agent also has to be free of any live ACD call, because the switch will not interrupt queued work.
And the platform must log the call under a non-ACD state code. Skip that and it quietly corrupts the queue’s average handle time (AHT), which then feeds bad numbers into every downstream key performance indicator (KPI).
Most modern telephony stacks treat non-ACD as its own agent state, sitting alongside ready, wrap-up, and auxiliary.
Genesys, NICE CXone, Five9, and Amazon Connect all ship that split by default — so managers can lift the minutes out of service level math while still paying for them.
That handling follows long-standing guidance from the International Customer Management Institute (ICMI), whose agent-state and occupancy standards are what most workforce teams build their state-code trees around.
Cisco documents the same split in its Unified Contact Center Enterprise reporting guides, where non-ACD calls carry their own call-type and state categories instead of folding into queue totals.
CloudTalk’s guide to call center agent duties makes the point from the floor. Agents field queued and direct traffic in one shift, so reporting must separate them or coaching gets muddled.
| Call state | Routed by the ACD? | Counts toward queue AHT? | Illustrative share of connected agent minutes | Typical use |
|---|---|---|---|---|
| ACD inbound | Yes | Yes | 70–85% | cold inbound to a shared queue |
| Non-ACD in-call | No | No, tracked separately | 10–25% | direct dial to a named agent |
| Non-ACD out-call | No | No, tracked separately | 3–8% | agent-initiated callback |
| Auxiliary | No | No | not connected time | breaks, coaching, training |
Those shares are illustrative bands, not vendor-reported figures. Ask any provider for its actual state-code split before you accept a productivity number at face value.
Examples
Non-ACD in-call turns up in three recurring patterns: dedicated-account handoffs, warm transfers between support tiers, and returned voicemails. Each one skips the queue, and each one still bills against paid agent time in the workforce report.
In 2024, a mid-market fintech in Manila put dedicated agents on its top 50 accounts. Those clients now dial the agent’s DID straight through, so roughly 20% of daily inbound arrives as non-ACD in-call.
That is one inbound call in five, invisible on the queue dashboard but plain in the per-agent activity log — the kind of gap that makes an occupancy report look better than the shift actually was.
A Philippines-based provider listed in OA’s Top 40 BPO companies in the Philippines guide reported in 2023 that warm transfers between technical tiers took up 15% of agent-connected minutes.
Every one of those transfers lands as non-ACD in-call on the receiving agent’s line. At 15%, that is close to one connected minute in seven arriving without ever touching the queue.
Healthcare and legal outsourcing operations lean on the pattern hardest, for continuity of care and for privileged conversations. A returning patient wants the case manager they spoke to last week — not the next available voice in the queue.
So the contact center publishes direct extensions and tracks that volume apart from ACD first call resolution (FCR) rates.
Deloitte’s 2024 Global Outsourcing Survey flagged personalization and named-agent continuity as top-quartile buyer priorities, which keeps pushing non-ACD traffic upward across mature BPO programs.
Related terms
The terms below sit either side of the routing boundary: the systems a non-ACD call skips, the places its minutes get reconciled, and the metrics it distorts when nobody tags it. Adjacent channel terms like email and chat fall outside this cluster.
- Automatic Call Distributor: the routing engine a non-ACD call bypasses entirely.
- Call Center: the operating unit where non-ACD activity gets reconciled against queue traffic.
- Interactive Voice Response: the front-end menu that direct-dial callers never hear.
- Average Handle Time: the headline metric non-ACD calls distort when they go untagged.
- Customer Service: the broader function both queued and direct calls serve.
- Business Process Outsourcing: the delivery model that most often reports a non-ACD split.
- Key Performance Indicator: the metric layer where non-ACD earns its own bucket.
FAQ
What does non-ACD mean in a call center?
Non-ACD describes any call that never touches the automatic call distributor. The agent is reached directly instead of through the queue and its skill-based routing rules. The work is identical; only the path and the reporting bucket change.
Is non-ACD in-call the same as a personal call?
No. Non-ACD in-call is work traffic: direct dials from customers, warm transfers between agents, and returned voicemails. Personal calls belong in auxiliary or off-phone time, which is a different state code entirely.
Why do managers track non-ACD in-call separately?
Queue metrics like service level and abandonment rate would skew if direct-dial volume were mixed in. Splitting the two keeps queue performance clean while still counting the agent’s paid time. It also shows supervisors who is carrying the named-account work.
Does non-ACD traffic count toward agent occupancy?
Yes. It counts toward paid occupancy and productivity, but not toward ACD-specific KPIs such as queue AHT or FCR. Most workforce management tools carve it into its own state bucket automatically.
How can outsourcing buyers audit non-ACD volume?
Ask for a state-code breakdown covering ACD inbound, non-ACD in-call, non-ACD out-call, and auxiliary. A credible vendor shares the full split, not the queue view alone. Gartner’s contact center research treats that transparency as a baseline selection test.
Does non-ACD in-call affect first call resolution?
It lands on the receiving agent’s personal log rather than the team’s rolled-up FCR, so the queue dashboard stays clean while the agent still gets the credit.
Compare vetted providers and contact center playbooks inside the Outsource Accelerator hubs to see how mature operations report non-ACD activity alongside their queue metrics.
Independent
