Platform as a service for communications: what must be true before you build on it
What is platform as a service for business communications?
Platform as a service (in communications, the model most buyers call CPaaS) means a provider runs the voice network, the messaging channels, the AI agents, and the contact center as one hosted product you build on — so your application consumes calls, texts, and agents-in-the-loop as one account, not as carrier contracts and channel vendors you integrate yourself. The evaluation splits on what must be true underneath the label: does the provider own the network your calls terminate on, is there one SLA across every channel, are the AI agents native rather than a bolted-on product, and does one pay-as-you-go bill cover the whole surface? Orbit by Devotel passes all four: every voice leg terminates on Devotel's own wholesale carrier-of-record softswitch (500+ voice-aggregator and mobile-operator interconnects), one published SLA covers voice, SMS, WhatsApp, RCS, email, video, and AI agents together, AI voice and chat agents run inside the same queues and inbox as human agents, and everything meters onto one pay-as-you-go bill with published rates. A provider that resells another platform's network, or ships its AI layer as a separate product, fails the test regardless of what it calls itself.
The need-to-know evaluation checklist
These are the factors that decide whether a communications platform as a service is one product or a stitched stack wearing the label. Ask every short-listed vendor all six — including us.
1.Does the provider own the network, or resell someone else's?
Voice quality, caller-ID integrity, and STIR/SHAKEN signing trace to whoever owns the softswitch your calls terminate on. A reseller adds a second provider to every quality issue. Orbit terminates every voice leg on Devotel's own wholesale carrier-of-record softswitch, which interconnects with 500+ voice aggregators and mobile operators — one accountable party for the call.
2.Is there one SLA across every channel, or one negotiated per channel?
A stitched stack pays you a separate guarantee per vendor and no guarantee on the seams between them. Orbit publishes one uptime SLA across voice, SMS, WhatsApp, RCS, email, video, and AI agents — 99.0% on Pay-as-you-Go up to 99.99%+ on Enterprise, with service credits if it's missed — so the whole surface answers to one commitment.
3.Are the AI agents native, or a separate product bolted on?
The first real use of AI in a communication stack is answering and resolving calls and chats inside the queue your human agents already work. Orbit's AI voice agents run in the same ACD queues and AI chat agents in the same inbox as human agents, so a conversation moves between AI and human without leaving the platform — no second AI product to integrate.
4.Does one bill cover every channel, with published rates?
Adding a channel should never start a new procurement cycle. Orbit meters voice minutes, messages, AI-agent usage, and the contact center onto one pay-as-you-go invoice with published per-country rates and no required per-seat licence — so the evaluation survives contact with your finance team.
5.Can a developer read the API, and an admin run the console, in the same account?
A PaaS that is only an API forces your operations team to build their own surface; one that is only a console leaves builders locked out. Orbit ships both: a documented REST API with SDKs in every major language for builders, and a working dashboard — queues, inbox, wallboards, flows — for the team that runs it day to day.
6.Does one customer timeline span every channel?
The point of omnichannel is that a call, a text, and an email from the same customer land in one thread. Orbit reads and writes one per-customer conversation timeline across voice and messaging, so an agent picking up a call sees the SMS that came before it — the difference between a platform and channels sharing a login.
What a PaaS on Orbit ships today
| Capability | What you get |
|---|---|
| Owned carrier-of-record voice network | Every voice leg — inbound, outbound, IVR, ACD-routed, and AI-voice-agent calls — terminates on Devotel's own wholesale softswitch connected to 500+ voice aggregators and mobile operators, with STIR/SHAKEN signing applied end to end. |
| Every business messaging channel | SMS and MMS, WhatsApp, RCS, and email sit on the same account as voice, sharing contacts, consent state, and the conversation timeline — no second vendor for the messaging leg of an omnichannel journey. |
| Native AI voice & chat agents | AI voice agents answer and resolve calls in the ACD queues human agents work, and AI chat agents handle SMS, WhatsApp, and web-chat conversations in the same inbox — a native layer, not a bolt-on product. |
| One SLA and one bill across all of it | One published uptime commitment — 99.0% on Pay-as-you-Go to 99.99%+ on Enterprise — across every channel, metered onto one pay-as-you-go invoice with published per-country rates. |
| Developer API + working console together | A documented REST API with SDKs for builders and a dashboard — queues, inbox, wallboards, flows — for operators, on the same account and the same data. |
| Built-in contact center | ACD queues, skills-based routing, live wallboards, and dispositions run in the same account, so an AI agent can resolve a call in the queue and a human picks up the same thread. |
Who runs this evaluation
Consolidate a stitched communication stack
Replace a carrier contract, a messaging API, and a separate AI builder with one account — one integration, one bill, one accountable party for quality and support.
Evaluate a vendor before committing
Apply the need-to-know checklist to short-listed providers before your engineering team commits: network ownership, one SLA, native AI, one published-rate bill, one timeline.
Put AI in front of every channel
Have AI voice agents front your inbound calls and AI chat agents answer SMS and WhatsApp, with a human queue behind both — inside the platform, not integrated to it.
The checklist applied: Orbit vs a reseller vs a stitched stack
| Factor | Orbit | Reseller PaaS | Stitched stack |
|---|---|---|---|
| What must be true underneath | |||
| Owned carrier-of-record voice network | |||
| One SLA across every channel | |||
| Native AI agents in queue and inbox | |||
| One pay-as-you-go bill, published rates | |||
| One customer timeline across channels | |||
| API + console in one account | |||
Comparison reflects the categorical shape of each model as of Q3 2026 — an owned carrier-of-record platform, a typical reseller platform, and a multi-vendor stitched stack. Individual providers may differ; the checklist above is the test to apply. Yes Partial No
Platform as a service — frequently asked
- What is platform as a service for business communications?
- Platform as a service (PaaS) in communications — usually called CPaaS — means a provider runs the voice network, messaging channels, AI agents, and contact center as one hosted product you consume from your own application, instead of carrier contracts and channel vendors you integrate yourself. What separates a real PaaS from a stitched stack wearing the label: the provider owns the network the calls terminate on, one SLA covers every channel, the AI layer is native inside the queues and inbox, and one pay-as-you-go bill carries the whole surface at published rates. Orbit by Devotel passes all four; providers reselling another platform's network or selling AI as a separate product fail them.
- What should a business check before choosing a communications PaaS?
- Six things, and each is a yes/no question you can put to any vendor: does the provider own the network or resell someone else's; is there one SLA across every channel or one per channel; are the AI agents native or a bolt-on product; does one published-rate bill cover everything; can developers use the API while operators use the console on the same account; and does one customer timeline span every channel? A provider that answers any of these with a qualification has handed you the integration work a PaaS is supposed to remove.
- How is a platform as a service different from buying one channel API?
- One channel API puts you back in the integration business: you still contract a voice carrier, operate a messaging provider, and find an AI product separately — then own the seams between them. A PaaS removes that by running the channels as one product, so the evaluation becomes whether the provider genuinely owns the network, SLA, AI, and billing underneath the label. The distinction matters most when a second channel or an AI agent enters the scope, which is when stitched stacks stop scaling.
- Why does carrier-of-record network ownership matter in a PaaS evaluation?
- Because whoever owns the network your calls terminate on owns your voice quality, deliverability, and STIR/SHAKEN signing. Orbit terminates every voice leg on Devotel's own wholesale carrier-of-record softswitch — interconnected with 500+ voice aggregators and mobile operators — so there is one accountable party for the call. A reseller PaaS passes every quality issue up to a second provider you cannot see, which is the single most expensive thing to discover after committing.
- Do AI agents belong inside the PaaS or as a separate product?
- Inside the PaaS, natively. The first job AI does in a communication stack is answer and resolve calls and chats inside the queue your human agents work — which is only possible when the AI layer reads the same queues, inbox, and customer timeline as the rest of the platform. Orbit's AI voice agents run in the same ACD queues and AI chat agents in the same inbox as human agents; buying AI as a separate product re-opens the integration a PaaS is supposed to close.
- Can I migrate off my current provider without re-building?
- The migration question is why the PaaS shape matters: when the voice, messaging, and AI surfaces are one product, consolidating onto one account is a supplier change, not a re-architecture. Orbit's SDKs and documented REST API map to the calls a business already makes against a Twilio-style stack, and number porting brings the existing DIDs over — but the durable win is the one after: every future channel becomes a toggle on the account, not a new procurement cycle.
Explore more
Build on a platform that passes its own checklist
The PaaS evaluation ends where the checklist passes — owned carrier-of-record voice, native AI agents, one SLA, and one pay-as-you-go bill across every channel. Start free, or talk to our team about your stack.