An AI phone agent for the PT front desk that's already checking someone in

A physical therapy or chiropractic front desk lives on the phone in a way few other practices do. A plan of care is not one appointment—it is a series, often multiple visits a week for weeks, and every visit can generate a call: a reschedule, a running-late, a cancellation that opens a slot someone on the waitlist wanted. Add referral paperwork arriving by fax, benefits questions, workers'-comp adjusters, and a patient asking whether to keep doing an exercise that hurt—while the person who could answer the phone is checking in the 2:00 p.m. evaluation.

ThunderPhone gives a PT, rehab, or chiropractic clinic an AI phone agent that answers immediately, works from clinic-written scripts and escalation rules, collects structured information, uses connected scheduling systems, and transfers the calls that need a person. It is a front-office worker, not a clinician: it never gives exercise instruction, never interprets pain or symptoms, and never changes a plan of care. Those boundaries are the design.

What a therapy-clinic agent can be configured to do

Every workflow below runs on clinic-written instructions. The agent follows the script, collects the fields the clinic requires, and escalates when a clinic-defined trigger is met.

New-patient scheduling with referral and prescription intake

The agent can take the first call from a prospective patient: collect contact details, the reason for seeking care in the caller's own words, location and schedule preferences, and insurance information the clinic chooses to take by phone—then book the evaluation through a connected calendar or practice-system API. Where the clinic requires a physician referral or prescription—requirements vary by state and by payer—the script collects the referring provider, what paperwork the patient has, and how it will arrive, and flags evaluations booked pending documentation. The agent never decides whether a referral is required; it collects what the script asks for and routes open questions to staff.

Recurring-visit series scheduling

A plan of care means booking a series, not a slot. Connected to the schedule, the agent can book multiple visits in one call at the frequency the clinic specifies—say, twice a week for six weeks with a preferred therapist—read the dates back, and record conflicts for staff to resolve. When a patient calls to move one visit, it reschedules that visit without touching the rest.

Plan-of-care adherence reminders and missed-visit rebooking

Outbound campaigns can call ahead of scheduled visits to confirm attendance and capture a reschedule on the spot instead of inheriting a no-show. When a visit is missed, a clinic-scripted outbound call can reach the patient promptly, offer open times, and rebook—so one missed Tuesday does not quietly become a lapsed plan of care. Voicemail detection can leave a configured message or follow the campaign's retry policy. The agent encourages attendance only in the clinic's approved words and never discusses clinical consequences of missed care beyond that script.

Cancellation backfill from the waitlist

When a cancellation opens a slot, an outbound campaign can work the clinic's waitlist in order: call, offer the specific time, book the first acceptance through the connected schedule, and stop. What took a stack of sticky notes and an hour of callbacks becomes a triggered sequence—and the schedule stays full.

Insurance and benefits questions—verify and route, never adjudicate

For general questions the clinic has approved—which plans the practice accepts, whether a referral is typically needed for a given plan, what to bring to the first visit—the agent answers from the knowledge base. For patient-specific eligibility, visit limits, authorization status, or balances, it collects details and routes the call or files a structured request for the billing team. It never tells a caller what their plan covers or promises authorization.

Workers'-comp and auto-claim intake

Injury cases arrive with extra fields, and the clinic decides what they are. The script can collect claim number, carrier, adjuster name and contact, employer and date of injury for workers'-comp, or the auto-insurance claim and attorney details the clinic requires—delivered as a structured record so staff start verification with a complete file. The agent gathers and routes; coverage decisions stay with humans.

Home-exercise-program questions routed to clinicians

Patients call about their home program: is this soreness normal, should I keep going, can I add weight. The agent takes these calls seriously by not answering them. It collects the patient's identifiers, the question in their own words, and callback details, tells the caller a clinician will respond, and routes the message—or transfers immediately if the clinic's escalation rules say so. It never gives exercise or clinical advice, full stop.

Intake-form completion reminders

Evaluations run long when paperwork is not done. Outbound reminder calls can reach patients before the first visit, confirm they received the intake forms, repeat the clinic's approved completion instructions, and flag anyone who needs the link re-sent or wants to arrive early to complete forms on paper.

Multi-location routing

A multi-clinic practice can run one agent across locations: identify which clinic the caller wants by the number dialed or by asking, apply that location's hours, providers, and scripts, and book into that location's schedule. Callers who dialed the wrong location get moved, not bounced.

