Reviews
Part of Making sense of VoIP systems: live or die on the network path
VoIP systems: the written trial that separates real contenders
Choosing VoIP systems software works better as a written requirement and a scored trial than as a shortlist. Here is the requirement, scoring and exit clause.
No best phone system exists, and a page that names the best VoIP systems software for 2027 is guessing about your building, your call volume and your staff. The process that produces your right answer can be written down, and it is short enough to run in three weeks.
What the connection underneath must provide is set out in our guide to voip systems.
The names that surface first when a small business shortlists VoIP systems are RingCentral, Zoom Phone, Vonage, Ooma, 8x8, GoTo and Microsoft Teams Phone. They are candidates, not answers: which of them survives depends on the requirement below and on what the trial shows.
What to take away
- Write the requirement before you look at anything. Four sentences about what callers experience and who administers it will eliminate most candidates.
- Score a trial, not a demonstration. A demonstration shows the product working in conditions that are not yours.
- Decide the exit before the entrywho owns the numbers, how you get the configuration out, and what notice you must give.
Write the requirement in four sentences
- Who calls you, and what do they need to reach? A queue, one person, a department, or an answer at three in the morning.
Four-sentence VoIP requirement
- Who calls you, and what must they reach?
- Who calls out, and from where?
- Who administers it, and how often will it change?
- What must survive a power cut and connection failure?
Anything not implied by those four sentences is optional. Score optional things at zero, because a long feature list is easy to produce and rewards the supplier who produced it. Measuring the line first is a job for our guide to business internet, and it decides how much of the rest is even testable.
The scoring sheet
Set weights before you see any proposal, and write them down before the trial starts: call quality and routing fit carry the heaviest weight, administration and reporting come next, and headline price weighs least once the requirement is met. These are the categories that
Scoring sheet: category and test
Category
- Call quality
- Real calls at busy hour
- Routing fit
- Build real routing in trial
- Administration
- Manager makes one change unassisted
- Reporting
- Look at the report
- Resilience
- Pull the plug during trial
- Exit
- Read the contract
- Support
- Raise out-of-hours ticket, time it
How to test it
- Call quality
- Routing fit
- Administration
- Reporting
- Resilience
- Exit
- Support
| Category | What you are scoring | How to test it |
|---|---|---|
| Call quality on your network | Whether it works over your connection at your busy hour | Real calls during the trial, wired and wireless |
| Routing fit | Whether the out-of-hours and queue behavior matches sentence one | Build your real routing during the trial, not a sample |
| Administration | Time to make a routine change | Ask your own manager to do one, unassisted |
| Reporting | Whether unanswered calls are visible | Look at the report, not the brochure |
| Resilience | What happens when power or the line goes | Pull the plug during the trial |
| Exit | Numbers, configuration export, notice period | Read the contract, not the sales answer |
| Support | Who answers out of hours and what they can do | Raise a ticket during the trial and time it |
Fill the last column in during the trial. A category you cannot test is a category you are guessing at, and guessed scores should be marked as such. The network configuration that protects call quality is in our guide to setup and troubleshooting.
The trial, and how to keep it honest
Run it with one real team doing real work, alongside the existing system, for
Keeping the trial honest
- Run one real team alongside the existing system
- Include a Monday and a month end
- Do not let the supplier configure it
- Saturate the upload during a call
- Unplug the router during the trial
- Call the out-of-hours number at eight
long enough to include a Monday and a month end. Two rules keep it useful:
- Do not let the supplier configure it for you.You need to know what administering it feels like, and that is the part you live with.
- Break it deliberately.Saturate the upload during a call. Unplug the router. Call the out-of-hours number at eight in the evening. Everything you do not test in the trial you will test in production.
Get the exit terms in writing during the trial
Ask each supplier for four things before the trial ends: the per-seat price for the users you actually have, any charge for porting your numbers out, the length of the term, and the notice period you must give to leave. Keep the answers beside the scoring sheet, because the exit is the part you cannot test once you have signed.
The two questions suppliers dislike
"What is your port-out process and how long does it take?" Your numbers are the thing that makes leaving hard. Porting in the US is governed by the FCC's local number portability rules, 47 CFR part 52, subpart C, and the FCC's benchmark for a simple port — the same service at the same address, with no new features — is one business day. Ask your supplier to put its own commitment in writing, and read our guide to business phone numbers for the account record that governs it.
"How are emergency calls handled, and what address is passed?" Get the answer in writing and tell your staff. The FCC's consumer guide to VoIP and 911 service explains why the address is a record held by the provider rather than a fact about the wire, which is exactly why it can be wrong when somebody moves desk or works from home. Under the FCC's rules for interconnected VoIP, 47 CFR part 9, the provider must obtain a registered location for your service and give you a way to update it, so make updating it part of every desk move and every remote hire.
Common questions
How many suppliers should we trial?
Two. Three is a project. One is a negotiation you have already lost.
Should we take the cheapest that meets the requirement?
Usually yes, provided the exit is clean. A clean exit is worth more than a feature you have not needed yet.
What if our requirement changes in a year?
Then a short term and a documented export matter more than the feature list. Buy flexibility rather than prediction.
Is an on-premises system ever the right answer?
When internal calls must survive a connection failure, or when someone in the building is genuinely available to run it. Choosing it to save money and then budgeting nobody's time is the way it goes wrong.
