Guide

The dropped call: reconnect, fall back, document, bill honestly

Summary

When a telehealth visit drops, follow a set sequence: wait briefly, try to reconnect on the same platform, then fall back to a pre-agreed backup channel such as a phone call, and reach the patient to confirm safety and continue or reschedule. Use a HIPAA-compliant channel, document the interruption and the actual time delivered, and bill only for the service you furnished — not the full session if it did not happen. Agree the backup plan at intake.

By Gale Editorial · Updated 2026-07-27. Every figure cited to a dated source. How we write.

What to do the moment a telehealth call drops

When the connection drops mid-session, run a fixed sequence rather than improvising. Wait a short, pre-set interval in case it self-recovers; attempt to reconnect on the same platform; if that fails, switch to the backup channel you agreed with the patient at intake, usually a phone call; and reach the patient to confirm they are safe and to continue or reschedule 1. Having the sequence written down keeps a stressful moment orderly.

Add a safety layer for the visits that need one. If the session was addressing acute risk and you cannot re-reach the patient on any channel, follow your safety protocol — which may include contacting the patient's emergency contact or, when warranted, requesting a welfare check through 911. Keeping 988 in the patient's documented safety plan means they have a route to crisis support even when your connection is the thing that failed.

The backup channel still has to be HIPAA-compliant

The fallback channel has to meet the same privacy standard as the primary one. A phone call is generally fine as audio-only telehealth, but a random consumer video or messaging app is not, and the COVID-era enforcement discretion that once tolerated non-compliant tools has ended 2. Decide your backup channel in advance and make sure it is covered by a business associate agreement where one is required, so the reconnection is not itself a violation.

This is why the backup plan is a setup decision, not an in-the-moment one. Pick a compliant phone or audio-video path, confirm the vendor will sign a business associate agreement, and write the fallback into your workflow. Scrambling for any tool that connects is exactly how a dropped call turns into a privacy incident.

Does a phone fallback still count as a covered visit?

Sometimes, but not automatically. For behavioral health, Medicare permits audio-only telehealth under specific conditions, so a phone fallback can still be a covered visit when those conditions are met and the code is audio-only eligible 3. Confirm the code on the current CMS telehealth list, which marks which services are payable by telehealth and which allow audio-only, and apply the audio-only modifier the payer requires 4. Commercial and Medicaid rules differ.

Because these audio-only allowances are volatile, treat any specific rule as current to July 2026 and reconfirm at the payer level. A phone segment that would be covered for one payer may be denied by another, so the safe habit is to verify audio-only eligibility per payer before you rely on it to close a session that started on video.

Billing honestly when the visit was cut short

Bill for the service you actually furnished, not the one you scheduled. If you select an office-visit level by total time and the session ended early, you count only the time actually spent, which can move you to a lower level 5. Time-based psychotherapy codes follow the same logic: the minutes delivered determine the code, and below the minimum there may be no separately billable session. Code the encounter that happened, on the channel it happened on 6.

The temptation after a frustrating drop is to bill the visit you meant to deliver. Resist it. If the reconnected portion plus the original portion together meet a code's requirements, bill that; if they do not, bill the lesser service or reschedule the remainder. Overstating time or completeness on an interrupted visit is the kind of error an audit finds and a clean record avoids.

Document the interruption

Write the interruption into the note the same visit. Record the time you connected, the time it dropped, your reconnection attempts, the channel you switched to, the minutes actually delivered, the clinical content, and any safety check you performed. This is both your billing support and your defense if the claim or the care is later questioned. When the internet drops mid-session, the note is the only durable record that the visit was handled responsibly.

A short structured block in your template makes this automatic: connected at, dropped at, reconnected via, minutes delivered, safety confirmed. Filled in while the timeline is exact, it is far more reliable than a reconstruction weeks later when a payer asks why the time billed does not match a continuous session.

Prevent the next drop

