VoIP Phone System for Small Business: What to Actually Buy and Set Up

The last analog phone line I saw in a small business office had a sticky note on it that said “DO NOT UNPLUG.” Nobody knew what it was connected to or why. When we finally traced it, it was a fax line going to a machine that hadn’t had paper in it since 2019. That’s where most small businesses are with their legacy phone infrastructure — paying for something they mostly don’t use, built on technology that can’t support remote work, and completely dependent on a physical location.

VoIP is not a complicated transition for most small businesses. It is, however, one that’s easy to get wrong if you pick the wrong service, skip the network configuration, or don’t handle number porting correctly. This guide covers the decisions you actually have to make, in the order you have to make them.

---

Why the Landline and Old PBX Are Dead

Traditional phone service — PSTN lines, on-premise PBX hardware — has three fundamental problems for a small business in 2026.

Cost. A small business analog phone system with 5–10 lines runs $200–$400/month in line charges before you touch the PBX maintenance contract. A comparable VoIP system costs $100–$200/month total, including per-user software licenses. Over three years, the difference is significant.

Inflexibility. When your phones are tied to physical lines in a physical building, your business is tied there too. Someone calls your office number at 5pm and gets voicemail — that’s fine when you have a receptionist, but if you’re running lean, you want that call to ring your cell phone and the call to look like it’s coming from your business number. Legacy systems can’t do that without expensive add-ons and a phone company technician. VoIP does it by default.

No remote work support. This one became obvious to a lot of businesses during 2020 and still applies today. If your phone system is hardware in a closet that requires physical phones plugged into it, your phone system stops working the moment your team isn’t in the building. VoIP systems route calls through the internet to apps on any device, anywhere. The office number rings on your phone in a coffee shop the same as it does at your desk.

An on-premise PBX might make sense if you have more than 100 extensions, complex call routing requirements, or an IT staff that can manage it. Under 50 employees, cloud VoIP wins almost every time.

---

Cloud VoIP vs Self-Hosted: Which Setup Is Right for You

Cloud VoIP (also called hosted VoIP) means your phone system’s intelligence lives on a provider’s servers. You log in, configure your system through a web portal, and your phones or apps connect to the provider’s infrastructure. You maintain no phone hardware beyond the desk phones or ATA adapters.

Self-hosted VoIP means you run a software PBX on a server in your office — typically Asterisk or FreePBX — and manage everything yourself. You have more control and lower per-seat costs at scale, but you own every configuration decision, every update, every troubleshooting call.

For under 20 employees: cloud VoIP is almost certainly the right call. You’re not paying for IT infrastructure you don’t have the staff to manage, and the major cloud providers have built enough features into their platforms that the control trade-off isn’t meaningful for most small businesses.

Self-hosted makes sense if you have someone on staff who’s comfortable with Linux and SIP configuration, you have a specific need the cloud providers don’t support, or you’re scaling past 30–40 seats and the math on per-user monthly costs starts hurting. For most of the businesses I work with, this isn’t the situation.

---

The Services Worth Evaluating

There are a lot of VoIP providers competing for small business customers right now. Here are the ones I actually know and can speak to:

RingCentral. Feature-rich platform with solid call quality, strong CRM integrations, video conferencing built in, and an extensive API for custom integrations. Also pricey — the Essential plan starts at $30/user/month and meaningful features are locked behind higher tiers. Worth the cost if you’re running a sales team that lives in Salesforce and needs tight phone-to-CRM integration. Overkill for a 5-person professional services office.

Ooma Office. My most common recommendation for businesses with 1–15 users. $19.95/user/month, includes a physical ATA adapter (OBi device) in the box for desk phones, good call quality, and a functional auto-attendant that doesn’t require professional setup. The app works well on iOS and Android. Ooma is not the flashiest platform, but it works, the pricing is honest, and support is responsive. For a small office that needs reliable phone service and basic auto-attendant without complexity, this is the right call.

Nextiva. Strong choice if you need CRM features, call analytics, or you’re running a small call center operation. Pricing is competitive with RingCentral at the feature-equivalent tier. I’ve deployed this for professional services firms (law offices, insurance agencies) where the ability to pull up account notes during a call is genuinely useful.

Google Voice for Business. Part of Google Workspace. Cheapest option at $10/user/month as an add-on to your existing Workspace subscription. If your team already lives in Google and your phone needs are minimal — inbound calls, basic routing, voicemail transcription — it’s a reasonable option. The limitations are real: auto-attendant features are basic, the call quality is usually fine but not consistently excellent, and there’s no support for physical desk phones (software only). If you’re comfortable with those trade-offs, it’s hard to argue with the price.

3CX. A self-hosted platform worth knowing about. 3CX is a Windows or Linux-based PBX that you run on your own server (or a VPS). The software itself is free for up to 8 simultaneous calls; paid tiers are reasonably priced. If you have a technical person on staff who wants full control over the phone system, 3CX is a capable platform with a large support community. I’ve deployed it for businesses that had specific call routing requirements that cloud providers couldn’t accommodate. Not for the technically averse.

---

Field Notes — Weekly tools, techniques, and deals from J.D. Sweeney. Subscribe free →

---

Hardware: What You Actually Need on the Desk

The clean answer is: you might not need anything. Every cloud VoIP platform has a smartphone app (iOS and Android) and a desktop app (Windows and Mac). If your team is comfortable using a headset on a laptop or a phone app on their mobile, you can run a full VoIP system without buying a single piece of desk hardware.

