Skip to content
AI Dialer

Buying guides

How to choose a business phone system (without overbuying)

  • 7 min read

By Last updated

The short answer

A business phone system routes calls to the right person, keeps a record of what happened, and lets a team share numbers rather than tying them to individual handsets. The choice comes down to five things: how calls arrive, how many people answer, whether you dial out, what you must record, and how your volume varies.

Most phone-system comparisons are feature matrices, which is exactly the wrong shape for this decision. Every product in the category has voicemail, an auto attendant, and a mobile app. What separates them is how they price, how they handle outbound, and what happens when volume is uneven, none of which shows up as a tick in a column.

Five questions decide it.

1. How do calls arrive, and who has to answer them?

If calls arrive at one main number and any of three people could handle them, you need shared numbers, a queue, and a shared inbox, not three extensions. If calls arrive for named individuals, you need direct dial-in numbers and simple forwarding.

The mistake teams make is buying extension-based systems for a shared-number reality. You end up with calls sitting in one person's voicemail while two colleagues are free, and no way to see it happened. If more than one person could reasonably answer any given call, that is a queue requirement, and a system without one will quietly lose you calls forever.

2. How many people answer, and how does that number change?

This is the question that determines your pricing model, and it is the one most likely to cost you money over three years.

Which pricing model fits which team
Your teamPer-seat licensingUsage pricing
Stable headcount, everyone on the phone all dayUsually cheaperComparable
Part-time or shift staffYou pay full price for eachYou pay what they dial
Seasonal campaignsSeats sit idle out of seasonCost falls with volume
Mixed roles: some heavy callers, many occasionalYou pay heavy-caller price for everyoneEach costs what they use
Growing fast, uncertain sizeRenegotiation every timeNo renegotiation

Run one calculation before reading any feature list: total monthly cost divided by conversations your team actually has. Not per seat, not per feature. Most teams find they have been paying for capacity rather than for calls, which is the reason our own pricing has no seat licences at all.

3. Do you dial out at volume?

This is the fork in the road. A business phone system and an outbound dialing platform are genuinely different products, and buying the wrong one is expensive in both directions.

  • Occasional outbound: returning calls, following up customers. Any decent phone system handles it. Click-to-call from the CRM is the only feature worth insisting on.
  • Systematic outbound: working lists, prospecting, collections, appointment setting. You need dialing modes, dispositions, cadences, and above all number-reputation controls. A standard phone system will burn your numbers within weeks because it has no concept of per-number volume.

The requirement teams discover too late

Systematic outbound needs owned numbers, registered caller ID, and per-number daily caps, or answer rates collapse within a month or two. Almost no general-purpose business phone system provides those, and by the time you notice, several numbers are already labelled.

4. What must you record, and for how long?

Recording is where regulated industries and everyone else diverge sharply.

  • Coaching only: you need recording, transcripts, and search. Retention of a few months is plenty.
  • Regulated: you need policy-driven recording per campaign and jurisdiction, tamper-evident storage, an access log, defined retention with legal hold, and the ability to produce a specific call years later. That is a materially different product.
  • Healthcare: anything storing recordings, transcripts, voicemail, or message content containing patient information needs a signed business associate agreement. A vendor that will not sign one cannot be used, whatever the feature list says; see healthcare calling.

Consent is a separate axis. Several US states require all parties to agree to recording, so the safe default is an automatic announcement on every recorded call, with the consent event stored alongside the recording.

5. Where are your customers?

If you sell into more than one country, number availability quietly becomes the constraint. Two things to check before signing anything:

  1. Which countries can you actually get numbers in, and which types? Local, mobile, and toll-free availability varies enormously, and mobile numbers in particular are restricted in many markets.
  2. What documents does the regulator require? Plenty of countries require proof of a local address or a registered business before assigning a number. That requirement comes from the regulator, not the provider, but a provider who tells you about it after you have paid is telling you something about how they operate.

For inbound marketing, local numbers per market consistently outperform a single national line, and for outbound, a local number is the difference between an answered call and an ignored one. See local presence dialing for how far that effect goes and where it stops.

