How do you evaluate UCaaS providers before buying?

A feature list makes a poor first filter. UCaaS, or unified communications as a service, means calling, meetings and messaging from one cloud service, so a list of those features describes the category more than it separates one provider from another. The requirements that separate them are specific to your company, and they tend to have a yes or no answer.

We'd start with four. The first is geography: whether the provider can supply phone numbers, and move your existing ones, at every location where you have people. The second is hardware. If you own desk phones you intend to keep, the provider either supports those models or it doesn't. The third is any integration you can't work without, such as the CRM or helpdesk where your calls get logged. The fourth is emergency calling. An internet phone can be used away from the office, so the provider needs a way to keep the right address on file for people who work from home or move between sites. We explain that process in how to register a VoIP phone for 911.

A provider's website will often answer these at the level of a category, and an exclusion needs the specific item. Atlantech Online's pages show how to read one. Its business phone service page says the company provides its full set of phone services anywhere in the United States. That tells you the advertised coverage. You still confirm your own office addresses and the numbers you plan to move, and an overseas office remains an open question. The page says you can use your own phones if they interoperate with Atlantech's voice switch, and its FAQ recommends devices from an approved list. Atlantech's UCaaS page says the service connects with helpdesk software and sales CRMs, and it mentions Google and Microsoft without listing individual products.

Each of those statements tells you what to send the provider next. You send the model numbers of your desk phones and the name of your CRM, and you ask for a yes or no on each. The phone service page also mentions that international calling is off by default to guard against toll fraud and is switched on by request. A company with customers abroad would want that arranged before its first day on the service.

A provider that fails one of these comes off the list, however good its demo was. The ones that pass are worth comparing in detail.

The second pass compares written offers, and the work is getting them onto the same basis. Published prices are a starting point. Atlantech's UCaaS page lists two lines: Business Line starting at $12 per user per month and Premium Line starting at $18 per user per month. For 30 users, those starting rates come to $360 or $540 a month. The page prints no contract term, taxes or setup charge beside them, so the full figure comes from the quote.

The two cards also list different features. The Business Line card lists call handling features and unlimited local and domestic long-distance calling. The Premium Line card lists voicemail, conferencing, collaboration and a softphone. Before you compare either rate with another provider's, find out which line includes the features your company depends on.

Other providers publish prices on different terms. Microsoft's US price list shows Teams Phone with Calling Plan at $17.00 per user per month on an annual subscription paid yearly, with a Teams license required separately. So a $17.00 figure and an $18 figure are not yet comparable. One is an annual commitment that needs another license under it, and the other is a starting rate whose term isn't stated on the page.

Offers can sit side by side once they describe the same thing. Use the same number of users and the same billing period for each. Add the taxes and fees each provider charges, and add what you pay once for setup, number porting and phones. We explain what moves the rate in how much UCaaS costs per user.

An uptime percentage means only as much as the definition of downtime behind it. Google's published terms show why. Google Voice is covered by the Google Workspace Service Level Agreement, which commits to a monthly uptime of at least 99.9%. The agreement defines downtime as a period when the user web interface has more than a five percent user error rate, measured on Google's servers. A call that drops because of trouble on your office network isn't downtime under that definition. The agreement also excludes problems that come from the customer's equipment or from third-party equipment outside Google's control.

The remedy is specific too. The credit is three days of service when monthly uptime falls below 99.9% but stays at 99.0% or above. It is seven days for uptime below 99.0% down to 95.0%, and fifteen days below 95.0%. One tier applies for the month, and fifteen days is the most Google will credit for a single month. The customer has to open a support case within thirty days of becoming eligible, or the credit is forfeited. The agreement calls these credits the customer's sole and exclusive remedy.

Those four clauses are the ones to find in any provider's service commitment: what counts as downtime, what you receive, how you claim it and what is excluded. Two providers can quote the same percentage and promise different things if they measure downtime differently. Record each provider's own wording on the sheet instead of the headline number.

A guarantee on a service page is a different kind of promise, and it gets its own entry. Atlantech's business phone service page offers a 30-day guarantee. If you use the service for 30 days and don't love the call quality, uptime and support, your next month of service is free. That covers something an uptime figure can't, which is your own judgment of how the calls sound and how support treats you. It applies after you've become a customer, and the page describes the remedy as a free month. A right to cancel and an uptime figure for the rest of the term are separate questions, and the service agreement answers them.

Whichever provider you choose, ask for any promise you're relying on to be written into the order you sign. A web page can change after you buy, and the signed agreement is the document both sides will go back to.

A demo shows the provider's setup. A pilot shows yours, and it doesn't have to be large to be useful. Whether a provider will run one before a contract, and on what terms, is something to ask each finalist.

Suppose a 30-person company has Atlantech's UCaaS service on its shortlist with two others, and each provider agrees to a two-week pilot. The company has a main number answered by a receptionist, a six-person support group, a sales team that works out of a CRM, and a dozen desk phones of one model. Atlantech's UCaaS page lists an auto attendant, ACD groups that distribute calls among agents, voicemail transcription, a mobile app and a softphone that works with the receptionist features. Those are the things this company would use every day, so the pilot tests exactly those.

The company asks for a temporary number and five test users: the receptionist, two support agents, one salesperson and one person who works from home. It tries two of its existing desk phones. The other users take calls on a laptop softphone and the mobile app. The company also decides how the support group should ring. Say it wants both agents' phones to ring at once.

Then it runs its own calls. Someone dials the temporary number from a personal mobile and chooses support from the auto attendant menu. The test is whether the group rings the way the company asked. The receptionist transfers a second call to the salesperson. A third caller leaves a voicemail, and the salesperson checks whether the transcription arrives. Whether the call appears on the contact's record in the CRM is a separate check, because the CRM link and voicemail transcription are separate features. The home worker repeats the calls over home internet.

Support gets tested the same way. Someone calls the provider's support line with a real question from the setup and notes how long it took to reach a person who could answer it. If the pilot runs long enough to open a ticket, the response to that ticket goes in the notes as well.

The company writes down each result as worked, worked after a change, or didn't work. The middle group deserves the most attention. A desk phone that makes calls but loses a button the receptionist relies on, for example, is a cost that didn't appear in the quote. If calls sound poor from one location, the cause may be that location's network and not the provider, and we cover how to tell in common UCaaS call quality problems. Setting up the test also previews the work of moving off an on-premises PBX, since both start with the same phones, numbers and call routing.

A pilot shows how the service handled the calls you tested. It doesn't settle what you'll pay after the first term or what the contract requires if you leave. Those answers are in each provider's agreement, in the clauses on contract length, renewal and notice. They vary from one provider to the next, so read them in each provider's own document and don't assume your last phone contract is the pattern. If a line on the comparison sheet is still blank when you're ready to sign, ask for it in writing first.