What Is UCaaS? A Buyer's Guide to Pricing, Teams and Porting

Hey there. I did a little bit of content research on UCaaS and found that several parts are missing on all the blogs. It's the contract auto-renewals at a higher rate, the port taking three weeks instead of a day, and the fire panel stopping dialing out. Here is the category, the platforms, and the parts that cost money after you sign.

TL;DR

• UCaaS is business telephony plus messaging and meetings, sold as a subscription. One provider, one bill, no PBX on site.
• Queues and IVR are UCaaS features, not CCaaS ones. CCaaS adds digital channels and workforce management.
• Three of seven major platforms publish no per-seat price. Get the quote, then read the renewal clause.
• A business phone port is not a one-day job. By FCC definition it is never a simple port.

What UCaaS Is, and What It Replaces

Gartner defines UCaaS as a multitenant, cloud-delivered subscription service offering business telephony, PSTN connectivity for inbound and outbound calling, and collaboration capabilities such as messaging and meetings. In practice it replaces three things at once: the PBX in the comms room, the PRI or analog lines feeding it, and often a separate meetings tool nobody consolidated.

The reason this keeps appearing on roadmaps is not a vendor campaign. It is the carriers withdrawing the service underneath. AT&T filed Section 214 discontinuance applications with the FCC roughly monthly through 2026, and CenturyLink filed emergency applications in eight separate months of the same year. When the copper under a site is scheduled for retirement, the phone system on top of it becomes a project whether anyone planned one or not.

The counter-narrative is worth knowing before you commit, because the vendor pages will not carry it. Metrigy surveyed 775 IT leaders in April 2026 and found 26.8% planning to leave their current UCaaS provider. Nearly 46% of those were considering a move back to on-premises or private cloud, citing data residency, security and reliability. Gartner cut its own expectation for 2028 cloud-telephony adoption from 90% to 70% in the same year.

UCaaS and CCaaS Are Not Divided Where You Think

Ask where UCaaS ends and CCaaS begins and the usual answer is queues and IVR. That answer is wrong, and Gartner's own requirements are what make it wrong.

Gartner's UCaaS mandatory feature list, updated August 2026, already requires hunt groups, queues with announcements, auto attendants, interactive voice response, attendant consoles for receptionists and hot desking. It also requires support for physical analog phones and analog devices such as fax machines and fire alarm panels. All of that is table stakes for a UCaaS platform, not a contact-centre upgrade you buy later.

The practical test is staffing, not features. If nobody is being scheduled into shifts and nobody is measuring adherence or reviewing recorded interactions for quality, you are being quoted a contact centre you do not need.

Where Microsoft Teams Fits

Microsoft documents four ways to get PSTN calling into Teams, not the three that most comparisons list.

Teams Phone Mobile is the one that gets dropped from comparisons, and it carries a limit worth catching early: Microsoft's documentation states it supports user phone numbers only, and does not support audio conferencing or voice application numbers. Auto attendants and call queues are voice application numbers.

The licensing trap is simpler and more expensive than the routing choice. Microsoft 365 E5 includes Teams Phone. Business Premium and E3 do not, and need a Teams Phone Standard add-on at $10 per user per month on annual billing, per Microsoft's pricing announcement effective 1 April 2025. Billing monthly on an annual term adds roughly 5% on top. A PSTN solution is a separate purchase from the Teams Phone licence either way.

Two changes have not filtered through to most comparisons yet. Microsoft's certified SBC page now states it is not accepting new nominations for certification until further notice, so the supported hardware list is effectively frozen. And Microsoft documents one SBC serving several tenants as a supported design, describing it as built for partners and carriers who then charge separately for PSTN services.

What a Seat Costs, and What the Contract Does to It

Published pricing is thinner than the category's reputation suggests. Of seven major platforms, two publish no per-seat figure at all, and four more withhold it above a seat threshold. Everything below was read on 17 September 2026.

Zoom's tiers are bundles rather than phone-only SKUs, so the upper ones include a paid Workplace seat. There is no published price for adding Zoom Phone to a Workplace seat you already pay for, which makes a straight per-seat comparison against the others misleading in Zoom's favour.

The contract does more to the bill than the tier does, and this is where the reading pays. Zoom's terms state the asymmetry outright: a modification takes effect at the next renewal term, unless you request an increase in services, which takes effect immediately. Decreases wait. Increases do not.

Vonage publishes the only hard automatic uplift in the group, stating that on auto-renewal the subscription charges will increase by 7%. Not may increase.

8x8 allows seat reductions at renewal with 45 days' notice while its non-renewal window is 30 days, which leaves a fortnight where you can still cancel outright but can no longer shrink. RingCentral's terms contain no clause using the words reduce, decrease or downgrade at all; the lock sits in a line saying recurring charges, once incurred, remain in effect for the term. Nextiva's is the sharpest of the set: give notice less than 30 days out and the agreement renews anyway, with termination landing at the end of that new term.

Dialpad publishes no initial term, renewal, notice or seat-reduction clause in its general terms. All of it lives in the Service Order, which you see once you are already in the conversation. That is worth treating the way you would treat any other vendor risk you cannot read in advance.

Migrating Off an On-Prem PBX

Handsets and dial tone are the easy part. What derails a cutover is everything plugged into the old system that is not a phone.

