WebPT integration
An AI receptionist for WebPT that finishes plans of care.
Rehab therapy clinics losing plans to authorisation gaps and quiet drop-off, where the plan of care is the whole unit of revenue.
Writing to WebPT
Real time, on the call
Writing…
Encrypted in transit, audit-logged
Who runs WebPT
WebPT runs rehab therapy clinics where the plan of care, and the authorisation behind it, is the unit of work. Visits left unbooked and authorisations left to lapse are where the revenue goes.
The problem
What is actually breaking.
The things practices tell us cost them the most, in the order they raise them.
Plans stall halfway
Patients book one visit at a time, attendance drifts, and the course ends before the outcome does.
Authorisations expire before the visits do
Care stops for an administrative reason, and re-approval takes weeks.
Therapist hours go unfilled
Utilisation is the business, and a cancelled hour is gone.
Drop-off is invisible until it is permanent
By the time anyone notices, the patient has stopped coming.
How it connects
Real time
Written while the patient is still on the line. Every write logged and reversible.
How 2care solves it
One platform, not a point fix.
Inbound answering, outbound outreach, write-back and escalation are the same agent - which is why the whole problem moves rather than one part of it.
The whole plan of care booked at once
The full frequency goes into the diary in one call at times the patient will actually keep.
Authorisation limits flagged early
Patients approaching their visit count are surfaced and contacted so re-authorisation goes in before care stops.
Cancellations backfilled same-day
A freed hour is offered to the waitlist immediately.
Drop-off recovered
Patients who stop attending mid-plan are called back and told exactly how many visits remain.
Scope
What it touches in WebPT.
Three passes. The third is what separates scheduling access from clinical access.
- Practitioner diary
- Therapist availability in WebPT at the moment of the call.
- Appointment type
- Visit types, so an evaluation and a follow up differ correctly.
- Patient record
- Patient records, so a returning patient is recognised.
- Availability rules
- Authorised visit counts, where the clinic tracks them here.
- Location
- Locations across the practice.
The difference
What changes on the WebPT phone.
A plan of care that stops at visit four was not a scheduling failure. It was a follow-up failure.
How it runs today
With 2care on WebPT
Plans stall halfway
Patients book one visit at a time, attendance drifts, and the course ends before the outcome does
The full frequency goes into the diary in one call at times the patient will actually keep
Authorisations expire before the visits do
Care stops for an administrative reason, and re-approval takes weeks
Patients approaching their visit count are surfaced and contacted so re-authorisation goes in before care stops
Therapist hours go unfilled
Utilisation is the business, and a cancelled hour is gone
A freed hour is offered to the waitlist immediately
Drop-off is invisible until it is permanent
By the time anyone notices, the patient has stopped coming
Patients who stop attending mid-plan are called back and told exactly how many visits remain
Straight answers
What WebPT practices ask before connecting it.
Can it book an entire plan of care?
Yes. Booking the full course in one conversation is what keeps a WebPT schedule from thinning out halfway through, and it is the change clinics notice first.
Does it help with authorisation limits?
It surfaces them. Patients approaching their authorised count are flagged while there is still room to submit a re-authorisation. Your billing team still does the submission.
What happens when a patient cancels?
It offers to move the visit rather than just recording the cancellation, and the freed hour goes to somebody waiting.
We are not granting broad write access to WebPT.
Nor should you. Therapist availability and visit types, plus the authorised visit count where WebPT holds it. Clinical documentation sits outside the scope entirely.
At a glance
The WebPT connection, in the terms a review will ask about.
WebPT runs rehab therapy clinics where the plan of care, and the authorisation behind it, is the unit of work. Visits left unbooked and authorisations left to lapse are where the revenue goes.
Go live
Weeks, not quarters.
Most practices on WebPT are live inside a few weeks of authorising the connection.
Authorise the connection
Your WebPT administrator approves API access. Nothing is installed, and nothing changes about how your team uses WebPT.
Map your rules
We map your providers, locations, appointment types, booking rules and escalation paths - the things that make your schedule yours.
Test, then go live
We run your real scenarios against a test environment with your team watching, fix what surfaces, then switch the line over and monitor.
See it work
A call, a booking, and a write-back into WebPT.
Recorded end to end. The system on screen is not yours, but the flow is the one described above.
Before you connect it
Questions about WebPT.
Yes, as a block at the prescribed frequency and at times the patient chooses, the biggest single driver of plan completion.
Patients approaching their limit are flagged and contacted so re-authorisation is submitted before visits stop.
People search it both ways. A WebPT answering service describes covering the phone. A WebPT integration describes what connects to what. Here they are one product: cover for the line that reads your diary and writes the booking straight into it.
Therapist availability and visit types, plus the authorised visit count where WebPT holds it, confirmed while the caller is still speaking.
No. Callers are matched against what WebPT already holds before anything new is created.
Yes. Transcribed against the patient, so a cancelled or rescheduled visit has the reason attached.
See 2care book into WebPT.
30 minutes, on your own call flows. No commitment.
- 18 specialties covered
- ·Live in weeks, not months
- ·HIPAA, GDPR and DPDP