What to actually test in a trial

  1. 1

    Call your own number from three networks

    Look at what displays. A bare number, a wrong city, or “Unknown” tells you the caller-ID foundation is not set up, and that is the single biggest determinant of whether calls get answered.
  2. 2

    Hang up mid-call and check the record

    Does the disposition, recording, and transcript land where you expect? Systems that lose the tail of a call lose it consistently.
  3. 3

    Have two people answer at once

    Queueing, presence, and “who picked it up” reporting either work or they do not, and you will find out in thirty seconds.
  4. 4

    Try to leave the platform

    Ask how to export call records and how to port numbers out. The answer tells you what renewal negotiations will feel like.
  5. 5

    Price your real month

    Take last month's actual minutes, messages, and headcount and price it under each model. Vendors quote a headline seat rate; your bill is the arithmetic.

The short version

Buy for how calls arrive and how your volume varies, not for the feature grid. Insist on shared numbers and a queue if more than one person answers. Treat systematic outbound as a separate requirement with its own deliverability needs. Get the recording and retention question answered by whoever carries the regulatory risk. And price it against your own last month, because that is the only number that is actually true.

Integrations: which ones actually matter

Integration lists are long and mostly irrelevant. Three connections do real work; the rest are marketing.

  • CRM, in both directions. Click-to-call from the record, and every call, recording, transcript, and outcome written back automatically. One-directional integrations (dial from the CRM but log nothing) create more admin than they remove.
  • Calendar, if you book anything. Live availability rather than a promise someone confirms later. This is what turns an AI receptionist from a message-taker into something that completes the job.
  • Your helpdesk or shared inbox, so a phone call and an email about the same issue are visibly the same conversation.

Test the write-back specifically during a trial. Vendors demo the dial-out because it is easy; the failure mode that actually costs you is calls that never appear against the record, which you only discover a month later when the pipeline report is wrong.

The questions vendors would rather you did not ask

  1. What attestation are my outbound calls signed at, and why? If the answer is anything below A, ask what would change it.
  2. What happens to my call recordings and records if I leave? Ask about export format and how long access lasts after cancellation.
  3. Is there a port-out lock or fee? How easily you can leave is the best available proxy for how renewals will feel.
  4. What is the actual concurrent-call limit on my plan? Not lines: simultaneous calls, which is what constrains a dialing team.
  5. Which of these features are on my tier? Get it in writing. Queueing, recording, and dialing modes are the three most commonly assumed and most commonly tiered.
  6. What is the notice period, and does the contract auto-renew? Auto-renewal with a long notice window is where multi-year lock-in actually lives.

Frequently asked questions

What is a business phone system?
A system that routes incoming calls to the right person, lets a team share numbers rather than tying them to individual handsets, and keeps a record of what happened on each call. Modern ones run in the cloud, so there is no on-premise hardware and the same numbers work from a browser, a desk phone, or a mobile.
Is per-seat or usage pricing cheaper?
Per-seat wins when every seat dials all day, every day, all year. Usage wins when volume is uneven, seasonal, or spread across part-time and occasional callers, which describes most teams. The only honest comparison is total monthly cost divided by conversations had, measured against your own volume.
Can I keep my existing phone number?
Yes. Numbers port between providers, and porting is usually the fastest way to go live because your caller-ID registration and reputation come with the number. Ask about the port-out process too; how easily you can leave tells you a lot about renewal.
Do I need a separate dialer for outbound calling?
Not a separate vendor, but you do need the capability. Systematic outbound requires dialing modes, dispositions, and per-number reputation controls that general-purpose phone systems do not have. Running list-based calling on a system without them burns numbers within weeks.
How many phone lines does my business need?
Count peak concurrent calls, not handsets. A forty-person office rarely exceeds twelve to fifteen simultaneous calls, while a ten-seat outbound team on a parallel dialer can need thirty or more.

Sources

  1. Combating Spoofed Robocalls with Caller ID AuthenticationFederal Communications CommissionThe STIR/SHAKEN framework, the attestation levels carriers sign calls with, and the mandate requiring providers to authenticate caller ID.
  2. 47 U.S.C. § 227 — Restrictions on the use of telephone equipmentCornell Legal Information InstituteThe Telephone Consumer Protection Act itself — the consent requirements, calling-hours limits, and private right of action.
  3. ITU-T Recommendation E.164 — The international public telecommunication numbering planInternational Telecommunication UnionThe international number format, the 15-digit maximum, and how country codes and national numbers compose.

See it working: cloud call centre

Cloud call centre software runs your inbound and outbound phone operation from a browser: queues, routing, dialling, recording, and reporting, with no on-premise hardware. AI Dialer prices it by usage rather than per seat, so cost tracks call volume instead of headcount.

  • No subscription
  • Numbers in 100+ countries
  • Compliance built in