"Carrier of record" and "omnichannel communications platform" sound like two different product categories. They are one buying decision wearing two hats. A carrier of record answers the question: whose network carries your voice and messaging traffic, and who is accountable for delivery. An omnichannel platform answers: how many channels share one account, one contact record, and one bill. Any vendor you pick in 2026 is being judged on both — so this page collects the criteria that decide the answer in production, not in a slide deck. It is deliberately about what to evaluate and how to verify it, not a vendor ranking; the Alternatives hub holds the head-to-head comparisons once these criteria have set your shortlist.
Why this evaluation changed going into 2026
Three shifts turned "which CPaaS" from a rate-card comparison into a due-diligence exercise.
Termination accountability now shows up in the data. US A2P 10DLC enforcement, STIR/SHAKEN attestation on calls, and RCS sender registration mean the chain between your application and the subscriber's carrier is inspectable. If a vendor cannot say whose switch terminates your outbound calls and messages, you will discover the answer at the worst moment — as an undiagnosable delivery failure with no one to call.
Channel count stopped being a differentiator. Every credible vendor lists SMS, WhatsApp, RCS, email, and voice. The 2026 question is whether those channels behave as one system — one contact timeline, one consent record, one wallet — or as co-branded products stitched at the account level.
AI agents moved the unit of work. Once an AI agent can resolve a customer contact across a chat that becomes a call that becomes a WhatsApp follow-up, "price per SMS" stops being the right comparison. The cost to compare is per resolved contact, and the architecture to inspect is whether the agent, the channels, and the human inbox actually share one record.
The criteria that decide the answer
Each criterion below is stated as a question you can put to any vendor — including us — and each comes with the proof that counts as an answer.
Network ownership — who operates the switch your traffic terminates on
There are three models in the market. A carrier of record holds regulatory carrier status and operates its own switching infrastructure (Bandwidth is the well-known US example). An aggregator-reseller sells access to networks it does not operate and passes both the latency and the accountability through. A wholesale-backed platform is a software platform anchored on an affiliated wholesale carrier's switch — the model Orbit runs, where outbound voice and SMS terminate on Devotel's own wholesale softswitch rather than a resold upstream. The right answer depends on your volumes, but the wrong answer is "we have great carrier relationships" with no switch you can name.
The termination path — can the vendor say where an outbound call or message exits
Ask for the delivery path of one outbound SMS and one outbound call, end to end. A vendor terminating on infrastructure it owns or directly operates can show a delivery receipt that reaches its own switch; a reseller shows you a receipt from its supplier, with the actual termination one hop further away and out of view. This is the difference between a delivery failure you can escalate and one you can only report. It is also where latency and price stability come from — every resold hop is a margin and a queue you don't control.
Compliance per market — registration, attestation, quiet hours, consent
Compliance in 2026 is per-market and per-channel: 10DLC brand and campaign registration for US A2P messaging, STIR/SHAKEN attestation levels on voice, sender registration for RCS, opt-out handling that survives a channel switch, and TCPA quiet-hours rules enforced before a message leaves. Score this as its own line item, not as a checkbox — the question is whether the platform enforces these at send time or hands you the liability with a documentation link.
One contact record — does the timeline survive a channel switch
The definition to hold vendors to: one customer's website chat, WhatsApp message, and follow-up phone call appear on a single timeline that a human agent opens without searching. A nightly sync between a "messaging product" and a "contact-center product" does not meet it. Neither does a shared login over separate databases. Ask for the demo: chat to call to message on one screen, one consent state, one identity.
Pricing at the unit of work — per resolved contact, not per channel rate
Headline SMS rates exclude LLM, TTS, and STT pass-through in AI deployments, and exclude the human inbox the conversation escalates to. Compare at the unit of work: one resolved customer contact, however many channels it touched. Then check whether the pricing survives procurement — published pay-as-you-go rates with no per-seat licence and no annual minimum can be evaluated at any scale; quote-only pricing reopens the evaluation at renewal, once switching is expensive.
The proofs that survive a demo
Whatever the answers above, the evaluation ends the same way: the contact-record merge shown live on the vendor's own dashboard, a delivery receipt traced to the terminating switch, and a rate card you can read without a sales call. Claims that can't be shown in one of those three forms are marketing, not criteria.
How to evaluate a carrier of record or omnichannel platform, step by step
1. Map your channel mix and markets before opening a comparison sheet
List the channels and the countries you will actually send into over the next 12 months. A vendor's global channel list is irrelevant next to the markets where it has registered, attested, insurable termination.
2. Name the terminating network for outbound voice and SMS
Ask who operates the switch your outbound calls and messages terminate on, and get a name: the vendor's own carrier operation, an affiliated wholesale switch, or a resold upstream. Orbit terminates outbound voice and SMS via Devotel's own wholesale softswitch — answer this question for every candidate before comparing features.
3. Score compliance per market as its own line item
For each market on your list from step 1: who handles registration, what attestation applies, where are quiet hours enforced, and where does consent live when a customer moves between channels. Vendors that can only point to documentation leave the liability with you.
4. Demand the live channel-switch demo
One contact, three channels, one timeline — shown live, then shown with an AI agent handling the first leg and a human agent inheriting the full history. This single demo answers most of the omnichannel question.
5. Compare at the unit of work and read the rate card yourself
Rebuild one resolved customer contact — AI minutes, messaging follow-ups, human-agent time — against each vendor's published pricing. If a vendor has no published pricing, treat the absence as an answer.
6. Trace a delivery failure end to end
Ask what happens when an outbound message is not delivered: which dashboard shows it, whose logs explain it, and which team can fix it. The answer reveals the real operating model faster than any architecture diagram.
Common traps in this evaluation
Comparing channel lists instead of termination paths. Channel count converged years ago; what did not converge is whose infrastructure an urgent, regulated, time-sensitive message exits through.
Accepting "unified" as a demo word. Unified means one contact record, one consent state, one timeline, and one wallet — observable in one screen, not described across four slide sections.
Treating compliance as legal homework. In 2026 compliance is enforced or it isn't. A platform that enforces registration, attestation, and quiet hours at send time is a different product from one that emails you a best-practices guide.
Scoring headline rates against AI-era workloads. A per-minute or per-message rate that excludes the AI stack and the human inbox is not a cheaper option — it is a smaller fraction of the same bill.
Where Orbit fits
Orbit by Devotel is the wholesale-backed model applied to the omnichannel question: outbound voice and SMS terminate via Devotel's own wholesale softswitch (criterion 2, with termination accountability behind it), the channels share one contact record and one pay-as-you-go wallet with every rate published on the pricing page (criterion 5), and AI agents handle the first leg of a conversation then hand the full history to a human inbox (criterion 4). For the carrier-vs-reseller infrastructure angle behind criterion 1, see carrier vs. reseller in CPaaS; for the consolidation question behind criterion 4, one provider vs. multiple vendors.
Frequently asked questions
What is a carrier of record, and why does it matter in 2026?
A carrier of record is the licensed operator whose network — and whose regulatory standing — your traffic runs on. It matters in 2026 because 10DLC, STIR/SHAKEN, and RCS registration made the termination chain inspectable: the party that terminates your traffic is the party that can see and fix a delivery failure, and "we have carrier relationships" is no longer an answer to that question.
Is choosing a carrier of record a different decision from choosing an omnichannel platform?
No — it is the same evaluation from two directions. Any platform you pick is judged on whose switch terminates outbound traffic and on whether the channels behave as one system. Evaluate both in one pass, or you pick a messaging vendor that can't carry voice, or a carrier that can't hold a contact record.
How do I verify a vendor's "we own our network" claim?
Ask what terminates outbound voice and SMS, and for the delivery receipt path end to end. Operated infrastructure produces receipts that reach the operator's own switch; resale produces receipts from a supplier you cannot see. The claim that survives this question is verifiable; the rest is positioning.
What's the single most common mistake in this evaluation?
Comparing headline per-channel rates instead of the unit of work. Once AI agents, follow-up messaging, and a human inbox all touch one customer contact, the cheapest per-SMS rate and the cheapest resolved contact are rarely the same vendor — rebuild one real contact against published pricing before shortlisting.
How many vendors should survive these criteria before head-to-head comparisons?
Two to four. Criteria 1–3 (network, termination, compliance) usually cut the list by more than half before any feature comparison is worth running — then take the survivors to the Alternatives hub for head-to-head comparisons grouped by business size.
Sources and further reading
- Carrier vs. reseller in CPaaS: how to verify a network-ownership claim, vendor by vendor.
- One provider vs. multiple vendors: the integration and accountability trade-off behind criterion 4.
- How to choose an omnichannel communications platform: the global-market version of this evaluation.
- Alternatives for 2026 hub: head-to-head comparisons once the criteria above have set your shortlist.
Published 26 August 2026. Part of the Orbit resources library: foundational guides for teams building on communications infrastructure.