> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# UCaaS, CCaaS, and CPaaS

> How the three cloud-communication categories differ — the phone system for employees, the contact-center suite, and the programmable API layer — and how Orbit maps to each

# UCaaS, CCaaS, and CPaaS

Three acronyms describe communication delivered from the cloud, but they
equip different audiences:

* **UCaaS** (Unified Communications as a Service) — a packaged cloud phone
  system, meetings, and team chat that a company turns on for its employees.
  Per user, per seat, per month.
* **CCaaS** (Contact Center as a Service) — the software a support or sales
  team uses to route, handle, and measure customer conversations. Per agent
  seat, per month on the incumbent platforms.
* **CPaaS** (Communications Platform as a Service) — the programmable
  communication APIs (voice, SMS, WhatsApp, email, video, AI voice agents)
  that developers build into their own product. Usage-metered, per minute
  and message.

## TL;DR

UCaaS equips every employee, CCaaS equips the contact-center team, and
CPaaS equips your software. On Orbit all three ship on a single account —
a built-in contact center, a UCaaS phone system, and the full programmable
channel set on one usage-based bill.

## What CCaaS is

CCaaS is the contact-center suite. Its components, stated one level below
the acronym:

* **ACD (automatic call distribution)** — routes each inbound conversation
  to a queue and then the best available agent, by skill or attribute.
* **IVR (interactive voice response)** — the menu that greets the caller,
  collects intent by keypress or speech, and hands routing context to the
  ACD.
* **Omnichannel routing** — one queue discipline across voice, SMS, chat,
  WhatsApp, and email, so the agent sees the whole conversation regardless
  of channel.
* **WFM and quality** — forecasting and scheduling the team, recording and
  scoring conversations, coaching agents against the recordings.

The historical commercial shape of CCaaS is *per-seat licensing* — each
agent is a named monthly seat, and the incumbent platforms
(Genesys, NICE CXone, Five9, Talkdesk) frequently quote AI and analytics as
separate add-ons on top of the seat.

## How it differs from UCaaS and CPaaS

| Dimension   | UCaaS                          | CCaaS                            | CPaaS                                              |
| ----------- | ------------------------------ | -------------------------------- | -------------------------------------------------- |
| Equips      | Every employee                 | The support / sales team         | Your developers' product                           |
| Core        | Cloud PBX, meetings, team chat | ACD, IVR, queues, WFM/quality    | Voice, SMS, WhatsApp, email, video APIs, AI agents |
| Consumption | Provision + configure          | License seats + configure queues | Integrate an API                                   |
| Billing     | Per user, per month            | Per agent seat, per month        | Per minute / message / call                        |

## The three categories on Orbit

Orbit treats the three categories as surfaces of one account, not three
purchases:

* **The contact center (CCaaS)** ships built in — an omnichannel agent
  inbox, an IVR feeding skills-based queues, supervisor wallboards — billed
  pay-as-you-go rather than per seat. See the queues and routing under your
  tenant's Messaging + Voice surfaces.
* **The UCaaS phone system** ships beside it — a softphone, queues, and an
  auto-attendant on the same numbers.
* **The CPaaS channels** are the programmable layer the whole thing sits
  on — `voice`, `messages`, `email`, and `video` APIs plus AI voice agents.

Every outbound voice leg terminates on Devotel's wholesale softswitch, so the
contact center, the phone system, and the API all carry on the same
carrier-of-record network.

## When you outgrow per-seat CCaaS

A per-seat contact-center suite fits while agent count tracks conversation
volume. The shift to a usage-based, unified account happens when:

* AI voice agents absorb the routine conversations but the human tier,
  the AI rider, and the WFM modules all still bill per seat.
* Your product — not just the agent desk — needs to place calls or send
  messages, which a seat license cannot deliver.
* The contact-center suite's channel ceiling forces the messaging and email
  surfaces onto a second vendor and a second contract.

At that point the bridge is Orbit's built-in contact center beside the
programmable channels on one bill.