The sales call makes it sound like a weekend project. New phones show up, you plug them in, you save money. Sometimes it really does go that smoothly. When it does not, the failure is almost never the phones. It is the number that did not move on schedule, the call flow nobody designed, or an internet connection that was fine for email and is not fine for voice.
We move Denton County businesses onto internet-based phone systems regularly, and the ones that go well share the same habits. They start the number work early, leave the old system running longer than feels necessary, and decide how calls should flow before anybody logs into a portal. Here is what that looks like.
What Porting Actually Involves
Porting means moving your existing number from one provider to another. The FCC’s consumer guidance describes it as a process that can be done between wireline, IP, and wireless providers, so a number that lived on a copper line for twenty years can generally move to an internet-based service.
It takes longer than the sales rep suggests because a port is a coordinated handoff between two companies, and the details have to match exactly. Your new provider submits a request. Your old provider validates it against their records. Any mismatch, a suite number, an old business name, a billing address that changed three years ago, sends the request back to the start of the line.
Two FCC facts are worth holding onto. First, your old company cannot refuse to port your number, even if you owe money for an outstanding balance or termination fee. That is leverage, and people do not realize they have it. Second, the FCC says its rules require simple ports to be processed in one business day. A single line is a simple port. Twenty numbers, a hunt group, and a fax line are not, so ask your provider what category your order falls into and what interval they commit to in writing.
Do Not Cancel the Old Service Yet
This is the single most expensive mistake in the project, and it is easy to make because cancelling feels like progress. The FCC’s guidance is direct: do not terminate your service with your existing company before initiating new service with another company. Cancelling releases the number back into the pool, and once that happens no amount of escalation gets it back.
So plan for a paid overlap. Run both systems for a few weeks. The new phones can be live on temporary numbers while your main number still rings the old system, and when the port completes, calls simply start arriving on the new platform. You pay two bills for one month. That is cheap compared to reprinting everything you own.
Design the Call Flow Before You Configure Anything
Most bad phone systems are not misconfigured. They are unplanned. Somebody opened the admin portal, started clicking, and the structure that emerged is whatever the software suggested by default. Sketch it on paper first, with your team in the room. Answer these before you touch a setting:
- Who answers first: a person, a menu, or a ring group. If a live person answers today and customers like it, do not replace that with a menu just because you can.
- What happens on no answer: after how many rings, and where the call goes next. Every path needs a defined end.
- What after-hours means: your actual hours, not the software default, plus holidays you observe.
- Where voicemail lands: and who genuinely owns that mailbox. Voicemail to email only helps if a real person reads it.
- Who can transfer to whom: and whether people know how. This is the number one complaint after go-live.
Your Internet Connection Is the Deciding Factor
Voice is not like web browsing. A web page can arrive late and you never notice. A voice packet that arrives late is worthless, because the conversation already moved on. That is why a connection that streams video perfectly can still deliver terrible calls.
Raw speed is rarely the problem. Microsoft’s Teams network documentation lists audio bandwidth starting at a minimum of 10 kbps up and down per stream, with 58 kbps recommended. A call uses a tiny slice of a modern business connection. Consistency is what matters, and Microsoft’s network performance guidance gives targets:
- Round trip time: under 60 ms is optimal, over 500 ms is poor. This is how long a packet takes to make the round trip.
- Average packet loss: under 0.5 percent is optimal, over 10 percent is poor. Microsoft notes loss ranges from individual packets with almost no impact to back-to-back bursts that cause complete audio cut-out.
- Jitter: under 3 ms is optimal, over 30 ms is poor. Microsoft explains that modern software absorbs some jitter through buffering, and you only hear it when jitter exceeds that buffer.
Measure these on your actual connection before you commit, not after. Prioritize voice traffic so a large file upload cannot flatten a customer call. If your phones live on the internet, an internet outage is a phone outage, the dependency we covered in what it means when the cloud goes down.
Plan for the Power and Internet Going Out
An old analog line kept working in a power outage because the phone company powered it. That is not how this works anymore, and the FCC says so plainly: VoIP service may not work during a power outage or when the internet connection fails or becomes overloaded. The FCC suggests considering a backup power supply, keeping a traditional line, or having a wireless phone as backup.
Build the fallback before you need it. Battery backup on the internet equipment, switches, and a few phones. A second internet connection on a different technology. A provider rule that forwards your main number to cell phones automatically when the office stops responding. Test that rule by actually unplugging things, at a time you choose.
Emergency calling deserves its own attention. The FCC advises providing your accurate physical address to your interconnected VoIP provider so emergency services can be dispatched to your location, and knowing your provider’s procedure for updating it. The FCC also warns that VoIP 911 calls may not connect to the call center serving your current location, or may not automatically transmit the caller’s number and location. If people work from other sites on office extensions, each location needs a correct address on file.
The Training Nobody Plans For
Here is the part cut from every project budget, and the cause of most week-one complaints. The phones work fine. Your team does not know how to use them.
Transfers are the big one. Warm transfer, where you announce the call, and blind transfer, where you send it through, are different buttons on every system, and nobody guesses correctly under pressure. Add parking a call, picking up someone else’s ringing phone, and using the app on a cell so the business number shows instead of a personal one.
Do a short live session before go-live, not a PDF afterward, and post a one-page cheat sheet at the desks that answer the most calls. Thirty minutes of training prevents weeks of workarounds, the same argument we made in why saving time beats saving money.
The Bottom Line
Moving to internet phones is a good idea for most small and mid-sized businesses. The features are better, the flexibility is real, and the monthly cost is usually lower. The projects that go badly did not pick the wrong vendor. They treated a number port like a same-day task, skipped the call flow design, never measured the connection, and assumed people would figure out the transfer button.
Start the port early. Keep the old service running. Draw the call flow on paper. Test the network. Plan for the power going out. Train the humans. All of it belongs before go-live, not after.
If you are considering a phone system change, we can review your setup, measure whether your connection is genuinely ready for voice, manage the port, and be there on go-live day. We will also tell you if staying put is the better call. Contact us today.
Sources:
Comments are closed