Buying a phone number for a business should be a two-minute operation. In most CPaaS products it still is not — you pick a country, pick a number, pay, and only then find out the carrier wants a business registration, a proof of address, and three days of review before the number activates. The number sits in a pending state, the money is already committed, and the launch date the number was bought for is now a compliance timeline, not a provisioning one.
That ordering problem — discover the rules after the purchase instead of before it — is the thread that runs through number procurement, porting, per-country capability, and caller-name display. This post is about what a better ordering looks like in 2026: preview the regulation before checkout, check the country's actual capability mix before searching, treat number filing and caller-name display as owned operational tasks, and be honest about what can be predicted versus what still requires a carrier to say yes. All of it describes shipped Orbit behavior, documented in the numbers section of the docs.
The number inventory problem CPaaS solves poorly
Three failure modes repeat across number procurement, and all three are information problems, not carrier problems:
- Porting gaps discovered late. A team plans a cutover around moving its existing DIDs, submits the port, and learns during carrier review that one range is not portable or needs a Letter of Authorization nobody signed. The portability question was knowable before the request was filed; it just was not asked. Orbit runs a portability preflight — a check against a number or a bulk list — before anything is dispatched to a carrier, precisely so the "not portable" answer lands before the project plan does. The full flow is in the number porting guide.
- Capability assumptions discovered after purchase. "Buy a UK number for SMS" assumes UK local numbers carry SMS. They do not — UK, Germany, and France local numbers are voice-capable, and two-way SMS needs a mobile-range number in those markets. A buyer who searches first and reads capability second has already paid for the wrong line type.
- Regulation discovered after checkout. Germany, for example, requires identity and address documentation before a local number activates. A purchase that lands without those documents sits in a pending-compliance state — debited but inactive — until a compliance profile is attached.
The fix for all three is the same idea applied at different layers: surface the constraint before the commitment.
Orbit's regulatory-preview endpoint answers "what does this country want before this number type activates" as a pre-checkout API call: the required fields (registered business name, address, tax ID), the document categories the carrier asks for (ID proof, address proof), the expected activation window, and — the useful part — a boolean that says whether one of your existing compliance profiles already satisfies every requirement. When it does, purchase is immediate. When it does not, the buyer knows exactly which documents to collect before spending anything. When a country is entirely unregulated, the response says so and the number activates instantly.
The country-capabilities endpoint does the same job one level up: before running a search, summarize what a country actually has in stock per line type and capability — how many SMS-capable mobiles, whether local numbers carry SMS at all, whether toll-free is send-only, and the authoritative two-way SMS count across all line types. "The UK has plenty of local voice numbers but zero SMS-capable local numbers" is visible before the first search, not after the first wrong purchase.
What can be predicted today — and what still requires filing
Predictability in numbering has a hard boundary, and it is worth being exact about where it sits.
What a platform can tell you before purchase, with shipped Orbit behavior as the reference:
- Whether the country requires anything at all — the unregulated flag in the regulatory preview, which renders as an instant-activation answer.
- Which fields and document categories the carrier will want, and the typical activation window when a human review is involved.
- Whether you already satisfy it — the compliance-profile match against documents you uploaded once and reuse across profiles.
- What the country's inventory can and cannot do — the per-capability counts, including the send-only nature of toll-free SMS and the 10DLC eligibility of US local numbers.
- Whether a number can port — the preflight check, before any carrier sees the request.
What still requires a filing, and cannot be shortcut by any platform:
- Carrier or regulator approval. Orbit stores documents, carries them to the carrier, and surfaces the review status — final approval is always granted by the carrier or regulator in each country, not by the platform. That division of responsibility is stated plainly in the KYC documents guide, because pretending otherwise is how vendors get their compliance pages into trouble.
- The actual review window. A typical activation time is an estimate; the carrier's queue is the real timeline.
- Port execution. A preflight can say a number is portable; the Firm Order Commitment date still comes from the carrier, and the cutover still happens on carrier time.
The lifecycle side of ownership — what happens after a number is active — has the same predictability split. Auto-renewal, scheduled release, reassignment to a sibling subaccount, and reclaiming a parked number during its grace window are all deterministic, tenant-owned operations documented in the number lifecycle guide. The carrier-dependent parts — a provisioning repair, a release retry — are the exception, and they are labeled as such.
The tenant-owned checklist: preview, collect, file, confirm
Compliance posture on Orbit is deliberately tenant-owned: the platform carries your documents to the carrier and shows you the status, but supplying, renewing, and standing behind the documents is yours. That makes the procurement sequence a checklist your team runs, not a ticket you file:
- Review the preview. Before any search or purchase, call the regulatory preview for the target country and number type. If the response says unregulated, proceed. Otherwise read the required fields and document roles.
- Collect the documents once. Upload each document a single time into the KYC document library — passports, business registrations, utility bills, proofs of address — and get back a document ID for each. The same file backs a German number profile today and a Sender-ID registration tomorrow; there is no second upload.
- File the profile. Create a compliance profile for the country and use case, fill the structured fields the preview named, attach the document IDs, and submit for carrier review. The profile moves through draft, review, and approval; approval by the carrier is what satisfies the country's checks.
- Confirm capability, then buy. Cross-check the country-capabilities summary for the line type and channels the number actually needs to support — especially two-way SMS — and only then purchase. The preview's match flag tells you the purchase will activate immediately rather than landing in a pending-compliance state.
Documents age out, and an expired document blocks a renewal the same way a missing one blocks a first purchase — the renewal and expiry side of the document lifecycle is covered in the same KYC documents guide, so the checklist is a recurring loop, not a one-time onboarding task.
CNAM: what shows up on the recipient's screen
Number procurement gets you a callable, textable identity. CNAM decides what human beings see when that identity calls them — and "UNKNOWN" or a bare digits string is how legitimate support lines get treated like robocalls.
CNAM — Calling Name — is the up-to-15-character display name carriers store against a number and show on the recipient's handset. Orbit's CNAM surface models it as a deliberate two-step, and the two-step is the point:
- Capture the name. Register the desired display name against a number. The registration sits in a pending state — captured, not yet dispatch — so a typo or a wrong casing is a cheap correction rather than a carrier-side mistake.
- Dispatch it. A separate call hands the captured name to the wholesale provisioning queue that writes it to the carrier CNAM database. Until that dispatch, the name never appears on a handset; this is intentional, because writes to the authoritative carrier database run only on Devotel's own wholesale softswitch, and the API captures intent rather than writing through a third-party network.
Two adjacent truths worth planning around. First, CNAM display is a carrier-side rendering decision once the name is registered — a dip against the carrier database (what the network currently shows for your number) is the verification step, and that dip interface is staged to return live carrier data as the underlying database contract completes. Second, display name and spam labeling are different systems: a registered CNAM does not clear a "Spam Likely" label. Orbit exposes a spam-label snapshot per number and a remediation request to dispute labels with carriers, but remediation is a filing to a carrier reputation system, not an automatic clearing — same predictability boundary as everything else in this post.
For outbound-heavy teams, the practical coupling is with what the number does once it displays correctly: a registered name on a voice-capable number is the front door to the routes buyers evaluate on the contact center software and omnichannel platform pages, where the channel mix behind that number — voice, SMS, WhatsApp, and the rest — is what the global omnichannel messaging post covers at the API layer.
Frequently asked questions
What does the regulatory preview actually check before I buy a number?
It returns, for a specific country and number type, the data fields the carrier requires (registered business name, address, tax ID), the document categories it wants (ID proof, address proof), the expected activation window, and a boolean saying whether one of your existing compliance profiles already satisfies every requirement. When a country is unregulated, the response says so and purchase activates instantly.
Can the preview guarantee my number activates instantly once my profile is approved?
It guarantees the requirement check — that your approved profile covers every required field and non-expired document, so the purchase will not land in a pending-compliance state. Final approval is always granted by the carrier or regulator in the country, not by the platform, so the actual review window remains the carrier's timeline.
Why does my country show zero SMS-capable local numbers in the capability summary?
Because in many markets — the UK, Germany, and France among them — local landline numbers do not carry SMS at all; two-way SMS requires a mobile-range number, and toll-free SMS is send-only. The country-capabilities summary exists to show that per-country, per-line-type reality before you search, so the capability check happens before the purchase rather than after it.
Does registering a CNAM display name remove "Spam Likely" labels?
No — CNAM is the display name carriers show for your number; spam labels are a separate carrier reputation system. A registered CNAM improves recognition; a spam label has to be disputed through a remediation request against the carriers that flagged the number, filed per number with the carriers that flagged it.
Do I need to re-upload KYC documents for every country or number?
No. Documents upload once into a tenant-wide library and are referenced by ID across compliance profiles and registrations — the same business registration can back a German number profile and a Sender-ID filing. What recurs is renewal: documents have validity windows, and an expired document has to be replaced before it blocks a number.
Can I check whether my existing numbers are portable before planning a migration?
Yes — a portability preflight checks a number or a bulk list before any port request is dispatched to a carrier, so non-portable ranges and missing Letter of Authorization details surface before the migration plan does. Port execution itself — the Firm Order Commitment date and cutover — still runs on the carrier's timeline.
The takeaway
Number procurement has a predictable core and a filing boundary, and the quality of a platform is mostly about which side of that boundary the surprises land on. Preview the regulation before checkout, read the country's capability mix before searching, run the portability preflight before the migration plan, and treat CNAM registration and spam-label remediation as owned operational tasks with a two-step write path. The numbers and compliance docs carry the endpoint-level contract for each step; the omnichannel comparison is where the numbers you procure turn into the channel mix a contact center actually runs on.
Published 23 August 2026.