CLI routes
CLI routes that put your real number on the handset
Direct, audited carrier paths that pass your authorised caller ID intact — so the person you call sees a number they can recognise, trust and call back. Quality-tiered per destination, STIR/SHAKEN-aware for North America.
Your rate deck is available in the portal after sign-up.
Outbound · CLI route · US
+1 212 ••• ••••
54%
3.8min
1.9s
Sample values · live per destination in portal
What it is
A CLI route is a voice path that keeps your caller ID intact
CLI stands for Calling Line Identification — the number displayed on the phone you are calling. When you send a call to a carrier, you attach a CLI in the SIP signalling, usually in the From and P-Asserted-Identity headers. Whether that number actually reaches the handset depends on every network the call crosses on the way.
Many low-cost wholesale paths are "non-CLI": somewhere along the chain a transit carrier strips the number, replaces it with a generic one, or hands the call to a grey interconnect that presents something unrelated. The call still connects, but the person you are calling sees "Unknown", a foreign number, or a number that is not yours. Answer rates fall, callbacks go nowhere, and your own numbers start to collect complaints that are not yours to answer.
A CLI route is engineered the opposite way. CLIRoutes selects interconnects that are contractually and technically committed to CLI passthrough, tests them continuously, and removes any path that stops delivering. You send an authorised number; that is the number the recipient sees.
CLI routes are not about presenting any number you like. They are about presenting the right one — a number you own or are explicitly authorised to use — reliably. That is what turns a cold dial into a call people pick up.
End-to-end passthrough
Your From and P-Asserted-Identity are preserved across every hop to the terminating operator.
Audited paths only
Every interconnect on a CLI tier is test-called daily and dropped automatically if CLI is altered.
Authorised numbers
We verify that you own or are authorised to use each CLI range before it goes live on your account.
Attestation-aware in the US
US and Canadian calls are routed with STIR/SHAKEN attestation level in mind, not as an afterthought.
Who it’s for
Built for teams whose results depend on being recognised
If a missing or wrong caller ID costs you conversations, CLI routes are the default choice.
- 01
Outbound sales teams
Prospects answer local, consistent numbers. Present a DID in their area code and keep it stable across the campaign.
- 02
BPOs and contact centers
Run client programmes on the client’s authorised numbers, with clean separation per client in your portal.
- 03
Support callbacks
Customers expect a callback from the number they called. CLI routes make sure that is what they see.
- 04
Resellers and platforms
Offer a premium CLI tier to your own customers with per-destination quality you can show them.
How it works
How your caller ID travels from your PBX to the handset
A call crosses at least four networks. CLI is lost at the joins, so we control the joins.
- Hop 1Your PBX or dialerSends the call with an authorised number in From and P-Asserted-Identity.
- Hop 2CLIRoutes edgeAuthenticates you, checks the CLI against your verified ranges and signs where applicable.
- Hop 3Audited carrierA direct or one-hop interconnect contractually committed to CLI passthrough.
- Hop 4Recipient handsetThe terminating operator displays your number. Callbacks reach you.
What breaks CLI
Transit hops through grey interconnects, SIM-box termination, malformed number formats and carriers that overwrite headers to save cost.
How we protect it
Fewer hops, daily test calls per destination, E.164 normalisation on ingress and automatic removal of any path that alters CLI.
Failover without loss
When a path degrades, traffic fails over only to other audited CLI paths — never silently to a cheaper non-CLI tier.
Features
What you get with CLI Routes
Verified CLI passthrough
Only audited interconnects carry CLI-tier traffic. A path that changes your number is withdrawn from service automatically.
STIR/SHAKEN-aware routing
US and Canadian calls are sent on paths that respect the attestation level your numbers qualify for, which protects answer rates on major carriers.
Per-destination quality
ASR, ACD, PDD and NER per country and per breakout, updated continuously in the portal and available via API.
Quality tiers
Choose premium or standard CLI tiers per destination. Your rate deck in the portal shows exactly which tier each prefix uses.
Live call monitoring
See active calls, concurrent channels and short-duration spikes as they happen, so you can pause a campaign before it hurts a route.
24/7 NOC
Routing engineers on shift around the clock. Open a ticket from the portal with the CDR attached and get a human reply.
Quality metrics
The numbers that matter here
On CLI routes, a healthy ASR is the clearest sign your number is being delivered and trusted. These are the four we track per destination.
52%
ASR Answer-Seizure Ratio
Rises when your CLI arrives intact and is recognised. A sudden drop is often the first sign of number reputation trouble.
3.4min
ACD Average Call Duration
Long, stable call durations confirm real conversations rather than hang-ups after an unfamiliar number appears.
2.1s
PDD Post-Dial Delay
Short post-dial delay means fewer hops. Long PDD usually points to transit chains where CLI is at risk.
97%
NER Network Effectiveness Ratio
Measures whether the network completed the call attempt — separates route problems from people not answering.
Gauge values are illustrative. Live per-destination ASR, ACD, PDD and NER are in your portal.
Setup
From sign-up to first call
Most customers place their first CLI call the same day they finish onboarding.
- 1
Open an account
Sign up with your business details. We confirm a few business basics — company, website and use case. Extra documents are requested only where a destination's regulator requires them (for example some DID numbers or local CLI presentation).
- 2
Verify your caller IDs
Add the numbers you will present. DIDs bought from us are verified instantly; others need a letter of authorisation or ownership proof.
- 3
Fund your wallet
Top up in USDT (TRC-20 or ERC-20), BTC or ETH. Your rate deck is available in the portal after sign-up.
- 4
Create an endpoint
Add your server IP or create SIP credentials, then select the CLI tier for the destinations you dial.
- 5
Send traffic
Point your PBX or dialer at the CLIRoutes host and watch calls and quality in real time.
; Send your verified number in both headers[cliroutes]type=endpointoutbound_auth=cliroutes-authaors=cliroutesfrom_domain=sip.example-carrier.netsend_pai=yescallerid=+12125550123allow=ulaw,alaw,g729 [cliroutes-aor]type=aorcontact=sip:sip.example-carrier.net:5060Compare
How this route compares
Most customers run two or three route types side by side. Use the one that matches each traffic profile — mixing them on one trunk is the most common cause of poor answer rates.
| Attribute | CLI | IVR | CC | A-Z | SIP trunk | DID |
|---|---|---|---|---|---|---|
| Primary job | Outbound with your caller ID intact | Automated, consented campaigns | Agent-handled dialer outbound | Broad wholesale coverage | PBX / UCaaS connectivity | Inbound and owned CLI |
| Caller ID | Guaranteed passthrough | Authorised CLI, delivered | Authorised CLI, delivered | Tier-dependent | Your DIDs or authorised | Number you own |
| Typical call length | Medium to long | Short (under 60s) | Medium | Any | Any | Inbound, any |
| CPS / concurrency | Moderate, steady | High, approved per campaign | High concurrency, bursty | Scales with volume | Channel limit you set | Per-number channels |
| Consent review | CLI authorisation | Required per campaign | AUP + DNC hygiene | AUP | AUP | Regulatory documents |
| Typical buyers | Sales teams, BPOs | Notification & survey platforms | Call centers, dialer operators | Resellers, carriers | Businesses, UCaaS | Support desks, local presence |
- CLI
- Primary job
- Outbound with your caller ID intact
- Caller ID
- Guaranteed passthrough
- Typical call length
- Medium to long
- CPS / concurrency
- Moderate, steady
- Consent review
- CLI authorisation
- Typical buyers
- Sales teams, BPOs
- IVR
- Primary job
- Automated, consented campaigns
- Caller ID
- Authorised CLI, delivered
- Typical call length
- Short (under 60s)
- CPS / concurrency
- High, approved per campaign
- Consent review
- Required per campaign
- Typical buyers
- Notification & survey platforms
- CC
- Primary job
- Agent-handled dialer outbound
- Caller ID
- Authorised CLI, delivered
- Typical call length
- Medium
- CPS / concurrency
- High concurrency, bursty
- Consent review
- AUP + DNC hygiene
- Typical buyers
- Call centers, dialer operators
- A-Z
- Primary job
- Broad wholesale coverage
- Caller ID
- Tier-dependent
- Typical call length
- Any
- CPS / concurrency
- Scales with volume
- Consent review
- AUP
- Typical buyers
- Resellers, carriers
- SIP trunk
- Primary job
- PBX / UCaaS connectivity
- Caller ID
- Your DIDs or authorised
- Typical call length
- Any
- CPS / concurrency
- Channel limit you set
- Consent review
- AUP
- Typical buyers
- Businesses, UCaaS
- DID
- Primary job
- Inbound and owned CLI
- Caller ID
- Number you own
- Typical call length
- Inbound, any
- CPS / concurrency
- Per-number channels
- Consent review
- Regulatory documents
- Typical buyers
- Support desks, local presence
Compliance notes
Rules that keep this route stable
CLI routes only stay high-quality if every customer on them presents numbers they are entitled to use. These rules protect your answer rates as much as ours.
Authorised numbers only
Present numbers you own, have ported in, or are authorised in writing to use. We verify ranges before activation.
STIR/SHAKEN in the US and Canada
Calls are attested according to your relationship with the number. Full attestation requires numbers we can verify are yours.
Per-country CLI rules
Markets such as the UK, Germany and India have specific presentation rules. Country pages explain each one.
Consistent presentation
Use a stable, dialable number per campaign so recipients can recognise you and call back.
Coverage
CLI Routes by country
CLI support and rules vary by market. Each country page explains local caller ID requirements and which tiers deliver CLI there.
- United States
- United Kingdom
- Canada
- Australia
- Germany
- France
- Spain
- Italy
- Netherlands
- Belgium
- Switzerland
- Austria
- Sweden
- Japan
- Brazil
- Mexico
Why caller ID is the cheapest answer-rate improvement you can make
Teams spend heavily on data, scripts and agent training, then send calls on routes that show the wrong number. Recipients decide whether to answer in a second, based almost entirely on what appears on screen. A recognisable local number, delivered consistently, changes that decision more than any other variable you control.
CLI routes cost more to operate than non-CLI paths because they use fewer, better interconnects and are tested every day. In exchange you get calls that connect to the right person, show the right number and leave a callback path that leads back to you. For most outbound programmes the improvement in answered calls and conversation length outweighs the difference in route cost many times over.
FAQ
CLI Routes FAQ
Can’t find what you need? Our routing team answers within the hour, around the clock.
What is the difference between CLI and non-CLI routes?
On a CLI route the authorised caller ID you send is the number the recipient sees. On a non-CLI route the number may be stripped, replaced or shown as unknown because the call crosses interconnects that do not preserve it. CLI routes cost more to operate but deliver materially higher answer rates.
Which numbers can I present as caller ID?
Numbers you own, numbers ported to you, DIDs bought from CLIRoutes, or numbers your client has authorised you to use in writing. We verify ownership or authorisation before a range can be used on CLI routes.
Do you guarantee CLI delivery to every operator?
We guarantee that CLI-tier traffic only uses paths that passed CLI test calls, and we remove paths that stop passing. A small number of operators in some countries alter CLI on their own network; country pages note where that applies.
How does STIR/SHAKEN affect my US calls?
US and Canadian carriers sign calls with an attestation level that reflects how well the originating carrier knows the caller and the number. Calls with full attestation are less likely to be labelled as spam. Presenting numbers we can verify as yours gives you the best attestation available.
Can I use different caller IDs per campaign?
Yes. You can register several verified numbers and choose which one each campaign presents. We recommend a stable number per campaign and region so recipients can recognise and call you back.
How do I see if my CLI is being delivered?
The portal shows ASR, ACD and PDD per destination in real time. You can also request a CLI test call to a destination from the portal, and our NOC can run a delivery check on request.
Can I use CLI routes with a predictive dialer?
Yes, but heavy predictive traffic with many short calls is usually better on CC routes, which are tuned for dialer concurrency. Many customers run agent callbacks on CLI routes and the dialer campaign on CC routes.
How quickly can I start?
Once onboarding is complete and your caller IDs are verified, endpoints activate instantly. Most customers send their first call the same day.
Where can I see rates?
Your rate deck is available in the portal after sign-up, broken down by destination, breakout and quality tier.
Present your number. Get answered.
Open an account, verify your caller IDs and start on audited CLI paths. Your rate deck is available in the portal after sign-up.