Contact us
Get started
Contact us
Log in

Manifesto

From UCaaS to
Conversational OS

Why we’re changing how we describe what we build — and why it matters for operators.

For the last decade, “UCaaS” has been useful shorthand for what platforms like Telavox do: cloud-delivered voice, messaging, video, and collaboration in one place. It made our offering legible to buyers, comparable to alternatives, and easy to slot into RFPs.

It’s served us well. It’s also reaching its limits.

The Shift

Telavox Conversational OS

When an operator asks what Telavox really is today, the honest answer isn’t “another UCaaS suite.” The system we’ve been building has grown beyond what UCaaS describes — and the way we and our operator partners go to market needs to catch up.

So we’re making the shift explicit. Starting today, the way we describe the platform is:
  • Telco-native core.
  • Workflow-led outcomes.
  • Human-centric workspace.

This isn’t a rebrand. It’s a more precise description of the system we already ship — and an acknowledgment that the category buyers are evaluating us in has moved on.

Market Context

What's changing in
business communications

Three shifts are happening at once, and none of them fit neatly inside
the UCaaS frame.

Conversations are becoming an interface, not just a channel.

A customer call used to be a transaction that ended when the call ended. Now it’s the start of a CRM update, a ticket, a payment, a follow-up email, a coaching note. The value of a conversation no longer lives in the conversation itself — it lives in what the conversation triggers across the rest of the business.

AI is collapsing the gap between conversation and action.

Real-time transcription, intent detection, automated summaries, and agentic harnesses are turning conversations into structured business events. The platforms that win the next decade won’t be the ones that bolt AI onto a UCaaS stack — they’ll be the ones where intelligence and infrastructure are designed together from the start.

Operators have a window that won't stay open.

Hyperscalers and pure-play SaaS communication vendors are circling enterprise communications, but they don’t have what operators have: numbers, mobile, FMC, regulatory presence, sovereignty, and direct customer relationships. The question for the next 3–5 years is whether operators package those assets into something strategic, or watch them get commoditized while someone else owns the workflow layer above them.
UCaaS as a frame doesn’t capture any of this. It describes a bundle of features. The buyer, and the operator partner who’s selling to that buyer, needs language for an architecture.

Market Context

What Conversational OS
actually means

A Conversational OS is the layer that connects business conversations across every channel and surfaces them as structured, actionable events inside the systems where work happens.
At Telavox, we think of it in three layers, with operator commercial control running across all of them.

The telco-native core.

The operator-grade communication foundation: voice, mobile, numbers, SIP, FMC, provisioning, billing, security, white-label control. This is where operators hold a defensible position — and it’s the part of the stack consumer-facing AI players and pure-SaaS vendors structurally can’t replicate. Most platforms treat this as infrastructure to abstract away. We treat it as the source of operator differentiation.

The workflow-led outcomes layer.

Where conversations become part of how customers actually work — one-click integrations, APIs, webhooks, real-time data streaming, a unified context layer that makes conversations available to the rest of the business. Communication used to run in a parallel track to the rest of work. In a Conversational OS, it’s part of the workflow itself.

The human-centric workspace.

The visible product — the web and mobile apps where business users work with conversations every day. AI Assist. AI Receptionist. Phone system. Collaboration. Omnichannel. Analytics. Its job is daily adoption: a workspace people actually return to, which is what makes product-led growth compound for operators selling into business accounts.

Cutting across all three: operator control and growth — partner tooling, BSS integration, packaging, white-label delivery, and product-led expansion that make this commercially scalable for operators selling to their own business customers.

The architecture is the offer. Not a feature list. Not a roadmap promise. A description of what we ship today, and a clear direction on where it goes next.

For Operators

Why this matters for
operators specifically

Operators have been asked for years to compete in business communications by offering hosted PBX or UCaaS to their business customers. The math has been hard — margins compress, differentiation is thin, and the customer relationship sits with whatever app the end user opens every day, which often isn’t the operator’s.

A Conversational OS changes the underlying economics in four concrete ways:
It differentiates beyond connectivity. The pitch to business customers stops being about minutes and seats. It becomes a strategic communications layer under the operator’s own brand, with AI and automation built in.
It opens growth inside existing accounts. When the workspace gets used daily, expansion compounds through adoption — the growth model stops depending entirely on how many quotes the sales team can push out each quarter.
It deepens customer ownership. The operator’s relationship extends from the network into the customer’s daily workflows — a much harder relationship to displace.
It creates a credible path into AI and automation that doesn’t require operators to bet on an AI startup, sign a hyperscaler agreement on someone else’s terms, or build the stack themselves. The intelligence lives inside a system they can deliver, support, and bill for under their own brand.

Where We Stand

What we are not claiming

A category doesn’t get earned in a single announcement, and we know that.

Some parts of this architecture are world-class today — the telco-native core is, and so is the white-label commercial model. Other parts are maturing: the workflow layer is expanding fast, and the AI capabilities are real and shipping, with meaningful work still ahead.

Conversational OS isn’t yet a finished story. It’s the right frame for the system we’re building — and the honest one for what operators need from a platform partner over the next five years.

What's next

Over the coming weeks we’ll be sharing how the architecture maps to specific use cases for telcos and MVNOs, what we’re prioritizing in 2026, and how our operator partners are already building inside the new frame. We’ll also be in conversation with analysts and operators across Europe.

If you’re at a European operator or MVNO and want to engage on this directly, the conversation is open.
Viktor Karlsson
Chief executive officer · Telavox