If you want physical desk phones — and there are legitimate reasons to, especially for a receptionist position or a conference room — Poly (formerly Plantronics/Polycom) VVX series phones are the industry standard. The VVX 350 is a solid 6-line mid-range desk phone that works with every major VoIP provider. It handles multiple lines, has a clear display, supports Power over Ethernet so you don’t need a power adapter, and the call quality is consistently good. Street price is roughly $80–$120.

For a conference room, the Poly Trio series is built for the purpose — hands-free with multi-directional microphones. More expensive ($400–$500+), but if you’re running client calls from a conference room, the audio quality improvement over a speakerphone app is meaningful.

Ooma ships with an ATA adapter that lets you plug a standard analog phone into the VoIP system — useful if you have existing analog phones you want to reuse. For new setups, IP phones like the VVX 350 are cleaner.

One thing to watch: some VoIP providers lock you to their own hardware or charge a provisioning fee for third-party phones. Ooma, 3CX, and most other standard SIP-based providers work fine with any SIP-compatible phone. A few providers (some hosted platforms) use proprietary provisioning that makes it harder to use non-approved hardware. Check before you buy the phones.

---

Network Configuration: The Part Most Businesses Skip

This is where VoIP deployments fail. Call quality problems — dropped calls, choppy audio, one-way audio, echo — are almost always network problems, not service problems. If you’ve set up VoIP and it sounds bad, fix your network before you call support.

QoS (Quality of Service). Your router needs to prioritize VoIP traffic. Voice calls use a protocol called RTP for the audio stream. If your router doesn’t specifically deprioritize other traffic to protect RTP packets, a large file upload or a video stream will cause your calls to break up. On a business-grade router (TP-Link Omada, UniFi) this is done through traffic control rules that identify RTP traffic and assign it a high priority queue. On a consumer router, your options are limited and often ineffective.

Separate VLAN for VoIP. If you’re running IP desk phones, they should be on their own network segment — separate from your staff computers, guest WiFi, and everything else. Most business VoIP phones support VLAN tagging (a setting in the phone’s admin interface). Your switch needs to be configured to put voice traffic on the voice VLAN. This is cleaner, more secure, and makes it easier to apply QoS rules consistently. If you’re using only softphones (apps on computers or phones), this matters less, but it’s still good practice.

Latency and jitter requirements. VoIP calls need low, consistent latency. The target is under 50ms one-way latency to your VoIP provider’s servers, with jitter under 30ms. You can test this from your network using tools like PingPlotter or simply by looking at the statistics in your VoIP provider’s portal during a test call. If your latency is consistently above 100ms or your jitter is high, the problem is usually your ISP connection or a congested network — not something QoS alone can fix.

The TP-Link Omada WiFi 7 router BE550 is worth mentioning here specifically for QoS implementation — if you’re running VoIP on a network that also carries significant data traffic, having a router that can properly classify and prioritize voice traffic is not optional, it’s the foundation of a working VoIP deployment.

---

Number Porting: Don’t Cancel Your Old Service Yet

If you have an existing business phone number you want to keep — and you should keep it, it’s in every directory and in your customers’ contacts — you need to port it to your new VoIP provider. This is a standard process, but there are a few things that will make it easier.

First, don’t cancel your existing phone service before the port completes. The number needs to be active at the old carrier for the port to go through. If you cancel first, you lose the number. The typical porting timeline is 2–4 weeks, though it varies by carrier. Some carriers fight number ports harder than others (especially if they know they’re losing your business). Document everything.

What you need to initiate a port: your account number with the current carrier, your billing address on file, and the PIN or passcode on the account (call your carrier to confirm what they have on file — they sometimes set a default PIN you don’t know about). Your new VoIP provider will walk you through submitting a Letter of Authorization (LOA).

During the porting window, keep your old service running in parallel. Test everything on the new system before the port finalizes. Once the port is complete, calls to your number will ring on the new system.

---

E911: The Compliance Requirement Nobody Mentions

Cloud VoIP has an E911 requirement that differs from traditional phone service. With a landline, the 911 dispatcher automatically knows your address because it’s tied to a physical line. With VoIP, you have to register a physical address with your provider for emergency calls.

Every VoIP provider has a process for this — usually an address verification step during account setup, and a dedicated E911 address field in your account settings. If your employees are using the VoIP app from home or remotely, they should update their E911 address in the app settings when they’re working from a location other than the office.

This isn’t optional. Federal regulations require VoIP providers to offer E911 capability. Make sure your provider has a valid address on file and that it’s the right address for where your phones are physically located.

---

My Recommendation for Most Small Businesses

For a business with 1–15 users that wants reliable VoIP without IT complexity: Ooma Office. $19.95/user/month, physical ATA adapter included, functional auto-attendant, good mobile app, honest pricing. Get it, port your number, set up the auto-attendant, install the app on staff phones, and you’re done.

For a business with 15–30 users that needs CRM integration or more advanced call routing: Nextiva or RingCentral — Nextiva if you want better value, RingCentral if you need the broadest integration ecosystem.

For a technically capable team that wants control and lower long-term costs: 3CX on a small VPS or local server. Budget an honest half-day of setup time and expect to read some documentation.

Before any of that: make sure your network is ready. Configure QoS on your router, set up a voice VLAN if you’re using IP desk phones, and verify your latency numbers. A $20/month VoIP service on a properly configured network will sound better than a $50/month service on a neglected consumer router. The service is the easy part. The network is what makes or breaks the experience.