What is CCaaS (contact center as a service)?

The "as a service" part describes who owns and maintains the system. NICE's CCaaS glossary entry says the provider "hosts, maintains, updates, and secures the platform," and the customer adds users, channels and capacity as needs change. In an on-premises contact center the company is responsible for that work. AWS's overview of CCaaS describes the older model as PBX and ACD hardware bought up front, maintenance and upgrades handled by the organization, and growth that often means adding physical resources. We compare the two models in how CCaaS differs from an on-premises contact center.

The design of the service stays with you. You still decide your hours, which calls go to which team and what the menu says. The provider supplies the tools for those decisions and keeps them running.

Atlantech's contact center service shows what that split looks like to a buyer. Atlantech delivers the contact center platform from the cloud, and it says it keeps an eye on that platform and maintains it remotely. A new customer starts with a discovery call of 15 to 30 minutes and then receives a quote. Once the quote is approved, Atlantech aims to finish the implementation in 30 to 45 days.

The parts are easiest to see by following one call. It arrives on your phone number, and an IVR, the recorded menu, asks what the caller needs. The answer places the call in a queue. An automatic call distributor then picks an agent according to routing rules you set. The agent answers in a desktop or web app, with the caller's customer record on screen if a CRM is connected. The call can be recorded, and supervisors can watch wait times live and pull reports later.

Each of those steps is a component you are renting. Atlantech's feature list covers the same ground: voice and web chat licenses, an IVR, skills-based routing, queue callback, real-time wallboards, supervisor control, historical reporting and CRM integrations. Larger platforms add tools around that core. NICE lists AI, analytics and workforce management, which covers forecasting and agent scheduling, among the parts of a modern platform.

Genesys describes CCaaS as a way to bring "voice, chat, email, SMS and social media within one interface." Which channels you get depends on the package. Atlantech's page names voice and web chat. Genesys describes its Cloud CX 1 plan as "for voice contact centers" and its Cloud CX 2 plan as "for omnichannel contact centers." How one set of rules routes several channels to the same agents is covered in what a unified queue is.

Providers charge by different units, so two prices can't be compared until you know the unit behind each one.

A named license belongs to one person. Genesys lists $155 per user per month, billed annually, as the named-user price for Cloud CX 3, and the same page offers concurrent and hourly license types. A concurrent seat is shared by whoever is signed in at the moment. Five9 sells its Core bundle at $159 per concurrent seat per month, with a 50-seat minimum.

Suppose a contact center employs 100 agents across two shifts and never has more than 60 signed in at once. On concurrent seats it licenses 60, which comes to $9,540 a month at Five9's rate. On named licenses it pays for all 100 people, which comes to $15,500 a month at the Genesys rate. The two plans don't include the same features, so the comparison says nothing about which vendor is the better buy. It shows how much the unit matters for a team that works in shifts.

A third model has no seats. Amazon Connect charges $0.038 for each minute of a voice call, plus telephony, so the bill follows call volume instead of headcount.

After the unit, check what the plan includes. Genesys describes Cloud CX 3 as the plan "with full WEM capabilities," its term for workforce engagement management. A team that needs those tools should compare quotes at that level, because a lower plan can cost more once the missing pieces are added.

Atlantech prices its service by quote and does not publish a per-seat rate. Its service runs on Xima, and the Xima feature matrix published for service providers lists concurrent agent licensing on all three of its packages. The minimum is five seats on the two lower packages and ten on the top one. Atlantech's quote sets the actual terms, so confirm the unit and the minimum on the discovery call.

The three names describe different jobs. RingCentral describes UCaaS as employee voice, video meetings, team messaging and SMS in one subscription. NICE draws the line with CCaaS by audience: CCaaS "manages customer-facing communications, while UCaaS primarily manages communications and collaboration among employees."

CPaaS is the odd one out because it is not a finished application. Twilio describes CPaaS as APIs and software development kits that put calling and messaging inside a business's own apps.

Many companies run UCaaS and CCaaS side by side. Atlantech sells them as separate services, and that matches the typical split. Company-wide calling and messaging run on UCaaS, which can include auto attendants and basic call queues. The deeper routing, supervision and reporting of a contact center are licensed for the agents who work the queues. We cover the full comparison in the difference between CCaaS, UCaaS and CPaaS.

Agents who use a browser or softphone reach the platform over an internet connection. NICE notes that cloud access is what lets a CCaaS platform support remote, hybrid and distributed teams. For those agents it also puts the connection in the path of each call. The usual causes of trouble are covered in common UCaaS call quality problems. Check each agent's connection before their first live shift, because a weak home or office link can show up as choppy audio on customer calls.