After-hours capture

Evenings and Saturday mornings are when working patients call. After hours the agent answers instead of voicemail: books permitted slots, takes structured messages, and handles cancellations so the morning team can start backfilling. For anything urgent it follows the clinic's script—approved guidance to seek emergency care and, where configured, a transfer to an on-call line. It does not assess urgency; it matches the clinic's written triggers.

Multilingual patient communication

ThunderPhone supports 47 voice languages. A clinic can set a primary language plus additional languages, and the agent switches mid-call when a caller changes to a configured language—coverage the front desk cannot staff on every shift.

Sample therapy-clinic call flow

Agent: Thank you for calling Riverbend Physical Therapy. This is the clinic's automated assistant. Are you calling to schedule, change an appointment, or something else?

Caller: My doctor told me to set up PT for my shoulder. I have a referral somewhere.

Agent: I can get your evaluation scheduled. May I have your full name and date of birth?

Caller: Dana Whitfield, June 3, 1985.

Agent: Thank you. Which of our two locations is easier for you—Riverbend Main on Fifth Street, or the Northgate clinic?

Caller: Northgate.

Agent: For a first evaluation at Northgate I have Thursday at 8:15 a.m. or Friday at 4:30 p.m. Which works better?

Caller: Friday afternoon.

Agent: Done—Friday at 4:30 p.m. at Northgate. You mentioned a referral: which provider referred you, and do you have the referral paperwork with you or will the office be sending it?

Caller: Dr. Iyer. I think her office faxed something over.

Agent: I've noted a referral from Dr. Iyer, expected by fax—our team will confirm it arrived before Friday. You'll also receive intake forms; completing them before your visit keeps your full time with the therapist. Is the number ending in 2276 the best callback number?

Caller: Yes. Also, is this covered by my insurance?

Agent: I can't verify your specific benefits on this call, but I've recorded your question and our billing team will call you back before your visit. You're set for Friday at 4:30 p.m. at Northgate.

Had the caller asked whether an exercise was safe to continue, the agent would have taken the question verbatim and routed it to a clinician rather than answering it.

Platform capabilities behind the therapy workflows

GDPR and HIPAA compliance posture — and the clinic's configuration responsibility

ThunderPhone's public compliance posture is GDPR and HIPAA compliant. That posture does not make any particular clinic workflow compliant by itself, and in a healthcare setting this responsibility deserves the most attention on this page. The clinic decides and configures: which patient information the agent may collect and which it must not; whether calls are recorded and what notice callers receive; how long transcripts and recordings are retained; which integrations receive protected health information and under what agreements; what the agent's disclosure script says; and who can access call data. Injury-claim intake adds sensitivities of its own—claim numbers, employers, attorneys—so limit each workflow to the minimum information it needs, and have your compliance owner review the prompt, recording settings, and data destinations before launch.

Inbound and outbound calling on your numbers

Agents handle inbound calls and place outbound campaigns. Clinics can bring existing numbers through supported direct VoIP connections or manual SIP configuration for any SIP trunk; verified imported numbers support inbound and outbound calling, so patients keep dialing the number they already know.

Warm and cold transfer

Cold transfers route a caller immediately. On eligible production numbers that can place an outbound SIP leg, warm transfers let the agent put the caller on hold, privately brief the therapist or billing specialist, and connect only after the recipient accepts—so a patient with a clinical question is handed off with context, not dropped into a queue.

Hold, keypad menus, and voicemail handling

The agent can navigate hold queues and keypad phone menus on outbound calls—useful when confirming a referral with a physician's office. Voicemail detection can let the prompt decide, hang up, or leave a configured message, with campaign retries governing the rest.

Knowledge grounded in clinic documents

Attach clinic policies, accepted-plan lists, location details, and cancellation policies—text files up to 5 MB, PDF or DOCX up to 50 MB—or import pages by URL. The agent searches these approved sources mid-call instead of improvising, and can be instructed to route any question they do not cover.

Integrations that fit the clinic's stack

Connected apps, HTTP APIs, and remote MCP servers let the agent act during a call—check a schedule, book a visit series, file a benefits-verification request, log a waitlist outcome. HMAC-signed webhooks deliver call events to clinic systems with verifiable integrity, and a web widget can put the same agent on the clinic's website.

