Here’s a debate that runs inside most wholesale voice teams, usually without anyone naming it. One side says: load every carrier’s deck into least-cost routing, let the engine choose per call, and manage by exception. The other says: the important destinations each behave differently enough that they need their own plan, written down and owned by someone.
A voice termination country playbook is that plan. It’s a short document for one destination covering which caller IDs survive, how origin affects price, the fraud exposure, the numbering quirks, what normal quality looks like, and how many independent routes you actually have. The question is whether it’s worth writing, and for how many countries.
Both sides have a real case. I’ll put each one as strongly as I can, then give a verdict.
The case for one global deck and LCR
The global-LCR position is that routing is a data problem, and data problems scale better with software than with documents.
The argument goes like this. A modern routing engine can evaluate every eligible route for every call on price, quality scores and capacity. It reacts in minutes. A playbook reacts when someone reads it. Carriers change rates weekly, routes degrade and recover daily, and no human-maintained document keeps up with that. Worse, playbooks go stale quietly: they describe the corridor as it was when someone last had time to update it, and people keep trusting them.
There’s also a coverage argument. A carrier buying termination into 150 or more countries can’t write 150 playbooks. If you can’t do it everywhere, doing it in some places creates a two-speed operation where the documented corridors get attention and everything else drifts.
And there’s a consistency argument. One routing policy, applied everywhere, is easier to audit. When something goes wrong, you debug one system.
It’s a strong case. For most of the long tail of destinations, I think it’s correct.
The case for corridor playbooks
The playbook position is that the things that hurt you most on a given corridor aren’t in the data your routing engine sees.
Take caller ID rules. Several regulators now require operators to block or strip international calls presenting domestic numbers, as an anti-spoofing measure. In the UK, Ofcom has required providers to block calls from abroad that present UK landline numbers, and has moved to extend that to UK mobile numbers when the caller isn’t roaming. In India, the Department of Telecommunications announced a system in October 2024 to identify and block incoming international calls that display Indian numbers. Your LCR engine doesn’t know any of that. It sees ASR drop and moves traffic to another route, which fails the same way, because the problem is the CLI you’re presenting, not the route.
Take origin-based pricing. For many destinations, the rate depends on where the call originated, and EU destinations commonly carry separate rates for traffic originating inside and outside the European Economic Area. Our mobile vs fixed termination guide explains why. A routing engine prices what it’s told. If origin is classified wrongly upstream, it will happily choose the “cheapest” route on the wrong column.
Take the US. Foreign-originated traffic that presents US numbers enters through gateway providers that have their own STIR/SHAKEN and robocall-mitigation obligations, and US providers are generally expected to accept such traffic only from foreign providers listed in the FCC’s Robocall Mitigation Database. That’s a relationship and compliance question, not a routing one.
The playbook side’s point is that the expensive failures on major corridors are structural. They come from regulation, commercial terms and numbering, and they don’t show up as a quality score until after they’ve cost you.
The verdict
Both sides are right about different destinations. The practical answer is a split: write playbooks for the corridors that carry most of your volume, most of your margin, or most of your risk, and run everything else through LCR with sensible defaults.
For most wholesale buyers, that means a small number of playbooks, often somewhere between five and fifteen, not a hundred and fifty. Pick them by ranking destinations on three measures: minutes, gross margin, and incidents (fraud, disputes, regulatory surprises) over the last year. Anything in the top slice on any measure gets a playbook.
The global-LCR side’s warning about staleness is fair, so the verdict comes with a condition. A playbook needs an owner and a review date. One without either will do more harm than none, because people will trust it.
The seven questions every playbook answers
A good playbook fits on a page or two. It answers the same questions for every corridor, so they’re comparable.
1. What caller ID will survive?
Which calling numbers can you present and still ring the handset? Are international calls presenting domestic numbers blocked? Does the destination require a particular format? Test with calls to real handsets on each major network, as described in our guide to CLI and non-CLI routes, and write down what arrived.
2. How is origin priced and classified?
Does the rate depend on where the call originated? How does your carrier decide origin: by calling number, by interconnect, or both? Which of your traffic falls into which column? Mistakes here are billing disputes waiting to happen.
3. What’s the fraud exposure?
Which number ranges in this country are associated with international revenue share fraud or premium-rate abuse? Are wangiri (one-ring callback) schemes common? What spending caps and alerts apply to this destination? Our SIP trunking security guide covers the attack patterns; the playbook records which ones matter here.
4. What does the numbering look like?
Is there a clear mobile-fixed prefix split, or are they mixed? How common is porting between networks? Has the numbering plan changed recently or is a change announced? Numbering changes show up as sudden 404 or 484 responses on a prefix, which look like route failures until someone checks the plan.
5. What’s normal quality here?
Write down the baseline: typical ASR, ACD and PDD ranges on your traffic, calling hours when answer rates are strongest, and known seasonal patterns such as national holidays. Without a baseline, every dip looks like an incident. Our ASR, ACD and PDD playbook covers how to build per-prefix baselines.
6. How many independent paths do you have?
Count routes that fail independently, not route entries in your LCR table. Two routes from different carriers that both buy from the same upstream aggregator are one path with two invoices. Ask carriers, as far as they’ll say, how they reach the destination. For critical corridors, you want at least two paths that don’t share a single point of failure.
7. Who owns it when it breaks?
Name the internal owner, the carrier escalation contacts for each route, and the notice periods for rate changes. Record the last review date. This is the section people skip, and it’s the one that decides how long an incident lasts.
Applying it: two quick sketches
A playbook doesn’t have to be elaborate to be useful. Two short illustrations of how the questions change the plan:
UK corridor for an offshore contact center. Question 1 dominates. If the contact center presents UK numbers from abroad, calls risk being blocked under the anti-spoofing rules, so the playbook sets the CLI policy first: which numbers are presented, how they’re authorized, and whether any traffic must originate in-country to legitimately present a UK number. The UK is also mid-transition away from the legacy copper phone network, which affects fixed-line destinations and deserves a line in the playbook’s numbering section.
EU corridor for a US-based CPaaS reseller. Question 2 dominates. The reseller’s traffic likely falls on non-EEA-origin rates, which changes the economics of every EU destination. The playbook records the origin classification, the rate columns that apply, and the quoting rule for customers so the reseller doesn’t sell EEA-origin prices on non-EEA-origin costs.
Neither sketch needs a routing change to be valuable. Both prevent the failure that LCR can’t see.
Keeping playbooks alive
The biggest risk to this approach is the one the global-LCR side named: stale documents. A few habits prevent it.
Review each playbook on a fixed schedule, quarterly for most corridors. Trigger an unscheduled review on any regulatory announcement in the destination, any incident, or any carrier change. Keep playbooks short enough that updating one takes less than an hour. Link each one to live dashboards instead of copying numbers into it.
Finally, feed what you learn back into routing. If a playbook establishes that a destination blocks a particular CLI pattern, encode that as a routing or signaling rule so the engine enforces it. The best playbooks gradually turn into configuration.
Coverage and where the carrier fits
The fewer suppliers you need for your core corridors, the simpler each playbook’s routes and ownership sections become. That’s a practical reason to consolidate core destinations with carriers that cover them directly. IDT Express, for example, terminates voice in 160+ countries on 1,000+ CLI-certified routes, which means many buyers can cover a large share of their playbook corridors through one interconnect, with a second carrier for path diversity where it matters. For the fundamentals behind corridor decisions, see our guide to how voice termination works.
Frequently asked questions
What is a voice termination country playbook?
A voice termination country playbook is a short written plan for one destination covering caller ID rules, origin-based pricing, fraud exposure, numbering, quality baselines, route diversity and escalation contacts. It captures the structural risks that routing software doesn’t see.
Is least-cost routing enough for international voice termination?
Least-cost routing handles price and measurable quality well, but it can’t account for regulatory caller ID blocking, origin classification errors or shared upstream paths. Most buyers combine LCR for the long tail with written playbooks for their highest-volume and highest-risk corridors.
How many country playbooks does a wholesale voice buyer need?
Most buyers need playbooks only for the destinations that rank highest on minutes, margin or incidents, which is often between five and fifteen. Everything else can run on LCR with standard defaults and monitoring.
Why are international calls with local caller IDs being blocked?
Several regulators require operators to block international calls that present domestic numbers, to fight caller ID spoofing. The UK and India both have such measures, so presenting a local number on a call entering from abroad can stop it from ringing.
What is route diversity in voice termination?
Route diversity means having termination paths to a destination that don’t share a single point of failure. Two routes from different carriers that rely on the same upstream supplier don’t count as diverse, because they fail together.
Talk to our carrier team
Planning coverage for your core corridors? Talk to the IDT Express carrier team about direct termination and path diversity for your top destinations.
