Short answer: Change the forwarding, not the number, and overlap the two services for at least one full weekend. Before the old vendor goes dark, get your call and message records out and get the termination clause of the BAA honored in writing — returning or destroying your patient data is an obligation, not a courtesy.
Practices change answering services for predictable reasons: a missed urgent call, a price increase, an operator who said something they should not have, or the slow realization that most of the volume is scheduling questions being handled by expensive humans.
The switch itself is usually treated as a procurement exercise. It is really a cutover, and cutovers have a specific failure mode — the window where neither system is clearly responsible for the phone.
If you have not yet chosen the replacement, the diligence questions come first: what to require before you sign an answering service covers the BAA and data-handling side, and the after-hours answering comparison covers cost per resolved call. This page assumes the decision is made and the job now is to land it cleanly.
Do not move the number. Move the forwarding.
The single most important structural decision, and the one that removes most of the risk: your published number should belong to your phone system, not to your answering service.
If the number patients dial is a number the answering service owns, then changing vendors means changing the number on your website, your door, your prescriptions, your insurance directories, and every referral partner's address book — and it means the old vendor holds your inbound traffic hostage for as long as it takes. If the number is yours and the answering service is simply a forwarding destination, switching is a routing change you can make in an afternoon and reverse in a minute.
If you are currently in the first situation, fix that as part of this switch rather than after it. Port the number to your own phone system, then forward from there. It is the last time you will have to do it.
Number portability has its own timeline and its own traps — the mechanics are in the business phone number porting guide, and the wider version of this exercise, changing the whole phone system rather than the answering layer, is in switching business phone providers.
The BAA does not just lapse
This is the part practices skip, and it is the part with actual obligations attached.
A business associate agreement contains termination provisions dealing with what happens to your patients' information when the relationship ends. The general expectation is that the business associate returns or destroys the protected health information it holds, and stops using it — and where returning or destroying it is genuinely infeasible, the protections continue to apply to whatever is retained for as long as it is retained.
- ▸Read your own agreement's termination clause before you give notice. The specific commitments vary, and you are about to rely on them.
- ▸Ask, in writing, what the vendor holds. Message logs, call recordings, transcripts, escalation records, the account's intake script, and any copy of your rotation.
- ▸Get a written statement of what was returned and what was destroyed, including the subcontractors and overflow centers in the chain, not just the primary vendor.
- ▸Confirm the retention window for anything they keep. If backups mean recordings persist for another ninety days, that is a fact you want recorded rather than discovered.
None of this is adversarial, and a healthcare-ready vendor handles it as routine. A vendor that finds the request unusual has told you something about how it has been handling your data all along — the same signal the eight diligence questions are designed to surface before you sign rather than as you leave.
Get your records out first
Whatever the vendor destroys on termination, you may want a copy of first — and the moment after you give notice is the worst time to discover an export costs money or is not offered.
Two things are worth pulling. The first is the operational history: call volumes by hour, by day of week, and by category. That data tells you what the new service actually needs to handle, and it is the only honest basis for judging whether the switch improved anything.
The second is anything with a clinical or legal tail — escalation logs and message records tied to specific patient calls. Where those constitute part of the record, they should land somewhere covered inside your own systems before the vendor's copy goes away. If recordings are involved, the retention and access questions around them are their own subject: recording patient calls.
Overlap. Do not cut over.
The cheapest insurance in this whole exercise is paying two vendors for a couple of weeks.
Run the new service in parallel before it is load-bearing. Send it test calls across every tier of your script. Then move real traffic during a period you can watch — a weekday evening, not a holiday weekend — and keep the old service contracted and reachable until the new one has covered at least one full weekend without incident.
The reason to overlap rather than cut is that the failures which matter are not the ones visible in a test. They are the ambiguous call at 1 AM, the escalation when the primary does not answer, the holiday when the rotation is wrong. Those need real time to appear, and you want the ability to fail back while they do.
Test the failure path deliberately during the overlap, not just the happy path — place an urgent call and let the on-call phone ring out, so you can watch the new vendor's chain actually run. What that chain should look like is in when the on-call provider does not answer.
The cutover checklist
- 1.Confirm the published number belongs to your phone system, not the outgoing vendor. Port it first if it does not.
- 2.Read the existing BAA's termination clause and note what the vendor owes you.
- 3.Sign the new vendor's BAA before any live patient call reaches them — including during the parallel-run period, which is live traffic.
- 4.Build and approve the new script rather than letting the vendor port the old one unread.
- 5.Publish the on-call rotation to the new service in the format it reads, and tell the providers and the backups.
- 6.Export call history, message records, and escalation logs from the outgoing vendor.
- 7.Run test calls across every tier, including one where nobody answers.
- 8.Move real traffic on a weekday evening, keeping the old service contracted.
- 9.Cover one full weekend before terminating.
- 10.Give notice, then get the return-or-destroy confirmation in writing, covering subcontractors.
- 11.Remove the old vendor's forwarding rules, saved numbers, and any lingering access to your systems.
The question worth asking during the switch
A vendor change is the one moment when the whole after-hours design is open for inspection, which makes it the natural time to ask whether the shape is still right rather than just who is filling it.
Most practices find, when they look at the call history they just exported, that the large majority of after-hours volume is administrative — hours, directions, reschedules, refill requests — and that they are paying per-call rates for a human to handle it. That is a structural finding rather than a vendor problem, and it usually argues for resolving that tier automatically and reserving the human service for the calls that need one. The operational case is in never miss a call again; what an automated system can genuinely resolve rather than route is covered by our sister company at AI voice agents for business.
And if the switch is being driven by a compliance concern rather than cost or quality, the practice-wide program that sits behind it — risk assessment, vendor management, breach response — is IT territory: the HIPAA compliance guide for healthcare IT.
Frequently asked questions
Will we lose our phone number if we change answering services?
Only if the number belongs to the answering service rather than to you. The durable arrangement is to own the published number on your own phone system and forward to whichever service you use, which turns a vendor change into a routing change. If the outgoing vendor owns the number, port it before you switch.
What happens to our patient data when we terminate an answering service?
The business associate agreement's termination provisions govern it. The general expectation is that the vendor returns or destroys the protected health information it holds and stops using it, with protections continuing to apply to anything retained where return or destruction is infeasible. Ask for written confirmation covering subcontractors and overflow centers, not just the primary vendor.
How long should we run two answering services in parallel?
Long enough to cover at least one full weekend without incident, and ideally to see an ambiguous overnight call and a real escalation. The failures that matter do not appear in test calls, so the overlap exists to buy the ability to fail back while they surface.
Do we need a new BAA with the incoming vendor before the trial?
Yes, if the trial involves live patient calls, because a parallel run is live traffic. A signed agreement should be in place before any real patient call routes to the new service. Testing with internal calls is the alternative if the agreement is still in review.
What should we take with us from the outgoing service?
Call volumes by hour, day and category, which is the only honest basis for judging whether the switch improved anything; plus escalation logs and message records tied to specific patient calls, which should land inside your own covered systems before the vendor's copy is destroyed.
Owning the number is what makes the next switch easy. Our pricing is public, and the plans that carry a BAA are marked on the healthcare page.