What a USA CC route covers
The traffic profile is the definition
Call-centre traffic looks wrong to a network built for conversations. Attempts arrive in bursts. A large share are never answered. The calls that connect are short. Measured across a day, the ratio of attempts to connected minutes is nothing like a business phone system, and a carrier reading those counters sees a pattern that on other routes would trigger a fraud review.
A CC route is a route whose supplier has agreed to accept that shape of traffic and has provisioned for it. That agreement is the product.
The label describes acceptance, not path
Two suppliers can both sell you "USA CC routes" and hand your calls to different carrier chains. One may interconnect directly with the terminating operator. The other may transit two intermediaries who each reserve the right to reroute. Same label, same country, very different answer rates — and a rate sheet will not separate them. The general mechanics are in VoIP routes explained.
"USA" is not one destination
Mobile and landline are frequently priced and routed separately, some prefixes are carved out, and a set of high-cost rural operators sits behind the same country code as everything else. A deck quoting one US rate is either simplifying or expecting you not to look.
CPS, concurrency and enforcement
Quote peak CPS, not average
Calls per second is the limit dialer operations hit before any other. A predictive dialer paces itself to agent availability, not to your contracted rate, so attempts cluster at the start of a campaign and after every break. US campaigns concentrate that further, because calling windows are set per state and the whole floor dials into the same permitted hours.
Illustrative, to show the arithmetic — not measured figures
A floor of 100 agents, a dialer set to three attempts per available agent, and a 20-second average ring time gives roughly 300 calls in flight and about 15 new attempts per second while the floor is fully staffed. An operation that reports "five CPS on average" across the day still needs a ceiling well above 15 to survive its own opening minutes.
Concurrency covers attempts, not agents
Concurrent channels have to cover every attempt currently ringing, not the calls agents are talking on. Sizing concurrency from headcount is the most common provisioning mistake, and it surfaces as rejected calls during exactly the periods the campaign was built around.
Ask what happens at the ceiling
The ceiling matters less than the behaviour at it. A route that rejects excess attempts with a clear SIP failure lets your dialer back off and lets you see it in your own counters. A route that queues adds post-dial delay your agents feel. A route that silently degrades — accepting the call and delivering it badly — is the worst case, because your reporting says the call completed. Rejections also feed back: most dialers retry, so a throttle upstream can produce more attempts rather than fewer.
Caller ID into the US
Attestation follows the number's owner
STIR/SHAKEN signs the calling number, and the attestation level reflects what the originating provider can vouch for: that it knows the customer, and that the customer has the right to use that number. A call handed between several carriers before it reaches the US rarely arrives with the strongest attestation, even when the number is genuine and the traffic is lawful.
Analytics sit on top of attestation
Terminating networks and handset features score inbound calls, and attestation is one input among several. Call patterns are another — short duration, high volume from one number, low answer rates. A campaign can be entirely lawful and still accumulate the profile that gets calls labelled, and once a number is labelled, changing route does not clear it.
What NCLI means into the US
A call with no calling number gives the framework nothing to sign, so it sits at the bottom of the attestation range by construction. That is the difference between NCLI as a cost saving and NCLI as a delivery problem — CLI vs NCLI routes sets out the answer-rate arithmetic.
The supplier question sheet
Nine questions, in the order they become answerable. The third column is what a weak answer sounds like — not dishonesty, usually just a reseller who cannot see the path either.
Before the quote
| Ask | Why it matters | Weak answer |
|---|---|---|
| How is US termination broken out? | Mobile, landline and high-cost prefixes are routed and priced separately. | "One flat US rate." |
| Direct or transit for our destinations? | Each intermediate carrier is another place caller ID can be rewritten. | "We have excellent coverage." |
| What is the billing increment? | Dialer calls are short; 60/60 rounding bills a full minute for each one. | "Standard terms." |
Before the test
| Ask | Why it matters | Weak answer |
|---|---|---|
| What CPS ceiling is provisioned? | Dialers burst well above their average at campaign start. | "As much as you need." |
| What happens when we exceed it? | Reject, queue and silent degradation produce very different reporting. | "You will not hit it." |
| Can you report CLI delivery rate per destination? | It is a separate number from ASR and rarely in a standard report. | "Our ASR is high." |
Before you move volume
| Ask | Why it matters | Weak answer |
|---|---|---|
| Who do we contact when a route degrades, and how fast? | Route problems are campaign outages; escalation speed is the product. | "Open a ticket." |
| Will you tell us when the carrier chain changes? | Least-cost routing reselects without any change to your contract. | "Rates are fixed." |
| What is the second path for our top destinations? | Single-sourcing turns one route fault into a silent campaign. | "We never have issues." |
A test plan for one week
What to run
- Dial handsets, not test numbers. Several US networks, landline and mobile, and record what each one displays for the calling number.
- Repeat at three times of day. Least-cost routing reselects continuously; a route tested once at 3am is a route you have tested once.
- Send a controlled slice of real traffic. One campaign, one destination set, enough attempts to see the CPS ceiling rather than model it.
- Force the ceiling deliberately. Push past the provisioned CPS in a window you control and record what the route does — reject, queue or degrade.
- Repeat the handset checks at the end of the week. Delivery that held on day one and fails on day five tells you the chain moved.
What to record
Keep it in your own CDRs. Supplier reporting describes their side of the call; you are buying outcomes on yours, and where the two disagree yours is the one that pays. Log answer rate, average duration, post-dial delay and caller ID delivery separately per destination, not as a blended figure.
Reading the metrics together
| Pattern | Usual meaning |
|---|---|
| High answer rate, very short duration | Answered by something that is not a person |
| Normal answer rate, rising post-dial delay | More hops than the route description implies |
| Falling answer rate, unchanged rate card | The carrier chain moved underneath you |
| Caller ID on one network, missing on another | Partial delivery — a routing conversation, not a config fault |
CC route or retail trunk?
A CC route fits when
- A dialer generates the traffic, not people
- Attempts far outnumber connected calls
- Average duration is short and volume is concentrated
- You need a CPS ceiling quoted and enforced
A retail trunk fits when
- Seats map to concurrent calls
- Calls are conversations, measured in minutes
- You want a published rate and self-service provisioning
- Volume is steady rather than bursty
The clause that decides it
Many retail agreements carry traffic-profile terms — maximum attempts, minimum average duration, restrictions on automated dialling. Traffic can sit inside the technical capacity and still breach the contract, and enforcement is usually suspension rather than a conversation. MCC provisions CC Routes for call-centre and dialer traffic and Wholesale Voice for general outbound termination; which one fits starts from the same questions about attempts, duration and destinations.
Failure modes to expect
Sizing from agent count
Capacity bought to match headcount runs out during the busiest minutes of a campaign — the minutes the campaign exists for.
Re-attempt amplification
When a route starts rejecting, dialers retry. Load already above the ceiling goes further above it, and provisioning turns into an argument about abuse.
Assuming caller ID survives
A number you own and may lawfully present can still arrive unattested or labelled. Presentation is a property of the path, not of your intent.
Treating the label as a spec
"USA CC route" answers one question. Path, CPS ceiling, caller ID behaviour and enforcement are four more, and each needs asking before the first campaign.
What this page cannot tell you
Rates, coverage and route types change by destination and by month. No guide — this one included — substitutes for testing the specific route you are offered. Rate-deck mechanics in general are covered in wholesale voice termination; the part specific to CC traffic is that short calls make the billing increment compound against you at volume.