Switching to a VoIP Phone System — A Practical Small Business Guide

Sooner or later the phone system forces the issue. The old PBX in the closet needs a part nobody stocks, the vendor who installed it retired, or the phone bill arrives with charges for lines that haven't been used since two office moves ago.

Moving to a VoIP phone system — voice over your internet connection instead of copper lines — is one of the few IT projects that reliably costs less than what it replaces. It's also one of the easiest to do badly, because the quality of the result depends almost entirely on things the phone provider doesn't control: your network.

Here's what actually matters.

What You're Really Buying

A modern cloud phone system (often sold as UCaaS — unified communications as a service) replaces the box in your closet with a provider's platform. You pay per user per month, calls travel over your internet connection, and configuration happens in a web portal instead of a service call.

What that typically gets you:

• Auto attendants and call routing you can change yourself in five minutes
• Voicemail delivered to email, with transcription
• Softphone apps so a laptop or cell phone rings as the desk extension
• Business SMS from your main number
• Video meetings, and often team chat
• Call recording, queues, and reporting
• Failover rules that route to mobiles when the office internet dies

The two changes that matter most day to day are usually the least glamorous: staff can work anywhere without giving out personal cell numbers, and you stop waiting on a vendor to change a greeting.

The Part That Decides Whether It Sounds Good

Voice traffic is unforgiving in a specific way. A web page loading 200 milliseconds late is invisible. Voice arriving 200 milliseconds late is a conversation where both people keep interrupting each other.

The targets to design against:

• Latency under about 150 ms one way
• Jitter (variation in packet arrival) under roughly 30 ms
• Packet loss under 1% — voice degrades noticeably above that
• Roughly 100 Kbps in each direction per concurrent call with standard G.711 encoding

That bandwidth number surprises people because it's so small. Ten simultaneous calls is about 1 Mbps each way. Almost any business connection has the raw capacity.

Which is exactly the point: VoIP call quality problems are almost never bandwidth problems. They're contention problems. Someone starts a large cloud backup, a workstation begins pulling a Windows feature update, and voice packets queue behind them. The calls get choppy for eleven minutes and then it's fine again, which is why nobody can ever reproduce it for the provider.

The fixes are network-side:

• QoS with DSCP EF marking for voice traffic, honored end to end on your LAN, so voice packets jump the queue
• A separate voice VLAN to keep voice off the same broadcast domain as everything else
• PoE switches so desk phones get power and data on one cable, with a UPS on the switch
• Disable SIP ALG on your firewall or router. This "helpful" feature mangles SIP traffic and causes one-way audio and dropped calls more often than it helps. It is the first thing to check when calls behave strangely.
• Wired phones where possible. Wi-Fi handsets work, but they need a properly designed wireless network, not a consumer access point in a hallway.
• A second internet path if phones are business-critical — a cable or fiber primary with an LTE/5G failover

If any of that sounds like your network isn't ready, it's worth reading 5 signs your network infrastructure needs an upgrade before you sign a phone contract. Rolling out VoIP over a network with an aging switch and no QoS is how businesses conclude "VoIP sounds bad" when the phones were never the issue. Getting the network setup right first is not an upsell; it's the whole project.

The 911 Rules You Are Legally On the Hook For

This is the section most sales conversations skip, and it applies to multi-line telephone systems in US businesses.

Kari's Law requires that a user can dial 911 directly — no 9 first, no access code — and that the system sends a notification to a front desk, security, or another on-site point when a 911 call is placed, so someone can meet responders at the door.

RAY BAUM'S Act requires that a dispatchable location be transmitted with the 911 call: not just the street address, but enough detail to find the caller — building, floor, suite. For a multi-floor or multi-suite office, "1234 Example St" is not sufficient.

Two practical consequences:

1. Every registered device needs an accurate location on file, and it has to be maintained as people move desks.
2. Remote and hybrid workers need to update their registered address when they work somewhere else. A softphone in a home office in Arvada that reports the downtown office address will send an ambulance to the wrong building. Most platforms prompt for this — make it part of onboarding rather than trusting the prompt.

The FCC publishes the current requirements for 911 requirements for multi-line telephone systems. Ask any prospective provider directly how their platform handles both laws, and get the answer in writing.

Porting Numbers Without Losing Them

Your phone numbers are portable. The process is routine and the failure modes are boring and avoidable.

• Never cancel the old service before the port completes. If the losing carrier disconnects the number first, you may not get it back. Cancel after.
• Submit an exact match to the losing carrier's records — the billing name, service address, and account number as they have them, not as you'd write them. Nearly every rejected port is a mismatch here.
• Get a recent bill from the old carrier before you start; it has the details you'll need.
• Plan 2 to 4 weeks for business lines, longer if you have a PRI, and don't schedule a port for the week of your busiest season.
• Port the main number last, after you've tested with a temporary number and confirmed routing works.
• Check every place your number is published: Google Business Profile, your website, invoices, email signatures, Yelp, industry directories, vehicle wraps. Inconsistent phone numbers across the web also quietly hurt local search visibility.

Hardware: What to Buy and What to Skip

Desk phones still make sense for reception, warehouses, conference rooms, shared workstations, and anyone who takes calls all day. Buy phones that are certified by your provider rather than the cheapest compatible model.

Headsets matter more than handsets for anyone on calls constantly, and this is not the place to save $40.

Softphone-only works well for staff who are already on a laptop all day, and it's how most hybrid teams end up operating.

Analog devices need a plan. Fax machines, alarm panels, elevator phones, gate intercoms, and paging systems all have opinions about being moved to VoIP. Fax over IP is genuinely unreliable without T.38 support or a dedicated fax service. Alarm and elevator lines frequently need to remain on a copper line or a certified cellular replacement, and that's a code question — check before you disconnect anything.

What to Ask Every Provider

• What happens to calls when our internet goes down?
• Is number porting included, and what's your realistic timeline?
• How do you satisfy Kari's Law notification and RAY BAUM'S dispatchable location?
• Are there per-minute charges, and for what — toll-free inbound, international, SMS?
• What's the contract term, and what happens at renewal?
• Do we own our numbers and can we port them out without a fight?
• Is call recording included, and where is it stored and for how long?
• What support do we get at 7am on a Monday?

That last one separates providers more than any feature list.

Frequently Asked Questions

Will VoIP work with our current internet? Almost certainly, in terms of raw bandwidth. The real question is whether your firewall, switches, and Wi-Fi are configured to prioritize voice — which is a configuration project, not usually a new circuit.

What happens during a power outage? Desk phones lose power unless the switch is on a UPS, and your internet may be down anyway. This is why call-forward-to-mobile failover rules are worth configuring before you need them.

Can we keep our phone numbers? Yes. Port them; don't cancel first.

Is VoIP secure? It's an internet service, so it carries internet risks — toll fraud from weak extension passwords is the most common real-world problem. Use strong device credentials, restrict international dialing to the people who need it, and set spending alerts. Toll fraud is usually discovered on a bill, not in an alert, unless you set one up.

Should we host our own system instead? For most small businesses, no. Self-hosting means you own the patching, the redundancy, and the 911 compliance. Cloud platforms handle that as part of the subscription.

Get the Network Right First

A cloud phone system is a good deal for most small businesses. It only feels that way if the network underneath it is prepared for real-time traffic.

netkraft handles both halves for Denver-area businesses: assessing and configuring the network — QoS, VLANs, PoE, firewall settings — and managing the phone deployment, porting, and 911 registration so nothing falls between the phone vendor and the IT vendor.

Contact netkraft to talk through a phone system project, or read more about our network setup and managed IT support services.