Testing before a patient ever hears it

Rehearse the risky calls. Run AI-caller simulations—a patient pressing for exercise advice, a workers'-comp caller with a half-remembered claim number, a frustrated patient cancelling a whole series—with graded scenarios. Build the passing cases into regression suites so a prompt edit cannot silently weaken the no-clinical-advice rule, and use A/B experiments to compare wording on live traffic. Recordings, transcripts, and grading make every production call reviewable.

What would this cost each month?

Suppose a clinic handles 1,100 AI-assisted calls per month, averaging 3 minutes each:

1,100 calls × 3 minutes = 3,300 minutes per month

Spark: 3,300 × $0.02 = $66/month
Bolt: 3,300 × $0.05 = $165/month
Storm: 3,300 × $0.09 = $297/month

That is base engine usage, not a quote. Premium voice or language paths can add up to 3¢ per minute, and phone-number or carrier charges depend on the telephony setup. Hold time bills a flat 2¢ per minute; voicemail and phone-menu minutes bill at the engine rate. Optional add-ons such as verbal acknowledgements, call supervision, and long prompts carry their own published surcharges. The agent builder shows the current all-in rate before calls are placed.

Guardrails a therapy clinic should write into the agent

Each rule belongs in the prompt explicitly, with a simulation that proves it holds:

No exercise or clinical advice, ever. Questions about home programs, pain, soreness, technique, or progression are collected verbatim and routed to a clinician. The agent never reassures, never modifies, never demonstrates.
No symptom assessment. Urgency handling is a lookup against the clinic's written trigger list—new numbness, a fall, post-surgical concerns, whatever the clinic specifies—followed by the clinic's exact configured response.
No coverage adjudication. Benefits, visit limits, authorizations, and workers'-comp coverage produce structured requests for the billing team. The agent says so plainly and never predicts an outcome.
Referral rules stay with the clinic. The agent collects referral and prescription details per script; it never tells a caller they do or do not legally need one.
Minimum necessary information. Collect only the fields each workflow requires; a reschedule call does not need an injury history.
Disclosure and recording notices. The agent identifies itself as an automated assistant and delivers whatever recording or privacy notice the clinic's compliance owner requires.
Escalation is always available. Any caller who asks for a person gets a transfer path or a callback message—the agent never becomes a wall between a patient and their clinic.

Frequently asked questions

Is ThunderPhone HIPAA compliant for a physical therapy clinic?

ThunderPhone's public posture is GDPR and HIPAA compliant. The clinic remains responsible for configuring its own compliant workflow: what patient information the agent collects, recording and notice settings, retention, which integrations receive protected health information, and who can access call data. Review the configuration with your compliance owner before launch.

Can the agent answer questions about my home exercise program?

No, and it should not be configured to try. It collects the question in the patient's own words with callback details and routes it to the clinical team, or transfers per the clinic's escalation rules. Exercise and clinical guidance come only from licensed clinicians.

Can it book an entire plan-of-care visit series?

Yes, when connected to a calendar or practice-system API that permits it. The agent can book recurring visits at the frequency the clinic specifies, read the dates back, reschedule a single visit without disturbing the series, and record conflicts for staff.

Does it handle referrals and prescriptions for new patients?

It collects what the clinic's script requires—referring provider, paperwork status, how documentation will arrive—and flags bookings pending documentation. Because referral requirements vary by state and payer, the agent never rules on whether one is needed; that question routes to staff.

Can it verify insurance benefits or workers'-comp coverage?

It collects the fields the clinic specifies—plan details, claim number, carrier, adjuster—and files a structured request for the billing team. It does not verify eligibility, quote coverage, or promise authorization on the call.

How does cancellation backfill work?

When a slot opens, an outbound campaign calls the clinic's waitlist in order, offers the specific time, books the first acceptance through the connected schedule, and stops. Voicemail outcomes follow the campaign's retry policy.

Can one agent cover multiple clinic locations?

Yes. The agent can identify the intended location by the number dialed or by asking, then apply that location's hours, providers, and scripts, and book into that location's schedule.

Can it speak with patients in languages other than English?

Yes. Configure a primary language and additional languages from the 47 supported, and the agent can switch mid-call when a caller changes language, provided the selected voice supports the configured set.