Dallas-Fort Worth, TX
What does onboarding to a new business phone system look like for a DFW office?
Onboarding to a new business phone system runs in a set order: discovery, a full number inventory, routing design, the port, device setup, app installs, staff training, cutover and a follow-up check. A multi-line DFW office should plan on a week or two from clean port paperwork to cutover, and keep the old service running until the port completes.
Book a DemoUpdated October 2026 · Cleod9 Voice, Arlington, TX
Nine steps
Discovery, numbers, routing, port, devices, apps, training, cutover and follow-up, done in that order.
Port timing
Simple ports are generally targeted at one business day. Multi-line offices should plan on a week or two.
Keep old service
Never cancel your current service before the port completes, because canceling releases the number.
Run in parallel
Keep both systems running during the port so calls always land somewhere that someone answers.
The order matters more than the speed
Most phone switches that go badly go badly for the same reason: the steps happen out of order. Phones get ordered before anyone knows how calls should flow. The port gets submitted before anyone has found the fax line. Staff see the new phones for the first time on cutover morning. The fix is not speed. It is sequence.
Here is the order a well-run onboarding follows, from the signed agreement to the end of the first week live. The steps are the same for a small dental office in Grapevine and an HVAC contractor in Garland with dispatchers, technicians in trucks and a second shop in Denton. The contractor simply has more numbers, more routing and more people to train. If you are still choosing a provider to run this process with you, start with our hub on which DFW VoIP providers offer hands-on local support and onboarding.
Steps 1 and 2: discovery and the number inventory
Discovery is a conversation about how your office actually works, not how the org chart says it works. Who picks up first? Who covers the front desk at lunch? Which calls should reach the owner’s cell after hours, and which should never go there? Who works from home on Fridays? The answers shape everything that follows.
The number inventory runs alongside it. Pull the latest bill from every carrier you pay and list every number on it. Offices are often surprised by what turns up. The list has to be complete before the port order is written, because a number left off the order stays behind with the old carrier.
- The main number, plus any number printed on signs, trucks, the website or business cards.
- Direct lines for individual staff, including ones set up years ago and forgotten.
- Fax lines and lines used by alarm panels, elevators or gate entry, which each need their own decision.
- Toll-free numbers and any tracking numbers used in advertising.
- Which numbers send or receive texts, since business texting needs its own registration.
- For each number: the carrier, the account number and the exact service address on file, suite included.
Step 3: routing design
With discovery notes and the number list in hand, the next job is drawing how calls move. Start with the main number. Does it ring a group of desks at once, ring the front desk first, or go to an auto attendant? Then work through the exceptions. What happens when nobody answers? Where do calls go after hours, on holidays, or on a winter morning when ice keeps half the staff at home?
Write the design down as a one-page diagram before anything is built. It becomes the reference for the build, for training and for every change after go-live. Keep any auto attendant menu short, because a long menu teaches callers to press zero. Decide now where calls go if the office loses internet or power, such as the mobile apps or another number. That rerouting has to be set up in advance; it cannot be invented during the outage.
Cleod9’s platform supports ring groups and an auto attendant, and its AI Voice Concierge can answer overflow or after-hours calls, take messages, book appointments and warm-transfer a caller to a person. For the design choices in more depth, see our guide on how a small DFW office should route incoming calls.
Step 4: what keeps a port on schedule
A port needs a letter of authorization and a recent bill from your current carrier. The details on the authorization have to match the losing carrier’s records exactly: business name, service address, suite number, account number and the authorized contact.
Check for a port-out freeze before anything is submitted. If one is on the account, only the account holder can lift it, and it has to come off first.
Federal rules require carriers to complete simple ports within one business day, and a carrier cannot refuse a valid port request. A multi-line office should plan on a week or two from clean paperwork to cutover.
Step 4: what sends a port back
A mismatch is the most common reason a port gets rejected, and the usual culprits are small: a suite number written differently from the carrier’s records, or an authorized contact name that belongs to an office manager who retired. Each rejection means correcting the paperwork and submitting again.
The costliest mistake is canceling the old service early. Canceling releases the number, which is exactly the outcome a port exists to prevent. Leave the old account alone until the port completes.
Run both systems in parallel while the port is pending. Calls keep arriving on the old lines until the moment they move, so nobody misses a customer while the paperwork works its way through.
Steps 5 and 6: devices and apps
Device setup and app installs happen while the port is pending, so everything can be tested before the numbers move. On Cleod9, one extension follows each person across a desk phone, a desktop or browser app and a mobile app, and desk phones are optional. That makes this step partly a decision about who needs hardware at all.
Desk phones need power and internet, often from a PoE network switch, so confirm the switch can power every phone before they arrive.
One voice call needs about 100 Kbps each way, and Cleod9 recommends planning for at least double the minimum on upload.
Calls and texts placed from the mobile app show the business number, not the employee’s personal cell number.
Each office phone needs a 911 location, the street address plus floor or suite, entered before go-live.
The free C9 Speedtest gives a quick read on your office connection before cutover. For a softphone or mobile app used away from the office, the 911 call should carry a dispatchable location where technically feasible, which is why the location on file has to stay current. Federal rules under Kari’s Law and RAY BAUM’S Act cover direct 911 dialing and location information on multi-line systems. This page is general information, not legal advice.
Steps 7 and 8: training and cutover
Training belongs in the days just before cutover, close enough that people remember it and early enough that questions get answered before live calls arrive. Keep sessions short and split them by role. The front desk needs transfers and call pickup down cold, managers need their ring groups and voicemail, and remote staff need the mobile app. Cleod9’s user guides for the apps and desk phones give everyone a place to look things up afterward, and our page on training office staff on a new cloud phone system lays out a plan by role.
Cutover is the moment the port completes and calls start arriving on the new system. Have someone from the provider reachable that morning, and run a short test script before anyone declares the job done.
- Call the main number from an outside cell phone and follow every branch of the auto attendant.
- Let a call ring unanswered to confirm where it rolls and that voicemail plays the right greeting.
- Place outbound calls from a desk phone and from the mobile app, and check the caller ID that appears.
- Switch to the after-hours schedule, or wait until closing, and confirm where calls land.
- Confirm that fax, alarm and other special lines ended up where the routing design says.
- Schedule cancellation of the old service only after every number has ported and tested.
Step 9: the first week and the follow-up
The first week live is when the small things show up. A ring group rings too long before it rolls over. A part-time employee never installed the app. The receptionist wants a one-touch button for the warehouse that nobody thought of during discovery. None of this means the setup failed. It means real calls are doing what test calls could not.
Collect those notes in one place during the week, then go through them with the provider in a single follow-up conversation. Adjust the routing, fix the greeting, add the missing button. From there, the system moves out of onboarding and into ordinary support, which carries its own expectations. Those are covered in our guide to what support to expect after go-live.
Common questions
How long does onboarding to a new phone system take?
For a small office, roughly four weeks is a reasonable planning estimate, not a promise; most of it is waiting on the port. The exact time depends on how many numbers you have, how clean your paperwork is and how much routing you need. Within that, simple ports are generally targeted at one business day, and a multi-line office should plan on a week or two from clean paperwork to cutover. Ask any provider for a written schedule.
What should we gather before onboarding starts?
Collect the most recent bill from every carrier you pay, a list of every number on those bills and the account number for each. Note the exact service address on file, including the suite, and the name of the authorized contact on each account. Add a staff list showing who should answer what, and flag any lines used by fax machines, alarm panels or gate entry. That packet answers most of what discovery will ask.
Should we cancel our old phone service once we sign?
No. Keep the old service active until the port completes and every number has been tested on the new system. Canceling releases the number, and the whole point of a port is to keep it. Running both systems in parallel during the port is the sensible approach. Once everything has moved and tested cleanly, cancel the old account in writing and keep a copy of the confirmation.
Do we have to buy new desk phones?
Not necessarily. On Cleod9, desk phones are optional. Each person’s extension can run on a desktop or browser app and a mobile app instead, and many offices mix the two: desk phones at reception and in shared rooms, apps for everyone else. If you want to keep the handsets you already own, ask the provider whether your specific models will work on the new system before you plan around them.
Can the office keep taking calls during the switch?
Yes, if the switch is run properly. During the port, calls keep arriving on your old lines while the new system is built and tested alongside them. When the port completes, the numbers move and calls start arriving on the new system. The risky moments are an early cancellation of the old service and a cutover with no test script, and both are avoidable with planning.
What happens if our port gets rejected?
The losing carrier sends it back with a reason, and the most common one is a detail that does not match its records, such as a suite number or the authorized contact’s name. The fix is to correct the authorization and resubmit. A carrier cannot refuse a valid port request, so a rejection usually means a paperwork problem, not a dead end. Keep the old service running while it gets sorted out.
Talking to Cleod9
Before any demo, pull the latest bill from every carrier you pay and list every number on it. That list is the start of steps 1 and 2, and it shows quickly how much porting and routing work lies ahead.
Bring it to the first conversation with a rough sketch of how calls should flow, and ask which of these nine steps the provider handles and which fall to your office. Cleod9 supports its own customers locally, so the person you work with is in your time zone and can come on site if needed. Book a demo to start that conversation.