Key takeaways
- Port numbers on a planned date with a written order, and keep the old service live until every number is confirmed working.
- Multi-line systems must allow direct 911 dialing, notify a central point and send a dispatchable location; remote and softphone users need the same.
- A VoIP vendor that stores voicemail, recordings or call logs with patient details needs a signed business associate agreement.
- Plan for internet outages with automatic failover to mobile phones or a second connection before go-live day.
Why practices are moving, and what can go wrong
Most practices consider VoIP, or cloud phones, for three reasons: flexible routing, reporting that old systems cannot provide, and lower maintenance than an on-site phone system. Cost is often part of it too, since practice budgets are under pressure. In a June 2026 MGMA poll, 84% of medical groups said year-to-date operating costs were higher than at the same point in 2025[1].
- Reported higher operating costs 84%
Source: Medical Group Management Association (MGMA), 2026[1]
Show the data
| Item | Value |
|---|---|
| Reported higher operating costs | 84% |
The risks are just as concrete. A badly planned port can leave the main number dead for a day. A misconfigured system can route 911 calls without the right address. A vendor without the right agreement can leave the practice exposed on voicemail and recordings. And a single internet connection becomes a single point of failure for every phone in the building. Each of these is avoidable with checks done before the contract is signed.
The pre-switch checklist
| Area | What to ask the vendor | A good answer looks like |
|---|---|---|
| Number porting | Who files the port, what documents are needed, what date is committed? | Vendor files it, you sign a letter of authorization, a firm date in writing |
| 911 dialing | Can every handset and softphone dial 911 directly? | Yes, no prefix needed, tested on install |
| 911 location | How is the caller's dispatchable location sent, including remote staff? | Per-device location, updated when staff work from home |
| Agreement | Will you sign a business associate agreement? | Yes, before go-live, covering voicemail, recordings, transcripts and logs |
| Security | Are calls, voicemails and recordings encrypted, and who can access them? | Encryption in transit and at rest, role-based access, audit logs |
| Failover | What happens when our internet goes down? | Calls reroute automatically to mobiles or another site within minutes |
| Call quality | Can you assess our network before install? | A network readiness test with a written result |
| Exit | Can we take our numbers and data if we leave? | Yes, standard export and porting support |
Number porting without a dead line
Porting moves your existing numbers to the new provider. Federal rules require carriers to complete a simple wireline or simple intermodal port within one business day, unless the new provider or the customer asks for a longer period[2]. Many practice ports are not simple, though: several numbers, fax lines, toll-free numbers and lines tied to alarms or elevators all add complexity and time.
- Inventory every number first: main line, direct lines, fax, toll-free, after-hours, alarm and elevator lines.
- Get a copy of a recent bill from the current carrier; the name, address and account number on the port request must match it exactly.
- Ask the current carrier for any account PIN or passcode needed to release the numbers.
- Schedule the port for a quiet day, usually mid-week and early, and never the day after a holiday.
- Do not cancel the old service until every number has been tested on the new system, inbound and outbound.
Fax numbers are the most common surprise. Pharmacies, hospitals and labs still send faxes to many practices, so decide early whether fax moves to an online fax service or stays on a separate line, and test it with a real pharmacy before cutover.
911: the rules that apply to your system
A practice phone system with multiple lines is a multi-line telephone system under federal rules. Those rules require that a user can dial 911 directly from any station without an extra digit such as 9, that the system notifies a central location at the facility when 911 is dialed, and that the system can send the caller's dispatchable location to the 911 center[3]. Installers, managers and operators all have obligations under the rule.
- Set the dispatchable location per device, down to the suite or floor if your building has several.
- Decide who gets the 911 notification: usually the front desk lead and the practice manager, by screen alert and text.
- For staff working remotely on softphones, make sure they can update their location and know they must.
- Test 911 routing at install with the vendor's test procedure, and retest after any office move.
The agreement and the security settings
A VoIP provider that stores voicemails, recordings, transcripts or call logs containing patient information is handling protected health information for you. HIPAA lets a covered entity share that information with a business associate only with satisfactory assurance, in a business associate agreement, that it will be safeguarded[4]. Get the agreement signed before any patient call goes through the system.
The Security Rule also expects technical safeguards for electronic protected health information, including access controls, audit controls, and transmission security to guard against unauthorized access to information sent over networks; encryption is an addressable specification that you assess and document[5]. In practice, ask the vendor to show the admin console, how user access is set and removed, and where access logs live.
Failover and call quality
When an on-site phone system loses power, it often still works on copper lines. A cloud system depends on your internet. Plan the failure before it happens.
- Configure automatic rerouting: if the office desk phones go offline, calls ring to designated mobile phones or the vendor's mobile app.
- Consider a second internet connection from a different provider, with automatic failover on the router.
- Put the router, switch and phones on a battery backup sized for at least a short outage.
- Ask the vendor for a network readiness test. Call quality problems usually come from shared bandwidth, old switches or Wi-Fi handsets far from an access point.
- Prioritize voice traffic on the office network so a large file upload does not make calls choppy.
A cutover plan, week by week
Four weeks out: design
Agree call flows, queues, after-hours routing and greetings on paper with the front desk lead. Record new greetings. Confirm the signed agreement and the 911 settings.
Three weeks out: build and train
Vendor builds the system with temporary numbers. Staff practice on test phones: transfers, parking calls, queue callback, voicemail.
Two weeks out: test
Call every route from outside, including after-hours and holiday paths, and test failover by unplugging the internet for ten minutes.
Port day
Have the vendor on a live call. Test each number inbound and outbound as it ports. Keep a printed list of numbers and their status.
First week live
Check reports daily for abandoned calls and quality complaints. Keep the old carrier account open until the end of the week, then cancel in writing.
Training staff for day one
New phones change muscle memory. Staff who could transfer a call blindfolded on the old system will fumble the first morning on the new one, and that fumbling happens in front of patients. Training is cheap insurance.
- Give every user a one-page card for their role: answer, hold, transfer, park, send to voicemail, log in and out of a queue.
- Run two practice sessions on test phones before port day, with staff calling each other.
- Teach the front desk lead how to change routing for a closure and how to read the queue display.
- Show remote staff how to set their location on the softphone, and why it matters for 911.
- Agree how staff report problems in the first week: a shared list, reviewed with the vendor each afternoon.
What to measure in the first 90 days
Use the new system's reporting to prove the switch worked. Compare the first 90 days with whatever baseline you had: abandoned calls in the busiest half-hours, longest hold times, voicemails per day, and the number of call quality complaints from staff or patients. If abandoned calls have not fallen, the call flows probably copied the old setup instead of using queues and callback properly, and it is worth a design session with the vendor to fix that while the contract is new.
Worked Example: a two-site practice
Example: a fictional dermatology group with two offices and 14 numbers plans a move to cloud phones. The inventory turns up two numbers nobody remembered, one tied to the second site's alarm panel. The group keeps that line with the old carrier, moves fax to an online service, and ports the rest on a Wednesday morning.
Example outcome: twelve numbers port by mid-morning and are tested inbound and outbound within an hour. One direct line fails because the port request used the wrong suite number; the vendor corrects it the next morning while calls to that line forward to the main queue. Failover to mobile phones is tested once more on the first Friday. Remote billing staff set their softphone locations to their home addresses on day one.
For a broader view of which features to prioritize, see phone system features worth paying for, and for privacy questions, what makes a phone system HIPAA compliant.
Frequently asked questions
Is VoIP HIPAA compliant?
VoIP can be used in a HIPAA-compliant way when the vendor signs a business associate agreement where it handles patient information and the practice configures access controls, audit logs and transmission security. The technology alone does not make it compliant.
How long does porting a medical office number take?
Simple ports must be completed within one business day under federal rules, but practices with many numbers, fax lines or toll-free numbers often take longer. Get a committed date in writing and keep the old service live until testing is complete.
What happens to 911 calls on a cloud phone system?
The system must allow direct 911 dialing, notify a central point in the office and be able to send the caller's dispatchable location. Each device needs a correct location, including softphones used by remote staff.
What if our internet goes down?
Configure automatic failover so calls ring to mobile phones or another site, and consider a second internet connection and battery backup for network equipment.
References
Medical Group Management Association (MGMA) (2026). Operating costs keep climbing for medical practices in 2026 (opens in a new tab) โ
Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (current). 47 CFR 52.35 - Porting intervals (opens in a new tab) โ
Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (current). 47 CFR 9.16 - General obligations: direct 911 dialing, notification, and dispatchable location (opens in a new tab) โ
Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (current). 45 CFR ยง 164.502 - Uses and disclosures of protected health information: General rules (opens in a new tab) โ
Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (current). 45 CFR 164.312 - Technical safeguards (opens in a new tab) โ