Request a quote
Emergency SectorsCareers About us Blog Get in touch
Service desk agent with a headset and a pen in hand at a desk with laptops

CCaaS: when the queue in your phone system is no longer enough

CCaaS (contact centre as a service) is contact centre software that runs in the cloud and is licensed per agent. The question is rarely whether it works, but whether you need it: plenty of customer service teams run perfectly well on the call queue in their cloud phone system or in Teams. This article explains where that queue stops and a contact centre begins, and what to arrange if you make the move.

6 min read Written by the ITproposal team
Short answer

A call queue lets calls ring in a group. A contact centre decides who gets the call, shows who is calling and measures how long people wait.

Whether you need CCaaS comes down to four questions: how many people answer at once, which channels you serve, whether you report on waiting times and whether callers need to be recognised.

The platform belongs to a third party, and numbers and call minutes stay with your carrier. We set up the agent desks, the network and the integrations.

What CCaaS does that a call queue does not

Almost every cloud phone system, and Microsoft Teams too, has a call queue: incoming calls ring a group, the caller hears music and a message, and after a while the call goes to voicemail or another group. For a reception desk or a small team that is enough, and it is often already included in what you pay for.

A contact centre starts where the question shifts from “let it ring” to “who should take this call, and how well are we doing”. What CCaaS adds:

  • Skills-based routing. A call goes to the agent who speaks the language, knows the product or helped this customer before, not to whoever happens to be free.
  • Several channels in one queue. Phone, chat, email and messaging reach the same people, with one history per customer.
  • An agent desktop with customer data. Whoever answers already sees who is calling and what they were in touch about last time.
  • Supervision and reporting. See live how many people are waiting, listen in or bring in a colleague, and afterwards get figures on waiting time, abandoned calls and handling time.
  • Recording, quality and planning. Record and review calls, and plan staffing against expected demand.

When the queue in your phone system is enough

The most expensive mistake is buying a contact centre platform for a problem that sits in how the phone system is set up. So ask four questions first.

  • How many people answer at the same time? A handful of colleagues who can see and hear each other gain little from clever routing.
  • Does anything come in besides phone calls? If chat and a shared mailbox work well, they do not need to share a queue.
  • Do you have to account for waiting times? To your board, to customers with a contract or to a client. Then you need figures per hour and per channel that you can show.
  • Does a caller need to be recognised? If customers give their account number every time and agents look up their history by hand, both sides lose time.

If the answers are mostly no, you get more from a better configured cloud phone system: clear groups, a callback option, opening hours that are right and a weekly report. If they are more often yes, CCaaS starts to make sense.

Channels: one queue for phone, chat and email

The gain from several channels on one platform is not the number of channels but the history. A customer who emails first and then calls reaches someone who can already see the email. Without that, they tell their story again.

Two traps come up often:

  • Opening channels without staffing them. A chat button on the website promises a quick answer. If nobody is behind it, the experience is worse than a phone number with opening hours.
  • Giving every channel the same expectation. A caller waits seconds, a chat user minutes and an emailer hours. Agree per channel what “on time” means and set the routing to match.

Messaging channels such as WhatsApp have their own business account and terms, separate from the contact centre platform. Register that account in your organisation’s name so it does not leave with the platform if you ever switch.

Integrations with your CRM and ticketing system

The agent desktop is only useful if it knows who is calling. That almost always runs through an integration with your CRM or ticketing system, and that is where most of the work is.

  • Recognition by number. The platform looks up the caller’s number and opens the customer record. That only works if numbers are stored in the same format everywhere, with the country code, and if you know what happens when two contacts share one switchboard number.
  • Automatic logging. Every call lands in the customer history with time, duration and agent, without anyone retyping it.
  • Click to dial. Calling back from the CRM, so outbound calls are logged too.

For each integration, ask whether it is a standard connector from the vendor or custom work, and who maintains it when the CRM or the platform is updated. An integration that quietly stops after an update only shows when agents start searching by hand again.

The agent’s desk: headset, network and home working

