Integrations
The plan of care that stopped at visit four
It was not a scheduling failure. Plans stall for administrative reasons - an authorisation lapsed, a visit was never booked.
A plan of care that stops at visit four was not a scheduling failure. It was a follow-up failure, and it usually happened for an administrative reason rather than a clinical one.
The unit of work in rehab therapy is the plan, and the plan has an authorisation behind it. Both leak. Visits get booked one at a time, so attendance drifts and the course ends before the outcome does. Authorisations expire while care is still needed, which stops treatment for a reason that has nothing to do with the patient's progress and takes weeks to reverse. Underneath both, therapist utilisation is the business, and a cancelled hour is simply gone.
Answering is the easy half. What decides whether a front desk gets its hours back is where the work lands afterwards, and that is the part most tools skip. A booking request emailed to your team is not an integration; it is a second queue with better marketing. the platform answers the call, resolves what it can, and writes the result into WebPT while the caller is still on the line - the appointment against live availability, the intake as structured fields, the follow-up as a task in the queue your team already works. Nothing waits for a nightly sync and nothing needs rekeying in the morning. The WebPT integration page shows exactly what moves in each direction.
The whole plan goes into the diary at once, at the prescribed frequency and at times the patient will realistically keep - which is the single biggest driver of completion. Patients approaching their authorised visit count are flagged and contacted so renewal is submitted before visits stop. Cancelled hours are offered to the waitlist the same day, and patients who drift are called back and told exactly how many visits remain, which is usually the thing that brings them back.
How it connects
Real time
Written while the patient is still on the line. Every write logged and reversible.
Where it stops
It does not triage, and that boundary is deliberate rather than a limitation. The moment a call stops being administrative - a red-flag description, an urgent caller, a question that needs clinical judgement - it is escalated to a person, in seconds, with the transcript already attached so nobody starts cold. The agent will not guess, and it will not advise. For a practice being asked to put an AI in front of its patients, that refusal is usually the thing that makes the rest acceptable, and it is why the compliance posture behind it - HIPAA, GDPR and DPDP, encrypted in transit and at rest, every write logged and reversible - matters as much as the booking logic.
Seeing it rather than reading about it
Physical therapy covers the workflow in more depth, and other practices describe what changed once it was running. But the fastest way to judge a voice agent is to be on the other end of one. The demo will call your phone in under a minute, running whichever scenario you pick, or you can book fifteen minutes and we will point it at your own call flows and let you try to break it.
