AI Receptionist for WebPT Physical Therapy Clinics

Physical therapy has a constraint most of healthcare does not think about on the phone: the authorization. A patient arrives with a referral for a fixed number of visits, insurance has approved that many and no more, and every session booked has to fall inside that count or the clinic does the work for free. Book the eleventh visit against a ten-visit authorization and someone finds out at billing, weeks later, when the money is already gone. On a WebPT clinic, the front desk is not just filling a schedule; it is scheduling against a budget of visits that runs out, and that is the part a generic booking agent has no idea exists.

We build the WebPT connection, and this is about scheduling against that budget: booking within the authorized visits, and catching the recertification before the count runs dry.

The calendar is the easy half; the authorization is the half that costs money when it is wrong. 2care reads a patient's authorization from WebPT and schedules inside it, so a plan of care is booked up to the authorized count and no further, and the visits that would exceed it are flagged rather than quietly written.

The patient's authorization	What the agent does	Result in WebPT
A fresh referral, visits approved	Books the plan within the count	The plan scheduled, inside the auth
An authorization running low	Flags a recert before the visits end	The recert prompted, not missed
No authorization yet	Books the evaluation, notes auth pending	The eval scheduled, the gap flagged
An expired authorization	Routes to staff to renew it	Nothing booked against a dead auth
A cancellation mid-plan	Rebooks inside the plan window	The plan and the auth kept aligned

The value here is not that the agent books faster; it is that it books correctly against a rule that a busy front desk cannot hold in its head across dozens of patients. A schedule full of visits that are all inside their authorizations is worth far more than one that looks full and quietly contains unpaid work waiting to surface at billing.

The cost of getting it wrong is not evenly spread, which is what makes it dangerous. A single visit over an authorization is a small write-off; the same mistake repeated quietly across a busy caseload, a few visits over here, a lapsed auth there, adds up to a serious hole that only appears when the denials come back. Because the agent checks the count on every booking rather than relying on someone to remember, the error that compounds is the one it is best placed to prevent.

How a WebPT booking is made, and how fast

Underneath, one connection carries all of it. 2care reaches WebPT through its API, authorised with a scoped credential set during onboarding, with nothing new for the clinic to run. Availability is read live by therapist and visit type, so an offered slot genuinely exists, and the visit is written against the resolved patient and validated by WebPT's own rules, so a slot taken during a call fails cleanly rather than being assumed open.

Speed decides whether a referral call converts. The agent answers in roughly 480 milliseconds, with a ninety-fifth percentile under 700, on a voice stack we own outright rather than one assembled from third parties, so checking the authorization and reading the schedule live never stalls the call, which is still answered on the first ring in about 2 seconds. It stays up 99.9 per cent of the time, fields well over a thousand calls at once, and stamps every write with an idempotency key so a retry cannot double-book a slot. The turn detection holds for a finished sentence, so a caller reading out a referral and an authorization number is not interrupted partway.

Booking the plan within the authorized visits

A course of physical therapy is a plan, not a single visit, and the plan has to fit the authorization. Where WebPT supports it, 2care books the plan of care in one call at the therapist's cadence, up to the number of visits insurance has approved, so a patient leaves with the whole course scheduled and the clinic knows every session in it is covered. Booking only the evaluation and leaving the rest to a callback is how a plan of care falls apart and how visits that could have been authorized go unscheduled until the referral lapses.

Placing the whole plan at once, inside the auth, does something a piecemeal booking cannot: it makes the covered course visible to the patient as a commitment, which is a large part of why patients actually complete the therapy rather than dropping out after the pain eases. Completed plans are better outcomes and better economics at the same time, and both start with the plan being booked whole and within the authorization on the first call.

The recertification nobody tracks until it is late

The quiet failure in a PT clinic is the authorization that runs out mid-plan. A patient still needs care, the visits are used up, and the recertification that would have extended the authorization was not requested in time, so a session happens outside the auth and is not paid, or the patient's therapy stalls while paperwork catches up. It is nobody's job in particular, which is exactly why it slips.

2care watches the visit count against the authorization and flags a recertification before the visits run out, so the clinic requests it while there is still time rather than discovering the gap after a session has already been delivered. Turning the recert from a thing someone has to remember into a prompt raised from the data is a small change that closes one of the most common revenue leaks in outpatient PT.

