What UCaaS actually is
UCaaS stands for Unified Communications as a Service — a cloud-based replacement for a traditional on-premises phone system (PBX). Instead of buying and installing physical phone hardware, maintaining it in a server closet, hiring someone to manage it, and hoping it doesn't fail, UCaaS lets you provision phones, call routing, voicemail, call recording, and conferencing entirely through software.
The model is simple: you pay a per-seat, per-month fee (typically $15–$40 depending on the platform and feature set), and the provider handles the infrastructure, redundancy, updates, and compliance. Users get a softphone app on their computer or phone, a traditional desk phone if they want one, or both. Call quality depends on your internet connection, not on proprietary phone lines.
This is fundamentally different from a traditional PBX in three ways. First, it's pay-as-you-go — you license seats month to month, so adding 10 new employees costs exactly 10 times the per-seat price. Second, it scales geographically without infrastructure — an employee in Portland and one in Miami both run on the same system. Third, the whole stack is software, which means integration with Salesforce, ServiceNow, or a custom CRM is possible in ways it never was with a PBX.
UCaaS replaced traditional phone systems in most markets between 2015 and 2022. By 2026, PBX installations are rare outside of very large enterprises or heavily regulated industries. The only real choice left is which cloud platform fits your business model.
The major platforms compared
Five platforms dominate the market: RingCentral, Microsoft Teams Phone, Zoom Phone, 8x8, and Vonage/Ericsson. Each has legitimate strengths and some serious gotchas.
| Platform | Best for | Pricing Model | Contract Flexibility | Contact Center Add-on | Key Watch-out |
|---|---|---|---|---|---|
| RingCentral | Mid-market general use, high reliability need | $15–$25/seat/mo | Month-to-month or annual | Yes, mature offering | Included features vary by tier; clarify what's in each plan |
| Microsoft Teams Phone | Already in M365, want integration with Teams | $4–$10/seat/mo + calling plan | M365 licensing locks you in | Contact center available but separate | Calling plans are country-limited and expensive; Direct Routing adds complexity |
| Zoom Phone | Video-first culture, light phone needs | $15.99–$25.99/seat/mo | Month-to-month | Emerging but limited | Contact center roadmap unclear; relies on video-first assumption |
| 8x8 | Support-heavy orgs, contact center needs | $20–$35/seat/mo | 12 or 24 months preferred | Native, strong offering | Aggressive on longer contracts; slow implementation historically |
| Vonage/Ericsson | Mid-market, API integration, SIP flexibility | $18–$28/seat/mo | 1–3 years; now Ericsson-owned | Yes, available | Ownership transition (Ericsson acquisition) may affect roadmap and support |
RingCentral owns the largest market share and for good reason: mature platform, predictable pricing, strong mobile app, easy integrations. They're the safest choice for a first-time UCaaS buyer, though not necessarily the cheapest.
Microsoft Teams Phone is the wild card. If your business already pays for Microsoft 365 (and most do), Teams Phone looks cheap on paper because the base license is $4–$10/month. The trap: that price doesn't include calling plans. Calling plans (which let you actually make calls) cost extra and are not available in all countries. If you're in a country where Teams calling plans aren't available, you need Direct Routing — which means you have to source and manage a SIP trunk separately. This is the most common gotcha we see.
Zoom Phone makes sense if your culture is already built on Zoom and you want phone capability without a separate app. Implementation is usually faster than RingCentral or Teams. The downside: Zoom's contact center roadmap is unclear, so if you think you might need a contact center in the next few years, you're betting on Zoom's product direction.
8x8 is purpose-built for contact centers and support teams that live on the phone. If that's you, their native contact center features and call handling sophistication are worth the higher per-seat cost. The trade-off: they prefer longer contracts and have historically been slower at implementation than RingCentral.
Vonage, now owned by Ericsson, is a solid mid-market choice with good API tooling for custom integrations. The question mark is the Ericsson acquisition and what it means for product roadmap and support. This is worth asking the sales team about directly.
How to evaluate them
Before you run an RFP, clarify what actually matters to your business. The right platform for a 30-person consulting firm is completely different from the right platform for a 200-person contact center. Ask yourself these questions:
How many seats do you actually need? This drives licensing cost by an order of magnitude. Most platforms let you add seats month-to-month, but some will push you to commit to a minimum. Make sure the minimum aligns with your near-term headcount plan.
Do you have significant international calling needs? If your team is distributed across North America, Europe, and Asia, ensure the platform supports the countries you operate in and that international calling rates are clear. Some platforms hide international calling overage rates until you ask.
Are you going to need contact center features? Basic call routing and voicemail are standard on all platforms. Contact center features — queue management, call recording compliance, IVR scripting, blended inbound/outbound handling — are not. If you think you might need these in the next two years, factor them into your platform choice now. Adding contact center later can mean a platform migration.
Are you already deep in Microsoft 365? If Teams is already your daily-use collaboration platform and your entire directory is in Azure AD, Teams Phone integration is a real advantage. If you're not already a Microsoft shop, Teams Phone's calling plan complexity is a deal-breaker.
What integrations actually matter? Before choosing, list the three tools your team lives in: Salesforce, ServiceNow, HubSpot, Slack, whatever. Check the platform's app marketplace for the integrations you need. "Available on roadmap" doesn't count.
How good does the mobile app need to be? If your team is office-based and uses desk phones, mobile app quality is less critical. If you have significant remote or field staff, test the mobile app on actual networks before deciding. Some platforms' mobile implementations are significantly weaker than others.
What to watch in the contract
After you've picked a platform, the contract is where UCaaS pricing gets dangerous. Here's what actually appears in the fine print and what to push back on:
Auto-renewal with 60-day termination notice. Standard across the industry. Most platforms auto-renew unless you send written notice 60 days before expiration. Mark this on your calendar. Missing the window means you're locked in for another year.
Seat minimums that don't flex. You might commit to 100 seats, but next month your headcount is 85. Most contracts require you to keep paying for 100 seats. Some platforms are flexible here if you ask, but many enforce it strictly. Negotiate a true month-to-month overage if possible.
International calling overage rates that surprise you. The contract's per-minute or monthly rates for inbound/outbound international calling are often understated. Ask for the exact per-minute rate to every country your team calls. "International calling included" doesn't mean calls to everywhere — it's usually limited to major markets.
SLA credits that require you to file a claim within 24 hours. Most UCaaS contracts include 99.9% uptime SLAs, which sound reassuring until you realize you have to file a formal claim within 24 hours of an outage or you lose the credit. By the time you notice, investigate, and document a 2-hour outage, the 24-hour window may have closed. Push for a 7-day claim filing window.
Early termination fees (ETFs) for long-term contracts. If you sign 24 months and decide to leave after 12, you owe ETFs that can be substantial — sometimes 50% of the remaining contract value. Short-term contracts (12 months or less) usually have lower or no ETFs. For a first-time buyer, ask for a 12-month term with an auto-renew after 12 months instead of locking in 24 or 36 months.
Hidden professional services costs. The per-seat price is not the total cost. Number porting, E911 registration, desk phone hardware, implementation services, and custom integrations all cost extra. Make sure you have a line-item quote for these, not just an estimate.
The Microsoft Teams phone caveat
Teams Phone deserves special attention because it's marketed in a way that creates confusion. Here's what you actually need to know:
Microsoft Teams is a collaboration platform — Slack's competitor. It has messaging, file sharing, and video conferencing built in. But Teams does not include calling capability out of the box. To make calls through Teams, you need one of two things: (1) a Teams Calling Plan license for each user, or (2) Direct Routing set up to an external SIP provider.
Calling Plans are the simpler route: you add a license ($4–$10/month per user) and Teams handles the phone system backend. The catch: Calling Plans aren't available in every country, and calling to mobile numbers in some countries costs more. If you're in Canada or Western Europe, you're fine. If you're in Southeast Asia or parts of Latin America, Calling Plans might not exist.
Direct Routing is the fallback: you keep your current phone system or contract a SIP trunk (essentially a Voice-over-IP provider) and wire it into Teams. This gives you full flexibility and access to cheaper international calling, but it requires someone on your team (or a consultant) to understand SIP trunking, because you're now maintaining the connection between Teams and the outside world.
We see many clients who go the Teams route thinking they're getting a complete phone system for $4/month, only to discover they need Calling Plans (not available in their region) or they need Direct Routing (which adds cost and complexity). Before you commit to Teams Phone, know which path you're taking and calculate the real all-in cost.
Implementation realities
Choosing a platform is 20% of the project. Implementation is the hard part. Here's what to expect:
Number porting takes 2–4 weeks. You can't cut this timeline. The process involves your current provider, the new provider, and regulatory paperwork. During the porting window, you need a fallback plan (or your calls go nowhere). Set up call forwarding to mobile phones or a message saying you're migrating. Budget 2–4 weeks and don't plan a cutover during your busy season.
E911 registration is per-location, not per-company. You have a physical office in Portland and a small satellite office in Chicago. You need two separate E911 registrations (one for each location), and each one costs money and takes time. If you're managing 50 locations, this becomes a project of its own. Confirm upfront how the vendor handles multi-location E911.
Users need training on the new softphone app. Your team has been using physical phones for years. A softphone is different: different buttons, different workflows, different call transfer logic. Budget time for training and for early-adoption support. The vendor usually provides training, but you might want to do a pilot with 10 power users first.
Test during business hours, cut over at night. Some platform implementations can happen in parallel with your old system (you test while still operational). Some require a flag day where you kill the old system and bring the new one live. If it's a flag-day migration, do it on a Friday after hours or a Sunday, not during your busiest business day. Have your escalation contacts available.
Have a failover plan ready. For the first week of the migration, something will go wrong: a missing feature, a forgotten department, a call queue configured wrong, an integration that didn't port over. You need a live fallback: either your old phone system still running in parallel, or a set of cell phones with pre-programmed forwarding rules so you can revert to manual. This is not optional.
Frequently asked questions
Can I keep my phone number when I move to UCaaS?
Yes, in almost all cases. The technical process is called "number porting" and it usually takes 2–4 weeks. Your new UCaaS provider handles the paperwork with your old carrier. During the porting window, your old and new systems usually run in parallel so you don't lose calls. After the cutover, the number works on the new platform.
What's the difference between RingCentral and Zoom Phone?
RingCentral is a pure phone system that happens to include video. Zoom Phone is a phone system built into Zoom, designed for teams that already live in Zoom. RingCentral has more contact center depth and a longer track record. Zoom Phone is usually faster to implement and cheaper for smaller organizations. If you're already using Zoom heavily, Zoom Phone is simpler. If you want best-in-class phone features, RingCentral is safer.
Should I commit to 12 months or 24 months?
For a first-time UCaaS buyer, 12 months is the right choice. It gives you a full year to see if the platform fits your workflow and team. After 12 months, if you want to stay, you can sign another 12 months. If you want to switch, the transition cost is lower. 24 and 36-month contracts are cheaper on paper, but the early termination fees can be brutal if you need to change.
Do I need a contact center, or is just a phone system enough?
Most businesses use "contact center" and "phone system" interchangeably, but they're different. A phone system handles calling for a team. A contact center handles the specialized features you need if your team is managing queues, recording calls for compliance, routing based on skills, or handling blended inbound/outbound work. If you have a customer service team or support desk, you probably need contact center features. If you're just replacing traditional desk phones, a basic phone system is enough.
What happens if the platform goes down?
Most platforms promise 99.9% uptime (4.3 hours of downtime per year), backed by SLA credits if they miss. In practice, outages are rare. But when they happen, you lose all calling because everything is in the cloud. To be safe, maintain a fallback: know your team's mobile numbers and have call forwarding set up to bypass the system. It's also worth understanding the platform's status page so you can check if an outage is widespread or just affecting you.
Can I use UCaaS with bad internet?
No. UCaaS requires stable, low-latency internet — ideally 10 Mbps or better for calling quality. If your internet is spotty, your calls will sound bad or drop. Before moving to UCaaS, audit your internet connection: speed, latency, packet loss, jitter. If you can't hit 10 Mbps consistently, or if you have frequent outages, UCaaS will be frustrating. You might need to upgrade your internet connection as part of the project.
Is UCaaS more expensive than a traditional PBX?
For most mid-market businesses, UCaaS is cheaper than a PBX when you factor in the cost of hardware, maintenance, and a dedicated IT person. A $3,000 phone system plus $20,000 in hardware plus someone's salary to manage it for five years typically costs more than paying $20/seat/month for UCaaS. The trade-off: you don't own the hardware, and you're locked into monthly recurring costs. For a business with stable, fixed headcount and free IT resources, a PBX might be cheaper. For everyone else, UCaaS is the better economics.
Ready to evaluate cloud phone systems for your business?
Our team has evaluated 30+ platforms across 300+ deployments. We'll audit your current environment, clarify what you actually need, and run the RFP with multiple vendors so you can make an informed decision.
Start a Conversation