What is cloud telephony? VoIP, PBX and CPaaS explained

The short version

Cloud telephony means your phone system runs on somebody else's servers and reaches you over the internet, instead of running on a box in your building connected to phone lines. Numbers, routing, voicemail, menus and recording all become software.

The practical consequences are the ones that matter: no hardware to buy or maintain, numbers in countries you have no office in, capacity that changes in minutes rather than weeks, and a phone system that other software can talk to.

The acronyms, in the order they make sense

VoIP — Voice over Internet Protocol. The underlying method: audio is digitised, split into packets and sent over IP networks. Everything below is built on it. VoIP is a transport technology, not a product.

Hosted PBX — a private branch exchange, the thing that routes calls inside an organisation, running in the cloud rather than on-site. Extensions, transfers, hunt groups, voicemail. This is what most small businesses mean by a cloud phone system.

UCaaS — Unified Communications as a Service. Hosted PBX plus messaging, video and presence in one product. The Microsoft Teams and Zoom end of the market.

CCaaS — Contact Centre as a Service. Built for queues rather than extensions: skills-based routing, wait-time management, agent occupancy, supervisor monitoring, quality management. What you buy when volume is inbound and high.

CPaaS — Communications Platform as a Service. Not a phone system at all, but APIs — Telnyx, Twilio, Plivo, Bandwidth and similar — that let software place calls, send messages and manage numbers programmatically. This is the layer most modern sales tools sit on.

The distinction that trips people up is the last one. When a CRM says it has calling built in, it usually means it is built on CPaaS. The interesting question is then whether you use their carrier account or your own.

What actually happens when you place a call

Worth understanding because it explains most of the failure modes:

1. Signalling. Your client tells the platform to set up a call, usually over SIP. This negotiates who is calling whom and which audio codecs both ends support.
2. Routing. The platform decides how to reach the destination — over the internet to another VoIP endpoint, or handed to a carrier that connects to the traditional telephone network.
3. Media. Audio flows, typically over RTP, often on a different path from the signalling. This is why a call can connect and then have no sound: signalling succeeded, media did not.
4. Presentation. The receiving network decides what caller ID to show and, increasingly, whether to label the call as spam. In the US, STIR/SHAKEN attestation influences this heavily.

Step four is where most outbound calling problems now live. A technically perfect call that arrives labelled as suspected spam is a call nobody answers.

Caller ID, spam labelling and why connect rates fall

Carriers now score calls, and a number that generates short-duration calls, high rejection rates or complaints gets labelled. The label follows the number, and reputation recovers slowly.

Three things help, in order of effect:

• Do not burn numbers. Calling patterns that look automated attract labelling. Rotating caller IDs spreads load, but rotation is not a fix for a pattern that shouldn't be running.
• Register properly. In the US, correct STIR/SHAKEN attestation from a carrier that knows you own the number materially affects presentation.
• Call at reasonable hours in the recipient's timezone. This is also a legal requirement in most places, and it happens to be the same behaviour that keeps a number's reputation intact.

What carrier pass-through means for your bill

Voice has a genuine marginal cost: carriers charge per minute for the connection to the telephone network. How a vendor handles that cost is one of the biggest differences between platforms and one of the least visible.

Bundled minutes. You pay a seat price including an allowance. Simple, predictable, and expensive at volume, since the vendor prices the bundle for the average customer rather than for you.

Resold minutes. The vendor buys wholesale and sells to you with margin. Usually cheaper than bundles and still a markup on a cost that scales directly with how much you call.

Pass-through. You bring your own carrier account and the vendor charges only a platform fee. You pay the carrier directly at whatever rate you negotiated.

Autocloz uses the third model: connect your own Telnyx, DIDLogic or FreJun account and those per-minute rates reach your bill unchanged, with no per-minute markup from us. At a few thousand dials a month the carrier line typically exceeds the software line, which is why the model matters more than the seat price.

The trade is real and worth stating: pass-through means you manage a carrier relationship — an account, a top-up, number provisioning. Bundled minutes are simpler, and for a team making a handful of calls a day the simplicity is worth more than the saving.

What to check before switching

Number portability. Can you bring your existing numbers, how long does it take, and is there a cost? Porting is standard but slow, and a business number you cannot move is a lock-in you did not price.

Emergency calling. VoIP handles emergency services differently from traditional lines, because the network cannot infer your location. Confirm how it is registered and keep the address current — this is a legal obligation in many jurisdictions.

Network requirements. Voice is sensitive to jitter and packet loss more than to raw bandwidth. Ask what the platform needs and check whether your network prioritises voice traffic; most cloud-telephony quality complaints turn out to be local networking.

Recording, consent and storage. Where are recordings kept, for how long, who can access them, and does the platform capture consent where your jurisdiction requires it? Recording law varies significantly, including between US states.

Where the outcome lands. If the phone system and the CRM are separate products, the call outcome, recording and next step have to travel across an integration you now own. Native telephony inside the CRM removes that seam — the argument for it is not features, it is one fewer place for data to diverge.

Do you need a phone system or a dialer?

Different products for different problems, and buying the wrong one is common.

A phone system is for receiving calls: numbers, menus, routing, voicemail, extensions. A dialer is for making them at volume: list management, dial modes, dispositions, connect-rate reporting.

Most sales teams need mostly the second with a little of the first — an inbound path for callbacks, but nothing resembling a support queue. Autocloz is built for that shape: a power dialer with click-to-call, an IVR builder for the inbound path, voicemail drops, agent presence and call reporting, inside a CRM the outcomes write to. Teams whose volume is genuinely inbound and queued should be looking at CCaaS instead.

More on dial modes in auto dialer vs power dialer vs predictive dialer, and on the platforms in best call center CRM.