6 Types of Business Phone Systems Explained

Analogue calls carried over the PSTN copper network

A traditional landline system runs on the PSTN — the Public Switched Telephone Network. Physical desk phones connect by copper wire to your local telephone exchange, and the exchange switches each call through to whoever you dialled. Small offices often added a key system, a box in a cupboard that let a handful of handsets share two or three PSTN lines and press a button to pick up a specific one.

The PSTN is genuinely reliable and famously simple, and a basic corded handset keeps working in a power cut because the copper line itself carries a small voltage from the exchange. What it cannot do is anything modern. Features stop at hold, transfer and voicemail, every new line or extension needs an engineer visit, and a number is tied to the building it is wired into. It is also the oldest technology in this list, and carriers worldwide are progressively retiring it in favour of digital alternatives.

A private switchboard in your building, running over analogue or ISDN lines

A PBX — private branch exchange — is the switchboard that connects calls between people inside a business and out to the public network. In the traditional form it is a physical unit installed on site, connected to analogue or ISDN lines, with extensions wired to every desk. This is the system that gave businesses internal extensions, hunt groups and the first automated attendants.

For a mid-sized office it worked well and lasted decades, which is exactly the problem. The hardware is expensive upfront, needs a maintenance contract and a specialist to change anything, and ISDN is being retired alongside analogue. Businesses still running one are the group most affected by the switch-off, because replacing it is a project rather than a swap.

Calls travel over internet protocol, but the switching hardware stays on your site

An IP PBX is the middle ground. Calls are carried as data using internet protocol, so you get the features of a modern system — IVR menus, call recording, softphone apps, SIP trunking instead of ISDN lines — but the server doing the work still lives in your building and belongs to you. Platforms like 3CX made this approach popular by licensing the software per system rather than per user.

It suits organisations with reasons to keep voice in-house: strict data residency requirements, an existing investment in hardware, unusual integrations with on-site systems, or an internal IT team that would rather control the stack. The cost is that you own the whole problem — updates, security patching, hardware failure and capacity planning are all yours.

The PBX is software run by your provider; you use apps and handsets

In a cloud VoIP system — also sold as a hosted PBX or UCaaS — the switchboard is software running in your provider’s infrastructure. You get numbers, IVR menus, business hours routing, call recording, voicemail and desktop and mobile apps, and there is nothing to install beyond signing in. Adding a person is a checkbox rather than an engineer visit.

This is what most businesses buying today should choose, and the reason is feature economics rather than fashion. Because the provider maintains one platform for everyone, capabilities that used to be expensive projects — multi-level menus, recording, analytics, AI transcription — arrive as standard for roughly $10 to $30 per user per month. The genuine trade-off is that calls depend on your internet connection, so a flaky line becomes a phone problem.

A business number and simple menu that forwards to phones you already own

A virtual phone system is the lightest option here. You get a business number — often toll-free — plus an auto attendant, extensions and voicemail, and calls forward to whatever phones your team already carries. There is no handset to buy and frequently no per-user pricing, just a flat monthly fee for the account.

For a consultant, tradesperson, small practice or a two-person startup it does the important job: callers reach a professional-sounding business rather than a personal mobile. It runs out of room quickly, though. Reporting is minimal, recording is limited or absent, integrations are few, and there is no real concept of teams or queues.

Built for queues, agents and volume rather than for an office

A contact centre platform, sold as CCaaS, is a different product that happens to include telephony. Its purpose is managing large volumes of inbound contact: skills-based routing that matches a caller to the right agent, queue management, workforce scheduling, quality-management scorecards, speech analytics and compliance recording, usually across email and chat as well as voice.

The features are genuinely powerful and genuinely heavy. Pricing typically starts around $65 per user per month and runs well beyond it, implementation is a project with professional services attached, and administration needs a named owner. Buying one to run a thirty-person office phone system means paying for machinery nobody will operate.