WebPT integration
The best AI receptionist for WebPT.
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.
The difference
A lot of voice AI sits next to WebPT. 2care writes into it.
A plan of care that stops at visit four was not a scheduling failure. It was a follow-up failure.
Sits beside it
2care writes into WebPT
Availability
Reads a synced copy that can be minutes or hours stale
Reads live availability before it offers a single slot
Booking
Sends your team a request to key in by hand
Writes the appointment directly, in real time
New patient intake
Drops a free-text note or a call recording
Writes demographics and insurance as structured fields
Follow-up work
Lands in a second inbox nobody owns
Lands in the queue your team already works
Every morning
Somebody reconciles yesterday against the schedule
Nothing to reconcile
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.
Questions
2care and 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.
2care is built to work inside WebPT rather than beside it. It answers every inbound call, reads live availability from WebPT before offering a slot, and writes the booking back in real time - so there is nothing for your front desk to rekey afterwards.
Through WebPT's official API. Your onboarding specialist sets up the connection during go-live - there is nothing to install and no change to how your team works in WebPT.
No. 2care reads live availability before offering a slot and applies your booking rules, so it cannot create a conflict. Every write is logged and reversible.
It matches on the details WebPT already holds before it creates anything. A returning patient is picked up from the existing record, so you do not end up with a second chart for the same person.
Yes. Providers, locations, appointment types and booking rules are mapped during setup, so the agent offers the right slot with the right clinician at the right site.
No. It takes the high-volume routine calls - booking, rescheduling, hours, insurance, refill requests - and routes anything clinical or complex to a human with the context already attached.
Most practices go live in weeks, not quarters: authorise the connection, map your rules, test your real scenarios, then switch the line over with monitoring in place.
Yes - HIPAA-ready with a BAA available, GDPR compliant with a DPA, and DPDP compliant. Everything is encrypted in transit and at rest, and fully audit-logged. Patient data is not used to train shared models.
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