A cloud contact centre usually runs as a softphone in the browser or an app. That makes the desk simple and sensitive at the same time: every hiccup in the network is something the customer hears.

  • The headset decides what the customer hears. A good headset with noise cancellation does more for call quality than any setting. Standardise on one model so you have spares and know it well.
  • The network gives voice priority. In the office with QoS on switches and wifi, and a cable where possible. A connection saturated by a large upload is heard straight away in a call.
  • Home-based agents call over their own broadband. Agree the minimum they need and how to tell whether a problem is the home connection, the headset or the platform.
  • Sign-in with their own account. Through your identity platform with MFA, so a leaver is removed everywhere in one step.

Choosing CCaaS: what to ask and what drives the price

In a demo the platforms look alike. The differences are in what is included as standard, where your data lives and how you get out again later.

  • What is in the base licence and what is an add-on? Recording, workforce management, quality scoring and transcription are often separate.
  • Where are calls, recordings and transcripts stored? In which region, for how long, and who at the vendor can access them.
  • How do calls come in? Through your own carrier and numbers, or through minutes the platform supplies itself. That decides what happens to your numbers if you switch.
  • How do you leave? Can you export recordings, interaction history and reports in a usable format, and how quickly.

What drives the price is much the same across vendors: the number of agents and whether you pay per named or per concurrent user, the number of channels, the add-ons you take, how long you keep recordings, and the call minutes, which run through your carrier.

Call recording, UK GDPR and your staff

Recording is one switch technically and a decision legally. A recording is personal data, of the caller and of your agent. Decide in advance what you record for (training, evidence of an agreement, complaints), how long you keep it and who can access it. Tell callers the call is recorded, for example in the welcome message. In the UK the ICO’s guidance is the place to check how this applies to you.

For your staff there is more: a system that logs their calls, waiting times and handling times per person is monitoring at work. Be open with your team about what is measured and why before the platform goes live, not after.

If you use transcription or AI summaries, ask where that processing happens and whether the vendor uses your calls to train its own models. Have the whole arrangement reviewed by your data protection lead or a lawyer.

Where our work stops

We do not supply call minutes, line rental or phone numbers. Those stay with the carrier you choose, and the contact centre platform itself belongs to a third party: a software vendor with its own terms, licences and service levels. We do not own it and do not decide how the product develops.

What we do: configure the platform to your routing, integrate it with your telephony, CRM and identity platform, provide the agent desks with headsets, the network underneath and the support afterwards. How your customer service works, your opening hours and what your agents say remain yours; we make sure the system carries it out.

Frequently asked

Questions we get about this

The five that come up most often.

What is CCaaS?

CCaaS stands for contact centre as a service: contact centre software that runs in the cloud and is licensed per agent. On top of an ordinary call queue it adds skills-based routing, several channels in one queue, an agent desktop with customer data and reporting on waiting times. You do not have to run your own servers for it.

What is the difference between a call centre and a contact centre?

A call centre handles phone calls. A contact centre serves several channels at once, such as phone, chat, email and messaging apps, with one history per customer. In practice the terms are used interchangeably; the real question is which channels your customers actually use.

Can Microsoft Teams be a contact centre?

Teams has its own call queues and auto attendants, which are enough for a reception desk or a small team. For skills-based routing, more channels and detailed reporting you connect a contact centre platform to Teams. Your agents keep working in Teams while the platform handles the distribution.

What determines the cost of CCaaS?

The number of agents and whether you pay per named or per concurrent user, the channels and add-ons you take, such as recording, workforce management and transcription, and how long you keep recordings. Call minutes come on top, through your carrier.

Do you supply the platform and the call minutes as well?

No. The contact centre platform belongs to a software vendor, and call minutes, line rental and numbers stay with your carrier. We configure the platform, integrate it with your telephony and CRM, and supply and support the agent desks and the network underneath.

Related services

Further reading

What a contact centre connects to.

Is the queue enough, or is it time for a contact centre?

Tell us how many people answer, through which channels and what you cannot see today. We will tell you honestly whether your phone system will cope with better configuration, or whether a contact centre is the next step.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call