CLI, NCLI and CC Routes Explained
Route quality is the part of wholesale VoIP that buyers get wrong most often, usually by optimising the rate and discovering the consequences in their answer rates.
CLI routes
A CLI route delivers your calling line identification to the called party. The number you send is the number that rings on the handset.
This matters whenever the recipient decides whether to answer based on who is calling — which is to say, almost always. It matters more when callbacks matter: a support line that customers dial back, or any outbound operation where the recipient returning the call is part of the process. CLI routes cost more because the interconnects that preserve CLI are more expensive to hold.
NCLI routes
NCLI means the calling number does not survive the journey. The recipient sees a withheld number, an unrelated number, or a random one substituted somewhere along the route.
NCLI is cheaper — often substantially. It is a legitimate choice for traffic where nobody is calling you back and the recipient's decision to answer does not hinge on the display: some automated notifications, some conferencing legs, some wholesale-to-wholesale traffic.
It is the wrong choice for outbound sales, for support lines, and for anything where a withheld number materially reduces the chance of an answer. Answer rates on NCLI to consumer mobiles are usually visibly worse, and that difference frequently exceeds the money saved on the rate.
CC routes
CC — call centre — routes are tuned for the traffic shape a dialling operation produces: very high concurrency, high attempt volume, short average duration, and a lot of unanswered calls.
A route that behaves well for a handful of long conversational calls can fall over under that pattern. Carriers also apply their own controls to traffic that looks like a dialler, so a route sold generically may throttle or degrade once your attempt rate climbs. If you run a dialler, say so when you ask for rates — a supplier who does not ask about your traffic shape has not thought about whether their route survives it.
The three numbers that actually tell you the truth
ASR — Answer Seizure Ratio. Answered calls as a percentage of attempts. The headline route-quality metric. Judge it per destination and against your own historic baseline for the same traffic, since what counts as healthy varies enormously by country and by whether you are dialling mobiles or fixed lines.
ACD — Average Call Duration. If ACD collapses while ASR holds, calls are connecting and then failing — one-way audio, dead air, early teardown. ASR alone will not show you that.
PDD — Post Dial Delay. The gap between dialling and ringback. Long PDD usually means extra hops. Callers abandon during it, which then depresses your ASR without ever looking like a routing problem.
Picking the right route for your traffic
Match the route to what the traffic needs, not to the cheapest line on the deck.
Outbound sales and any callback-dependent traffic: CLI, and accept the rate. High-volume dialling: CC routes, and tell the supplier your concurrency and expected ACD. Automated one-way notifications where nobody dials back: NCLI is defensible, and the saving is real.
The mistake that costs the most money is buying NCLI for callback-dependent traffic because the per-minute rate looked better.
Frequently asked
Frequently Asked Questions
A CLI route delivers your calling line identification, so the recipient sees the number you sent. An NCLI route does not — the number is withheld, replaced or randomised in transit. CLI routes cost more because preserving caller ID requires better interconnects. NCLI is cheaper and acceptable for traffic where nobody calls back and the display does not affect the answer decision, but it typically reduces answer rates on consumer mobiles enough to erase the saving on callback-dependent traffic.
There is no single good number, and any supplier quoting one without asking about your destinations is selling rather than answering. ASR varies enormously by country, by mobile versus fixed, by time of day and by the quality of your dialling list. The meaningful comparison is against your own baseline on the same destinations with the same traffic. A route that drops your ASR against that baseline is a bad route regardless of the absolute figure.
Post Dial Delay is the time between the call being dialled and ringback being heard. It is a direct proxy for how many hops the call is crossing — a long PDD usually means the call is transiting several carriers rather than reaching the destination network directly. It matters because callers and diallers abandon during that silence, which shows up as a lower answer rate without ever presenting itself as a routing fault.
CC routes are call-centre routes, provisioned for the traffic pattern a dialling operation generates: high concurrency, high attempt volume, short average call duration and a high proportion of unanswered attempts. General-purpose routes often degrade or get throttled under that pattern because carriers apply controls to traffic that looks like a dialler. If you run a dialler, tell your supplier your concurrency and expected ACD before you contract.
Yes, and most operators with a mixed traffic profile should. Route callback-dependent and sales traffic over CLI, and put automated one-way traffic where the display does not matter over NCLI. Splitting by traffic type rather than buying one quality tier for everything is usually where the real saving is, because you stop paying CLI rates for traffic that does not need it and stop losing answers on traffic that does.
Get a rate deck for your destinations
Send us your destination list and monthly volume. We’ll come back with rates.
Request rates