"Hosted PBX", "VoIP" and "cloud PBX" are thrown around as if they mean the same thing. They overlap, but they answer different questions: VoIP is how calls travel, while a hosted PBX is who runs the phone system that manages those calls. Getting the distinction right matters because it drives what you pay, what hardware you need, and how resilient your phones are. This guide untangles the terminology in plain English and helps you decide what actually fits a UK business of your size.
VoIP, hosted PBX and cloud PBX: the terms untangled
VoIP — Voice over Internet Protocol — is simply the technology that carries phone calls as data over an internet connection instead of over the traditional analogue phone network (PSTN). Almost every modern business phone service is VoIP under the bonnet, especially now the UK PSTN is being switched off. So "VoIP" describes the transport method, not a specific product.
A PBX (Private Branch Exchange) is the system that manages your calls internally: routing, extensions, hunt groups, voicemail, auto-attendants and so on. Historically this was a physical box in a comms room. A hosted PBX moves that intelligence into a provider's data centre, delivered as a service over the internet — which is why it's also called cloud PBX or hosted telephony.
So the honest answer to "hosted PBX vs VoIP" is that they're not competing options at the same level. A hosted PBX uses VoIP to carry calls. The real choice is between different ways of delivering VoIP: a fully managed hosted PBX, a SIP trunk feeding your own on-premise PBX, or a basic app-only VoIP line.
- VoIP: the underlying technology that turns voice into data over the internet.
- Hosted / cloud PBX: a complete phone system run in a provider's cloud, using VoIP.
- SIP trunk: VoIP "lines" that connect an existing on-site PBX to the outside world.
- On-premise PBX: the call-management hardware kept in your own building.
When a hosted PBX makes sense vs plain VoIP
"Plain VoIP" usually means a lightweight service that gives you calling from an app or a single softphone, with minimal call-handling features. It's fine for a sole trader or a couple of remote staff who just need a business number and the ability to make and receive calls.
A hosted PBX makes sense the moment you need to route calls like a proper organisation: a main number that rings the right team, menus that direct callers, call queues for a busy sales or support line, voicemail-to-email, and consistent behaviour whether staff are in the office, at home or on mobiles. If people ask "can we transfer calls between departments?" or "can callers press 1 for accounts?", you've outgrown plain VoIP.
Most growing UK businesses land on a hosted PBX because it removes the need to buy and maintain a physical box while still giving enterprise-grade call handling. Our cloud hosted PBX approach is designed exactly for this middle ground — full features without on-site hardware to manage. If your team already lives in Microsoft Teams, a Teams phone system can deliver the same call handling inside the tool people use all day.
Is a hosted PBX just VoIP with extra features?
Broadly, yes — and that's a useful way to think about it. If VoIP is the dial tone, the hosted PBX is everything that makes a phone system feel professional: auto-attendants, ring groups, call recording, presence, reporting and centralised admin. The "extra features" are the whole point, because they're what a business actually buys a phone system for.
The distinction that trips people up is ownership of the call-routing brain. With a hosted PBX, that brain lives with the provider and is updated, patched and scaled for you. With a SIP trunk plus an on-premise PBX, you own the brain and the responsibility for keeping it running, licensed and secure.
There's no universally "better" option — it depends on control versus convenience. Businesses with heavy compliance needs, existing hardware investment, or specialist integrations sometimes keep an on-site PBX and simply modernise the lines with a SIP trunk. Everyone else tends to prefer letting the provider carry the operational load.
Costs, hardware and contracts compared
Cost is where the models genuinely diverge. A hosted PBX is typically billed per user per month, bundling the platform, features and often call allowances. There's little to no upfront capital outlay beyond handsets, and upgrades are included. That predictability suits businesses that want opex rather than capex.
An on-premise PBX with SIP trunks carries upfront hardware and installation costs, plus ongoing maintenance, licensing and eventual replacement. The per-minute or per-channel cost of SIP can be lower at high call volumes, which is why some larger, call-heavy operations still favour it. Plain app-only VoIP is usually the cheapest headline price but the thinnest on features and support.
Watch the small print regardless of model: number porting fees, minimum contract terms, whether handsets are bought or rented, and what happens to your numbers if you leave. Good business phone systems in London providers will let you keep your numbers and give clear porting timescales rather than locking you in.
- Hosted PBX: predictable per-user monthly cost, minimal upfront spend, upgrades included.
- SIP trunk + on-prem PBX: higher upfront capex, potentially lower call costs at scale, you own maintenance.
- App-only VoIP: lowest entry price, limited features and call-handling depth.
- Always confirm: porting fees, contract length, handset ownership and number retention.
Call handling, resilience and scaling
Resilience is often the deciding factor. A hosted PBX runs in redundant data centres, so if your office loses power or internet, calls can automatically fail over to mobiles or another site — the system itself keeps running. An on-premise PBX is only as available as your building and its single connection, unless you engineer expensive redundancy yourself.
That said, every VoIP-based system depends on your internet connection for quality and uptime. Jittery broadband produces choppy calls. This is why we advise treating connectivity and telephony as one project: a reliable leased line or well-designed SD-WAN with prioritised voice traffic does more for call quality than any feature list. Adding a backup connectivity line keeps phones working when the primary circuit fails.
Scaling favours the hosted model heavily. Adding users is usually a few clicks and a new licence, with no capacity limits to hit on a physical box. Seasonal teams, new sites and hybrid working are all handled without a site visit — a genuine advantage for multi-site or fast-growing UK businesses.
Choosing the right setup for your team size
For 1–5 people, plain VoIP or an entry hosted PBX plan is usually plenty: a shared main number, simple call forwarding and mobile apps. Don't over-buy features you'll never configure.
For roughly 5–50 people, a hosted PBX is the natural fit. You'll want auto-attendants, departmental queues, call reporting and the ability to add users without hardware headaches. If you're a Microsoft 365 organisation, integrating voice into Teams often removes a separate app entirely and simplifies admin.
For 50+ users, or businesses with existing PBX hardware, heavy call volumes or strict regulatory needs, the choice between a large hosted platform and SIP trunks into an on-premise system deserves a proper design conversation. Either way, connectivity and security should be scoped alongside the phones. If you'd like a straight recommendation for your headcount and sites, our team can assess it with you — get in touch and we'll map the options honestly.
The bottom line
"Hosted PBX vs VoIP" is a slightly false contest: VoIP is the technology, and a hosted PBX is the most common, feature-rich way to deliver it. The practical decision for most UK businesses is between a fully managed hosted PBX, SIP trunks into hardware you already own, and a bare-bones VoIP line.
For the majority of small and mid-sized organisations, a hosted PBX wins on cost predictability, resilience and effortless scaling. The exceptions are businesses with significant existing PBX investment or specialist needs, where SIP trunking modernises the lines without ripping out the system.
Whatever you choose, the phone system is only as good as the connection beneath it. Design voice and connectivity together, insist on clear contract and porting terms, and you'll end up with a system that quietly does its job for years.