A few standing measures cut both the frequency and the cost of drops. Build redundancy into your practice technology — a wired connection with a cellular hotspot as backup — and put the fallback protocol in your telehealth consent so the patient knows the plan before it is needed. If corrected and re-sent claims from interrupted visits start piling up, that rework is part of the 4-8% question of whether to outsource billing rather than handle it yourself.

And remember that switching channels does not switch jurisdictions. Even on a phone fallback, the rule under everything still governs: the patient's physical location decides your authority. If a client has traveled, keep any state telehealth registrations current so a dropped-and-reconnected call does not quietly become a licensure problem on top of a technical one.

Common questions

Run a pre-set sequence instead of improvising: wait a short interval for it to recover, try to reconnect on the same platform, then switch to the backup channel you agreed with the patient at intake, usually a phone call. Reach the patient to confirm they are safe and to continue or reschedule. Having this written down keeps the moment orderly.

Often yes, if the phone counts as a compliant channel and the service supports audio-only. For behavioral health, Medicare allows audio-only telehealth under specific conditions, and you confirm the code is audio-only eligible on the current CMS list and apply the required modifier. Commercial and Medicaid rules differ, so verify the specific payer before assuming the phone portion is covered.

Bill for what you actually delivered. If you chose a code by time, count only the minutes truly provided, which may drop you to a shorter code or, below the minimum, to no separately billable session. Code the encounter that happened on the channel it happened on. Never bill a full session that the dropped connection prevented you from completing.

Yes. The fallback has to meet the same privacy standard as the primary platform. A phone call is generally acceptable as audio-only telehealth, but consumer video or messaging apps are not, and the pandemic-era enforcement discretion has ended. Choose your backup channel in advance, cover it with a business associate agreement where one is required, and document which channel you used.

Record the time connected, the time dropped, your reconnection attempts, the channel you switched to, the minutes actually delivered, the clinical content, and any safety check. That entry supports your billing and defends the care if it is later questioned. Writing it the same visit, while the timeline is exact, is far more reliable than reconstructing it from memory afterward.

Run your practice on Gale

The software is free. Gale earns one flat 3.5% all-in per paid transaction — only on transactions that actually pay. No subscription, no setup fee, no network cut.

Start or manage a practice →

References

  1. 1.U.S. Department of Health and Human Services (2026). Telehealth for providers. Telehealth.HHS.gov. linkHHS provider-facing telehealth operations guidance supporting a reconnect-and-fallback protocol for technical failures.
  2. 2.HHS Office for Civil Rights (2026). HIPAA and Telehealth. U.S. Department of Health and Human Services. linkThat telehealth must run on HIPAA-compliant arrangements now that the COVID enforcement discretion has ended, including audio-only guidance.
  3. 3.Centers for Medicare & Medicaid Services (2025). Telehealth Services. CMS Medicare Learning Network (MLN901705). linkMedicare's conditions permitting audio-only behavioral-health telehealth, relevant to a phone fallback.
  4. 4.Centers for Medicare & Medicaid Services (2026). List of Telehealth Services. Centers for Medicare & Medicaid Services (CMS). linkThe CMS list of telehealth services identifying which codes are telehealth- and audio-only-eligible.
  5. 5.Centers for Medicare & Medicaid Services (2023). Evaluation and Management Services Guide. CMS Medicare Learning Network (MLN006764). linkThat E/M office-visit levels selected by total time count only the time actually spent, under the 2021-plus framework.
  6. 6.U.S. Department of Health and Human Services (2026). Billing for telehealth. Telehealth.HHS.gov. linkHHS telehealth billing guidance on place-of-service and modifiers, so the claim reflects the service actually furnished.

https://www.gale.care/for-providers/th-dropped-call-protocol · 6 sources. Competitor details are cited to dated public sources and maintained as they change; figures are estimates, not commitments. Synthetic demonstration.

Findability, by specialty

How practices like yours get found in local search and AI answers — the honest playbook, per specialty.

SEO for private practices · SEO for AI search / answer engines (all verticals)