Fire alarm panels are the clearest case. NFPA 72 requires a Managed Facilities-based Voice Network, which has to provide a loop-start circuit interface, proactive pathway management by the provider, eight hours of standby power at the premises and physical access safeguards. A generic analog adapter hanging off a UCaaS account meets none of the last three. Moving a fire panel's dialer onto one is a code problem, not a preference.

Elevator phones have their own rule and it is stricter than people expect. New York City's building code, adopting ASME A17.1, requires the communications power source to last at least four hours and unacknowledged calls to divert within 45 seconds. An adapter sitting on the customer LAN stops working the moment the switch or the ISP loses power.

Fax is the third, and the answer is usually to stop. T.38 is the standard where fax survives, but Microsoft states plainly that faxing services are not available to Teams customers through Phone System or any Calling Plan. Inventory the analog lines during scoping, not during cutover weekend: alarm panels, elevator phones, paging, door entry, lift-station dialers and the fax line accounting swears nobody uses.

The handsets divide into scrap and maybe. RingCentral publishes the most useful single sentence on this: non-SIP phones, digital phones, ISDN phones and the Cisco 79xx, 89xx and 99xx series are unsupported, alongside Nortel, NEC, ShoreTel and Panasonic sets locked to their own platforms. Cisco's own conversion guide explains the 79xx entry, because there is no path to convert those to the multiplatform firmware cloud providers expect.

A SIP phone you already own is reusable under four stacked conditions: the model and firmware appear on the new provider's list, it gets a factory reset, Cisco enterprise models are converted to MPP first, and the device is released from whatever provisioning service it was last bound to. That last condition is what makes a second-hand phone fail with no useful error, because it keeps pointing at the previous provider's server until someone clears the MAC address.

Porting, E911 and the Liability That Comes With Managing It

Two claims circulate that are wrong in the same direction: that porting takes a day, and that emergency calling is the carrier's problem.

The one-business-day figure is real, and it applies to simple ports. The FCC's definition of a simple port excludes accounts with more than a single line, complex switch translations such as Centrex or ISDN, and anything involving a reseller. A business PBX fails the first test before you reach the rest. Non-simple ports run four business days, and pulling part of a number block off a PRI becomes a negotiated project of up to 15 business days, because the losing carrier has to rebuild the hunt group you left behind.

Microsoft's own porting guidance is more candid than most carrier pages: 7 to 14 days start to finish, up to 30 depending on the losing provider, a minimum five-day lead time in the US, and a recommendation to target a date at least 15 business days out. Mismatched account data is the most common cause of rejection, and a rejection resets the clock rather than pausing it.

Budget for paying twice. The FCC's guidance is not to cancel existing service before the new service is running, and 8x8 tells customers a transfer can take up to four weeks depending on when the current provider releases the numbers. Together those mean a stretch of overlapping bills on every migration. Nobody publishes how long, so scope it as a range and say so in the quote rather than discovering it in month two.

Emergency calling is where the liability attaches, and the rule names the party. Under 47 CFR 9.17, the person engaged in the business of managing the multi-line telephone system is presumed responsible for non-compliance. The FCC said it would determine who that is case by case, including by reading the parties' contracts, and declined to create a safe harbour for installers.

The timing is the part worth pausing on. Kari's Law is forward-looking and does not apply to a system installed on or before 16 February 2020, so a client's untouched 2014 PBX is exempt. The migration is the event that attaches the obligation. From cutover, direct 911 dialing with no prefix digit, on-site notification to someone likely to see it, and dispatchable location all apply to the system you just installed.

There is a trap where the handset problem and this one meet. When a phone will not provision, the quick fix is generic SIP credentials, which most platforms will issue. Dialpad states the consequence outright: generic SIP devices do not support E911. Solving a hardware problem that way moves an emergency-calling obligation onto a device that cannot meet it, and the rule still points at whoever manages the system.

Teams splits this by path. Dynamic emergency routing comes from the carrier on Calling Plans, Operator Connect and Teams Phone Mobile. On Direct Routing you configure it yourself, through an emergency routing service provider or an ELIN application on the SBC. One gap to catch at design time rather than during a test call: dynamic emergency calling is not supported on the Teams web client.

How to Pick a Platform

Start with the analog inventory and the port, because those constrain the shortlist more than any feature matrix will. A site with a fire panel, two elevators and a 60-number PRI has a different answer from a 20-person office with SIP handsets and a single block of DIDs.

Weigh the SLA numbers less than the marketing does. Melissa Swartz, an independent UC consultant, has pointed out that Teams Phone's 99.999% figure applies only from your next renewal, that the Azure gateway behind Operator Connect carries 99.99% rather than five nines, that the voice quality SLA requires a certified desk phone on wired Ethernet, and that there is no SLA on incoming PSTN calls at all. Gartner's 2026 evaluation separately notes that Cisco caps financial remedies for Webex Calling outages at 5% of the monthly service fee.

Review scores will not separate the field either. Across Gartner Peer Insights the major platforms sit between 4.4 and 4.7, which is a polite way of saying the data does not distinguish them. Spend the time on the renewal clause instead, where the differences are large, published and specific.

Then price the thing properly. A per-seat figure is the smallest part of the number once you add the PSTN solution, the analog replacements, the port project and whichever uplift the contract applies at renewal. Our guide to pricing models covers how to structure that for a client rather than absorb it.

If you want the adjacent category that gets confused with this one on name alone, unified endpoint management is a different problem with a similar prefix.