Quick answer: A carrier of record is the licensed operator under whose regulatory filings a phone number actually lives — the entity carriers, registries, and auditors can name. On Devotel Orbit that is Devotel's wholesale softswitch: the numbers you search, buy, and port in terminate on infrastructure the same company that runs your messaging and voice APIs also operates, instead of on a reseller's upstream carrier. The comparison page, carrier-of-record infrastructure, argues the network-ownership case as a table; this post walks the same posture from the buyer's side — what changes the day you buy a number, and what stays yours either way.
The distinction matters because number procurement is where platform abstractions end. A voice-minute rate is a commodity; a number is a regulated identity — carriers file for it, regulators document it, and your customers save it. Who holds the record determines whose paperwork you're on, whose markups you're in, and whose answer you get when routing, caller ID, or a compliance status is wrong.
What a carrier of record looks like from inside Orbit
From the dashboard, "carrier of record" is invisible until you need it — which is the point. The flow a buyer touches is Numbers → Buy: search by country and capability (voice, SMS, MMS), read the per-country capability counts before searching anything, and preview the regulation before checkout. The regulatory-preview walkthrough covers that pre-checkout layer in depth: what the country wants, whether one of your existing compliance profiles already satisfies it, and the expected activation window before any money moves.
The carrier-of-record posture sits underneath that flow. When the operator of the network is the same company that runs the platform, three buyer-visible things change:
- One point of truth for routing and caller ID. Shipped caller-name behavior (CNAM registration on US numbers, the branded-calling work) is an operational task Orbit owns on its own network — not a ticket relayed to an upstream carrier whose answer you then re-relay to your customer.
- Pricing with no third-party layer. A reseller's rate card carries an upstream carrier's wholesale price plus a margin; an owned network publishes its own rates. The comparison table on the carrier-of-record page states this as owned-vs-resold on the operational questions a shortlist hinges on.
- The port-in path is the same network as the buy path. Porting lands your numbers on the same infrastructure new purchases activate on — one routing answer, one support chain. Section four below picks that thread up.
None of this is aspirational. The numbers routes in the dashboard — search, buy, regulatory preview, capability counts, porting — all terminate on the shipped product today.
The buying journey per region, through the guides already shipped
"Carrier of record" changes whose filing a number lives under; it does not change that filings exist. Every region layers its own regime on top, and three of the four regions Orbit covers already have shipped guides for exactly that layer. Walk the journey by region:
- US — sender identity is the regime. Buying a US local number for A2P messaging runs into 10DLC registration; buying a toll-free number runs into toll-free verification; calling US recipients runs into CNAM and branded-caller posture. The carrier of record is where those registrations get filed and defended. Orbit's tenant-owned side of that loop — collecting consent proof, registering the sender identity, keeping campaign drafts aligned with what was registered — is the subject of the KYC & sender-ID compliance loop checklist.
- EU + UK — data residency and identity documents are the regime. Local numbers in Germany, France, and the UK carry identity and address documentation requirements before activation, and voice-plus-SMS traffic inherits GDPR/UK-GDPR residency questions: where recordings and message bodies live, who can access them, and what the data-processing terms say. The GDPR data-residency buyer checklist for voice and SMS is the region's shipped guide — it frames residency as a set of tenant-verifiable controls, not a vendor promise.
- India — consent receipts are the regime. The DPDP Phase-II posture asks a business messaging Indian recipients to hold proof of consent as a first-class record — not a boolean on a contact, but a receipt. The India DPDP Phase-II consent-receipts guide walks what a receipt has to contain and where Orbit stores it as tenant-owned data.
The pattern across all three: the carrier-of-record question decides whose network the number terminates on; the regional regimes decide what you must hold as a tenant. Neither substitutes for the other, and the guides treat both as shipped, documentable surfaces.
The compliance posture per region — and what stays tenant-owned
A carrier of record files for the number; it does not own your vertical's compliance. That split is deliberate and it is how Orbit's shipped bundles work. The vertical compliance bundles announcement lists the four tenant-activated packs — healthcare (HIPAA-conscious patient messaging), fintech (KYC onboarding and account alerts), e-commerce (order lifecycle and re-engagement), and payments (PCI-safe collection). One activation provisions a draft compliance profile, draft campaigns, a vertical-tuned agent, and a double-opt-in flow, then hands back a go-live checklist — Business Associate Agreement before patient messaging, transactional-versus-marketing consent split before fintech promotions, marketing consent separated from order updates in e-commerce, payment links that route to a PCI-compliant hosted page and never carry card data over SMS.
Every one of those checklist items is a tenant-owned control. The carrier of record is the same in each case — the numbers terminate on the same network — but the compliance posture is yours to activate, yours to clear, and yours to evidence. That is the honest reading of "carrier of record" in a regulated vertical: it governs infrastructure accountability, not your regulatory duty. The comparison page's owned-vs-resold table makes the infrastructure argument; the bundles make the tenant side explicit.
What port-in means when the provider is the carrier of record
Porting has a regulatory definition we will not compress here — the porting walkthrough covers LNP, the CSR, the LOA, and FOC timelines end to end. The carrier-of-record angle is narrower and worth stating: a port-in is a carrier-of-record transfer. You are not handing a platform a pointer to your number; you are moving the number's filing from the old carrier to the new one, with paperwork a regulator can audit.
When the platform is the carrier of record, that transfer lands directly on the network your new purchases already run on. Orbit's shipped porting flow is built around visibility into exactly that transition: a bulk portability preflight (up to 1000 numbers per call) before anything reaches a carrier, a combined readiness gate, in-platform LOA signing, and per-stage porting webhooks so "where is this port stuck" is an API answer, not a support-ticket answer. The reason this post bothers to separate port-in from buying is that buyers routinely conflate them with import — a port is not Orbit reading your old carrier's records; it is the regulated move of the record itself.
Frequently asked questions
Does "carrier of record" change my compliance obligations as an Orbit tenant? No. It changes whose filing your numbers live under and who is accountable for network-level answers (routing, caller ID, carrier registrations). Your consent records, sender registrations, vertical checklists, and data-residency posture remain tenant-owned — the compliance guides linked above document those controls as things you configure and can evidence.
Is carrier of record the same as "Orbit owns physical phone lines"? It is the regulated version of that claim: the licensed operator whose records regulators and carriers consult for the numbers in question. Devotel operates its wholesale softswitch in that capacity; the comparison page states the owned-vs-resold difference on the operational questions (routing accountability, CNAM ownership, pricing layers) rather than as a slogan.
If I port numbers in, do I buy the rest of my inventory the same way? Yes — ported and purchased numbers sit in the same numbers inventory, same dashboard, same APIs. The port-in flow adds the preflight, the LOA step, and the FOC wait; afterwards the numbers are indistinguishable from bought ones.
Where do I start if my buying decision is still open? Read the carrier-of-record comparison for the owned-vs-resold table, then the regulatory-preview post for the pre-checkout behavior you can test on a free account before committing anything.