It is also better for the patient. A therapy that stalls while a recert is chased is a patient losing momentum at exactly the point continuity matters most, and an interruption in care is not just a billing inconvenience, it can undo progress the plan was built to protect. Flagging the recert early keeps the care continuous, which is the outcome the plan existed for in the first place.

The record and the data agreement

The patient is pinned down before anything is scheduled. A returning patient is located on their WebPT chart and verified against a date of birth; when two charts are plausible, a person decides rather than the agent, following patient matching. Referral and authorization details go in as structured fields, not a free-text note, so the booking carries what billing will need, and the same capture powers patient intake across every channel a patient uses.

A booking that assembles a transcript, matches a patient and writes a visit and its authorization into WebPT is handling protected health information, not passing a call along. Under HHS guidance a vendor doing that is a business associate, not a conduit, so a signed agreement precedes the first live call, the data is encrypted at every step, no model is trained on it, and each write can be rolled back. The compliance page has the specifics and the frameworks that apply beyond the US.

What 2care changes for a WebPT clinic

A WebPT clinic is not short of a documentation and scheduling system; it is short of a phone that schedules against authorizations without a person tracking every count by hand. 2care answers every call, reads the authorization, books the plan within it, flags the recert in time, resolves the patient, and writes each result back, through one voice stack we own rather than a chain of services relaying a patient between them.

What a clinic feels is not a faster booking on the calls it already took. It is the visits that used to slip outside an authorization now caught before they are booked, the recerts requested in time rather than late, the plans of care booked whole and completed more often, and the referral calls that used to reach voicemail after hours now scheduled. Scheduling against the authorization is the particular discipline a PT front desk lives or dies by, and it is the one 2care is built to keep.

For a multi-therapist clinic the effect scales with the caseload. One front-desk person can hold a handful of patients' authorizations in mind; nobody can hold two hundred. Moving that tracking from a person's memory to a rule read on every call is what lets a clinic grow its caseload without growing its write-offs at the same rate, which is the version of scale a PT practice actually wants.

Where this is right for WebPT, and getting live

This is right for a clinic whose scheduling runs against insurance authorizations, that keeps its therapists, visit types and authorization data current in WebPT, and that has a clinician for the calls that turn clinical. Given those, the value shows from the first day the line is live, most clearly in the visits that stop being delivered outside an authorization.

Getting there is three moves over weeks. The connection is authorised to read availability and authorizations and to write visits through the WebPT API. The clinic's setup is mapped: therapists, visit types and durations, plan cadences, how authorizations and recerts are tracked, and the clinical route. Then the line is tested against a sandbox with the front desk listening before it is switched across, and the authorization handling is tuned over the first days against real calls, each change backed by the trigger every escalation records.

The first days confirm the one thing a PT clinic will want to see before it trusts the line: that a booking which would breach an authorization is caught and flagged rather than written. Watch a handful of those on the recordings, see the count respected every time, and the front desk stops double-checking each booking. Nothing about the number patients dial changes, and there is no hardware to install.

Frequently asked questions

Does it stop a booking that would exceed the authorization?

Yes. It reads the patient's authorized visit count from WebPT and books within it. A session that would go past the authorization is flagged and routed rather than quietly written, so the clinic is not left delivering unpaid care that surfaces at billing weeks later.

Can it flag a recertification in time?

Yes. It watches the visit count against the authorization and prompts a recert before the visits run out, so the paperwork is started while there is still time rather than after a session has already been delivered outside the auth.

Does it book the whole plan of care at once?

Yes, where WebPT supports it and within the authorized count. Each session is placed at the therapist's cadence with a reminder against it, which is what keeps a plan of care running to completion instead of thinning out after the evaluation.

Will it create duplicate charts in WebPT?

No. A returning patient is located on their existing chart first and verified on a date of birth, and where two charts are plausible a person decides rather than the agent, so a therapy history and its authorizations stay on one record.

Is patient data ever used to train models?

No. Nothing a patient shares becomes training data for any model in the pipeline. It is encrypted end to end, kept only as long as the record requires, and covered by the agreement that governs every WebPT call the agent takes.

Hear it schedule against an authorization

The call worth judging on a WebPT line is a new referral with a fixed visit authorization: the plan of care booked whole, every session inside the authorized count, and the recert already flagged for when the count runs low.

See how the same connection runs on other systems across integrations, or hear a plan of care scheduled against an authorization on a live line when you book a demo.