How the Orbit omnichannel platform works — architecture, end to end
The architecture, answered up front
Devotel Orbit's omnichannel platform is one integrated stack, not channels bolted onto each other: every outbound voice call and every outbound SMS terminates on Devotel's own wholesale carrier-of-record softswitch (500+ global interconnects); one orchestration layer routes conversations across voice, SMS, WhatsApp, email, and chat onto a single per-customer timeline; and AI agents inject into that same stack — answering calls and replying to messages with a streaming speech-to-text/LLM/text-to-speech pipeline, grounded in your knowledge base, with human handoff into the same queues and inbox. The alternative — a stitched stack of independent vendors — fails the integration test by construction: the media, the messaging state, and the agent logic live in different systems you integrate yourself.
From API call to ringing phone, end to end
Every request — an outbound call, an SMS, a WhatsApp template, an AI agent picking up a conversation — traverses this same five-layer stack on Orbit. A provider that hides any layer behind a reseller hop hands you the failure to diagnose.
1.The carrier-of-record termination layer
Every outbound voice call and every outbound SMS exits the platform over Devotel's own wholesale carrier-of-record softswitch, interconnected with 500+ global aggregators and mobile operators. Quality, caller-ID integrity, and delivery receipts trace to that one accountable party instead of a reseller passing issues up to a second provider you cannot see.
2.The omnichannel orchestration layer
Channels — voice, SMS, WhatsApp, email, and web chat — are routed onto one per-customer timeline. A call, a text, and a chat session stay one conversation, so an AI agent or a human agent reads and writes the same record and the same consent state per channel.
3.The agent-runtime AI layer
AI agents inject into the same stack as a first-class pipeline: a streaming speech-to-text, LLM, and text-to-speech loop with barge-in for voice, knowledge-grounded retrieval over your uploaded documents, and registered tool calls into your own systems mid-conversation — not a separate product bolted on.
4.The human handoff layer
When a conversation needs a person, the AI agent escalates into the same ACD queues and the same inbox human agents already work, with the transcript and post-call synthesis attached — so a conversation moves between AI and human without leaving the platform.
5.The single account, bill, and SLA
Voice, messaging, and AI agents all run under one account, one pay-as-you-go bill with published per-country rates, and one uptime SLA — the consolidation the integration shape above is supposed to deliver, instead of three invoices and three status pages to reconcile.
The seven integration decisions
Settle each of these with every platform you weigh — including us. A provider that answers any of them with a qualification has handed you the integration work the platform is supposed to remove.
1.Decide whose network the outbound traffic terminates on
Voice quality, SMS deliverability, and compliance signing trace to whoever owns the softswitch. Orbit terminates every outbound voice leg and every outbound SMS on Devotel's own wholesale carrier-of-record softswitch — interconnected with 500+ aggregators and mobile operators — so one accountable party owns the send instead of a reseller you cannot see.
2.Route every channel onto one conversation timeline
The point of omnichannel is that a call, a text, and a chat form one conversation. Orbit routes voice, SMS, WhatsApp, email, and web chat onto one per-customer timeline, so a human agent picking up a call sees the thread that preceded it, and the AI's post-call synthesis lands in the same place.
3.Inject AI agents into the same pipeline, not a separate product
An AI agent bolted on as a third vendor re-opens the integration the platform is supposed to close. Orbit's agent runtime is a first-class pipeline on the same stack — a streaming STT/LLM/TTS loop with barge-in for voice, knowledge-grounded retrieval, and mid-conversation tool calls into your own systems.
4.Ground the agent's answers in your knowledge
An agent answering from a model's general knowledge invents policy. Orbit grounds responses in your uploaded documents and business rules through retrieval, with per-tenant isolation, so the agent quotes your own rules instead of improvising.
5.Keep human handoff inside the same queues and inbox
The first job of an AI agent is answering and resolving in the queue human agents already work, then escalating with context. Orbit runs AI and human agents in the same ACD queues and the same inbox, with the transcript attached — a separate AI product re-opens the integration work.
6.Keep one consent ledger across every channel
Consent that lives per channel is a compliance gap waiting. Orbit keeps every channel's opt-in and opt-out state on the same contact record, so a STOP from any channel applies across the journey, not per channel.
7.Demand one account, one bill, one SLA across the stack
A stitched stack bills and meters each vendor separately. Orbit meters voice, messaging, and AI agents onto one pay-as-you-go invoice with published per-country rates, and one uptime SLA covers all of it.
What Orbit ships in the stack
| Capability | What you get |
|---|---|
| Carrier-of-record network for voice and SMS | Inbound and outbound calls and SMS run on Devotel's own wholesale carrier-of-record softswitch interconnected with 500+ global aggregators and mobile operators — one accountable owner controls routing, caller ID, and deliverability end to end. |
| Real-time AI voice and chat agents, natively in-platform | Speech-to-text, an LLM reasoning layer, and text-to-speech run as a streaming loop targeting about a second per conversational turn, with barge-in — a native layer in Orbit's agent runtime, not a bolt-on product. |
| Knowledge-grounded answers and mid-conversation tool calls | Agents answer from your documents and business rules via retrieval with per-tenant isolation, and call registered tools against your own systems mid-conversation — look up an order, check a slot, create a ticket. |
| Human handoff into the same queues and inbox | The AI agent escalates into the same queues and inbox human agents already work, with the transcript and post-call synthesis attached — and squad handoff keeps context across conversations. |
| One consent state, one timeline, one bill | Opt-in and opt-out live on one contact record across channels, one per-customer timeline spans voice and messaging, and one uptime SLA meters everything onto a single pay-as-you-go invoice with published per-country rates. |
Where the integration pays off
Front every inbound call with an AI agent
Let the voice AI agent answer first, resolve account and order questions from your knowledge base, and hand off the calls that need judgment — with the transcript already in the human agent's inbox.
Follow up on the channel customers answer
Move confirmations, reminders, and recovery to SMS or WhatsApp utility templates where a call would not land, from the account that owns the number, the consent state, and the timeline.
Replace a stitched vendor stack with one platform
Consolidate a standalone voice carrier, a messaging BSP, and a separate AI vendor onto one account — one integration, one bill, one accountable party for delivery, quality, and support across every channel.
Integrated platform vs a stitched vendor stack
| Integration check | Orbit | Stitched stack |
|---|---|---|
| The integration checklist, applied | ||
| Outbound voice and SMS on an owned carrier-of-record network | ||
| AI agents inside human queues and inbox | ||
| Knowledge-grounded answers and mid-conversation tool calls | ||
| One consent ledger across every channel | ||
| One conversation timeline an AI engine and a human both read | ||
| One SLA and one pay-as-you-go bill across the stack | ||
Comparison reflects the categorical shape of each model as of Q3 2026 — an integrated omnichannel platform versus independent voice carrier, messaging BSP, and AI vendor stitched together. Individual providers may differ; the checklist above is the test to apply. Yes Partial No
How the platform works — frequently asked
- How does an omnichannel communications platform actually work?
- As one integrated stack, not channels stitched together: outbound voice and outbound SMS terminate on a carrier-of-record softswitch; an orchestration layer routes voice, SMS, WhatsApp, email, and chat onto one per-customer timeline; and AI agents inject into the same pipeline to answer calls and messages, with human handoff into the same queues and inbox. Devotel Orbit passes that checklist on one account; a stitched vendor stack fails the integration facts by construction.
- What does "carrier of record" mean for a platform?
- It means the platform terminates traffic on its own wholesale softswitch instead of reselling a second provider's network. Orbit terminates every outbound voice and SMS leg on Devotel's own wholesale carrier-of-record softswitch — interconnected with 500+ aggregators and mobile operators — so quality, caller ID, and delivery receipts have one accountable owner.
- Where do AI agents fit in the architecture?
- Inside the same stack, not beside it. Orbit's agent runtime runs as a first-class pipeline on the platform: a streaming speech-to-text/LLM/text-to-speech loop with barge-in for voice, knowledge-grounded retrieval, tool calls into your own systems mid-conversation, and escalation into the same queues and inbox human agents work.
- Why is one conversation timeline across channels important?
- Because omnichannel only pays off when a call, a text, and a chat form one conversation. Orbit routes every channel onto one per-customer timeline, so an AI agent or a human agent reads the thread that preceded a call and the AI's post-call synthesis lands in the same record — instead of reconciling two vendors' timelines.
- What does the stitched-stack alternative actually fail?
- By construction, the integration facts: the media network, the messaging state, the consent ledger, and the agent logic each live in a different vendor's system you integrate yourself — and the failure modes are owned by you, not one accountable party.
Explore more
See one integrated platform answer the checklist
Voice AI agents that answer calls natively in your queues, outbound voice and messaging carried on Devotel's own carrier-of-record network, and one pay-as-you-go bill across the stack. Start free, or talk to our team about your rollout.