What Is ACD in VoIP?

ACD stands for average call duration — the mean length of calls that actually connect and complete, measured over a route, a destination, or a campaign. It's one of the two metrics (alongside ASR, answer-seizure ratio) that wholesale voice providers track most closely to judge route quality, and it behaves very differently for call center traffic than it does for general business calling.

What ACD measures, precisely

ACD is calculated from completed calls only — calls that were answered and held for some duration before ending, however short. It doesn't include no-answer, busy, failed, or rejected attempts; those get captured separately in metrics like ASR. So a very low ACD doesn't necessarily mean something is broken. It can simply reflect the nature of the calls that connected: short, quickly resolved, or ended abruptly for reasons unrelated to route quality.

Why call center traffic runs low ACD

A meaningful share of dialer-generated call attempts that connect don't turn into long conversations. Some hit voicemail and get identified and disconnected quickly. Some connect to a live person who hangs up immediately, uninterested in an outbound call. Some are calls where the dialer itself drops the call within a second or two because it over-attempted relative to agent availability — a known behavior in predictive dialing sometimes called call abandonment, distinct from the recipient hanging up. Even calls that do reach an agent and get handled are often short by design: a scripted outbound call, a quick qualification question, a brief service update.

None of that is a sign of a failing route. It's the expected shape of call center outbound traffic. A route provider unfamiliar with call center patterns might see a low ACD number and assume something is wrong with the route, when in reality it's simply reflecting how the traffic behaves. This is exactly why CC routes are monitored with call-center-specific baselines rather than judged against ACD expectations built around longer-format business or consumer calling.

How ACD affects route selection and pricing

Route selection logic that weighs ACD alongside ASR needs to interpret both metrics in context. A route with low ACD but strong ASR (calls are being answered reliably; they just don't last long) is behaving normally for call center traffic. A route with low ACD and weak ASR is a different, more concerning signal — it suggests calls aren't connecting reliably at all, or worse, that something is truncating calls that should otherwise be running longer, which can indicate a technical routing problem rather than a normal traffic pattern.

Pricing is affected too, since termination costs are generally structured around minutes used. Low-ACD traffic means many short calls rather than fewer long ones, which shifts where the real cost sits in a rate deck and makes billing increment policy more consequential than it would be for longer-duration traffic.

ACD and billing increment

Billing increment — how a call's duration is rounded for billing purposes — matters disproportionately for low-ACD traffic because the rounding overhead is a larger percentage of a short call than a long one. A provider offering full-minute billing, per-second billing, or a hybrid structure will produce meaningfully different effective costs on a large volume of short calls, even at an identical quoted per-minute rate. This is one of the more overlooked line items when comparing CC route providers, precisely because call center traffic's low-ACD profile makes billing increment choice matter more than it would for a business with fewer, longer calls.

For the other half of the route quality picture — how call attempt rate factors in — see what is CPS in VoIP, or explore CC routes built around low-ACD, high-CPS call center traffic.