Outpatient PT is judgment work buried under portal work. Patients pay you to move joints — not to spend Monday morning toggling between eight payer sites because someone forgot to confirm the 10:30 eval slot.
Prior auth is not patient care — but it owns Monday morning
Ten hours. Every week. Gone.
A five-therapist outpatient clinic in Austin tracked one month: 3.6 hours confirming prior authorizations across Aetna, UnitedHealthcare, and Texas Medicaid portals, 2.8 hours renaming physician referral PDFs from fax queues (REF_scan3.pdf, DrMartinez_urgent.jpg), 2.2 hours building plan-of-care expiration lists from exports the coordinator stopped updating in March, 1.4 hours chasing no-show follow-ups from yesterday's eval board. Zero treatment time. Zero progression decisions. Just production work patients never see on the benefit estimate.
Most clinics under eight therapists know the fix is "hire another patient care coordinator." The math rarely works. A part-time coordinator at $22/hour for ten hours is $880/month plus benefits, PTO, and the Wednesday someone calls in sick during auth week. You are not short on therapists. You are short on a production layer that runs before anyone opens WebPT.
That layer is what an isolated cloud computer is built for — persistent folders per patient, a real browser that logs into payer portals through a residential VPN, and duties that fire whether you are treating a shoulder or driving between clinics.
Three duties that replace coordinator prep work
Start with prior auth. Not treatment planning.
These three patterns cover most of the ten-hour block for clinics under eight therapists. Each maps to a specialist on CloudAxis with scheduled duties — not a chat thread you re-paste instructions into every Monday.
- Prior authorization sweep (weekdays 6:38am). A Browser specialist logs into your payer portals through a residential VPN, pulls authorization status and visit counts remaining for patients scheduled in the next 48 hours, and writes rows to
~/files/auth/prior-auth-queue.csv. Active auths with visits left land in a "cleared" tab. Expired plans, missing referral numbers, and visit caps already hit get flagged in a WhatsApp summary at 6:51am — not a blast to the whole team. Same-day evals with "STAT" in the notes get their own row. - Referral intake filing (Tuesdays, Thursdays, Fridays 6:55am). A Browser specialist downloads referral packets from your fax portal and physician EMR export queue, renames to
{lastname}-{firstname}-referral-{YYYY-MM-DD}.pdf, and drops them in~/files/patients/{lastname-firstname}/referrals/inbox/. Illegible scans and unsigned orders land in a CSV grid you can fix inline in the Files app — ninety seconds on your phone between patients, same path the agent reads on the next run. - Plan-of-care expiration staging (Mondays and Wednesdays 7:00am). A Research specialist reads your WebPT POC export, cross-checks last progress note dates, and builds a renewal call list at
~/files/clinical/poc-renewals-this-week.csvsorted by days until expiration and visit value. Patients who already booked a re-eval in the last 72 hours get moved to an "already scheduled" tab so your coordinator stops calling people who already said yes.
A four-therapist clinic in Raleigh set this up on a Saturday. First Monday the Browser duty pulled the wrong auth year for one patient because United listed two active policies under the same member ID — twelve minutes to fix in the visible browser. By week three the prior auth queue filled before 7:00am and the lead coordinator stopped rebuilding her personal "who still needs auth" sticky note entirely.
Tell Cloudia the outcome in plain English: "Every weekday at 6:38am, check prior auth for everyone on tomorrow's schedule, update the CSV, WhatsApp me only expired auths and visit-cap hits." She builds the specialist, wires browser skills, and schedules the duty. Watch the first payer portal run in the Browser app — non-negotiable for anything involving clinic credentials.
Do not wire agents straight into live chart notes on pass one. Stage everything in
~/files/patients/ and ~/files/auth/ until naming conventions and auth flags are boringly consistent. Clinics that skip staging push wrong visit counts into WebPT and spend more time on denied-claim callbacks than they saved. Mark only payer portal and EMR login URLs as require VPN in settings — VPN minutes are capped per plan. Leave your public website intake form on standard routing.
The math — part-time coordinator vs agent stack
$880 versus $39. Different schedule board. Same eval slots.
Austin clinic before picture:
- Labour. 10 hours/week × $22/hour effective coordinator cost = $880/month. Add ~2 hours clinic manager review of auth gaps at $30/hour = $240. Total admin layer: $1,120/month.
- Opportunity cost. Those ten hours came out of weeks already at capacity — two new eval slots per month delayed because "Monday auth" ate the morning huddle.
After three duties on CloudAxis Pro ($39/month):
- Labour. 1.5 hours/week coordinator review of flagged rows and POC exceptions. About $132/month at $22/hour — but that hour is actual patient-facing triage, not portal clicking.
- Platform. $39/month. Browser minutes for payer portals stay inside hard caps — no surprise API bill. Overnight scheduling mechanics in how to make AI agents work overnight.
- Net. $772/month back in labour, 8.5 hours returned, $39 software. One eval that proceeds because auth was confirmed at 6:51am covers the platform for the year.
| Line item | Part-time coordinator | CloudAxis agent stack |
|---|---|---|
| Monthly labor | $880 (10 hrs × $22) | $0 (duties run unattended) |
| Manager review | $240 (8 hrs × $30) | $132 (6 hrs × $22) |
| Platform cost | EMR seats only | $19–$39/month (Growth or Pro) |
| Before-huddle auth status | Done manually by 8:30 or skipped | Auth duty runs 6:38am seven days |
| What you still pay humans for | Eval, treatment, progression | Eval, treatment, progression |
This is not "replace your front desk." It is replace the portal treadmill so the people you have greet patients instead of toggling tabs. For broader document skills — CSV grids, DOCX templates, PDF intake — see AI document processing in the agent OS.
What still needs a licensed PT — and why that is the point
Agents do not treat. They stage.
A patient whose shoulder exam shows something the auth row cannot see still needs a therapist who reads the movement screen. A plan of care where visits are exhausted but function is still impaired still needs a human who explains options at the eval table. Clinical judgment, informed consent, and the conversation that survives a denied claim — none of that belongs in a duty. The mistake clinics make is trying to automate the care layer because the auth layer feels embarrassing to still do manually in 2026.
Here is the reframe most owners miss: you are not buying a robot therapist. You are buying back the Monday huddle where your team talks about cases instead of which portal still shows "pending." The Austin coordinator still rooms every eval. She still calls the two POC renewal rows the agent flagged as high-value and expiring. What changed is she walks into the clinic with nine auths already cleared — while the practice down the street is still logging into Aetna at 8:35.
Monday 6:43am again. Same five-therapist clinic. The phone buzzes at 6:51. She reads the WhatsApp summary in the break room, taps into the Files app, fixes one referral number on a flagged row, clears three patients for the 10:30 block. The first eval starts at 8:00. Auth was confirmed forty-one minutes before the huddle. She did not open her laptop until the front desk.
The prior auth queue is not the relationship. It is the head start your competitor does not have.
FAQs — physical therapy clinic automation
Can AI agents run physical therapy clinic operations automatically?
Not clinical care you would stake your license on. Agents excel at prior authorization sweeps, referral intake filing, plan-of-care expiration staging, and payer portal monitoring. Evaluations, treatment progression, manual therapy decisions, and signed clinical notes stay with your licensed team. Think production line before the therapist rooms the patient.
How long does setup take for a clinic under eight therapists?
Most four-to-six-therapist clinics budget one Saturday for the prior auth duty and one week of morning test runs before a full schedule depends on it. Cloudia builds the first specialist in under twenty minutes if you have payer portal access and a patient folder naming template ready. Budget another hour to pin STAT keywords and your WebPT export format. Match the under-one-hour first agent guide for duty scheduling mechanics.
Will payer portals block an AI agent logging in from a datacenter IP?
Payer and EMR sites often serve different session behavior for datacenter IPs than for someone browsing from your market. CloudAxis routes marked domains through a residential VPN from your country — the same view someone working from Austin or Raleigh would see. Run the first week in the visible browser so you catch two-factor and CAPTCHA issues before they hit a Monday schedule. Put work on autopilot at app.cloudaxis.ai — free tier to test, Growth at $19/month for daily duties.
AI document processing automation · How to make AI agents work overnight · AI agents for dental practices — portal staging pattern