The paperwork queue that never clears
Every practice has a version of the same backlog. A referral goes out and nobody circles back to confirm the receiving office actually has it. A prior authorization sits in a queue because assembling the documentation takes a block of uninterrupted time nobody has. A records request comes in on Monday and is still open on Friday. A claim gets denied for a reason that turns out to be a missing modifier, but it takes a coordinator ten minutes just to find that out. A patient who no-showed a recall visit six weeks ago has quietly fallen off everyone's list. A cancellation opens a slot that sits empty because working down the waitlist by hand takes longer than the slot is worth.
None of these tasks require clinical judgment. They require someone to check status, fill in a form correctly, follow up on schedule, and know when to stop and ask a person. That is exactly the shape of work a custom AI agent can hold — and it is a different problem from the one a receptionist answering the phone is solving, which is why this is a distinct system built for the back-office side of the practice rather than the front line. It sits alongside the other systems Calfy builds for healthcare practices, scoped specifically to the administrative chasing that has nothing to do with a phone ringing.
What the agent does, day to day
A single agent, scoped to your practice's actual workflows, typically covers a combination of the following. It does not diagnose anything, does not judge clinical severity, and does not decide what a payer will or won't cover — it gathers the information a decision requires, prepares it, chases the people who are sitting on it, and puts a finished packet in front of a human for the call that is actually theirs to make.
- Referral intake and tracking. New referrals are logged, matched to the right provider and payer, and tracked until the receiving office confirms receipt — not just sent and forgotten.
- Prior authorization chasing. Requests are submitted with the documentation a payer requires, then followed up on a set cadence until there's a decision, not left to sit in a portal queue.
- Patient records requests. Incoming requests are logged, the requestor's authorization is checked against what's on file, and the scoped record set is assembled for a human to release.
- Insurance eligibility verification. Coverage is checked against the payer before the visit, not discovered at the front desk when the patient is already standing there.
- Claim denial triage and resubmission prep. Denial reason codes are read, sorted into a clean paperwork fix versus a case that needs a person's judgment, and the fix is drafted either way.
- Recall and no-show follow-up. Patients overdue for a recall, or who missed a visit, get a personalized outreach message and a tracked follow-up sequence instead of falling off the list.
- Waitlist backfill. When a slot opens from a cancellation, the waitlist is worked in order automatically instead of by whoever has a free minute to start dialing down a list.
Walkthrough: a referral from intake to confirmed visit
A referral arrives by fax, portal upload, or a forwarded email from the sending provider's office. The agent reads it, extracts the patient, the ordering provider, the payer, and the reason for referral, and creates the record in your practice management system rather than leaving it as a loose document in an inbox. It checks the referral against what the receiving specialty typically requires — imaging, prior notes, a specific form — and flags anything missing before it becomes a problem three days later.
It then sends a confirmation request to the receiving office through their portal or a standardized fax, and logs the referral as pending. On a set cadence — say, every two business days until confirmed — it checks for a response and follows up again if none arrives. Once the receiving office confirms, it notifies your scheduling coordinator (and the patient, if your workflow allows direct outreach) that the referral is ready to be booked. If nobody confirms after a defined number of attempts, it stops following the script and escalates to a coordinator with the full timeline attached, so the next call starts with context instead of a blank screen.
Walkthrough: chasing a prior authorization to a decision
An order that requires prior authorization enters the queue. The agent checks the payer's specific requirements for that procedure and pulls the supporting documentation from the chart — it retrieves what the payer's rules specify, it does not interpret whether the case meets medical necessity. It assembles the request in the payer's required format and submits it through their portal or fax line, logging a confirmation or reference number the moment it goes out.
From there it polls status on the interval that payer typically takes to respond, rather than waiting for someone to remember to check. If the payer comes back asking for additional documentation, the agent flags exactly what's missing to the coordinator instead of leaving a vague "action needed" note. Once a decision comes back — approved or denied — it updates the patient's account, notifies scheduling and billing, and, if denied, hands the case straight into the denial-triage workflow rather than letting it sit as a dead end.
Walkthrough: filling a cancelled slot from the waitlist
A patient cancels an appointment. The agent checks the waitlist for that provider and appointment type, ordered by however your practice prioritizes it — wait time, urgency flag from the referring note, or a first-come order — and sends an offer to the first eligible patient with a short response window. If that patient doesn't respond in time, it moves to the next one automatically. Once someone accepts, it books the slot, updates the calendar, and closes the offer to everyone else on the list so nobody shows up for a slot that's already gone. If nobody on the waitlist responds, it flags the open slot to your team rather than leaving it silently empty. The same connection that lets the agent read your calendar and book a confirmed slot is what makes automating appointment scheduling work end to end, rather than stopping at "here's who to call."
The same pattern runs for recall and no-show follow-up: a patient overdue for a visit, or who missed one, gets a message offering to rebook. If there's no response after a couple of attempts, the agent hands the follow-up to your team's callback queue — or, for practices that also run voice AI for healthcare, into that system's outbound calling list. The agent decides who needs a callback and why; it doesn't make the call itself.
Not a phone system
It's worth being direct about what this page doesn't cover. Voice AI for healthcare answers and makes calls — booking, rescheduling, after-hours coverage, the conversations that happen over the phone. This system does the opposite kind of work: it operates across your practice management system, your EHR, payer portals, fax, and email, chasing status and preparing paperwork without ever picking up a phone. Most practices end up running both, because the two solve different halves of the same operational load, but they're built and scoped as separate systems. If your bottleneck is genuinely simpler — reminders that just need to fire on schedule rather than a process that needs to be tracked and chased — workflow automation is often the lighter, cheaper fix, and we'll tell you when that's the better starting point. For the underlying mechanics of what makes this an agent rather than a script, see the AI agent glossary entry.
Where it connects into your systems
Practice management and EHR. Most platforms expose an API or a scheduled data feed, which is usually enough to read and write referral, scheduling, and billing records without disrupting your system of record. Where a platform is older or closed, there's typically still a workable path in — a database connection, an export job, or a portal the agent can operate the way a person would.
Payer portals and clearinghouses. Eligibility checks, prior authorization submissions, and claim status lookups run against whichever portals or clearinghouse connections your practice already uses. The agent works inside the access you grant it; it doesn't need — or get — anything broader.
Fax and email. A surprising amount of healthcare administration still runs on fax and email, and the agent is built to operate in that reality rather than assume everything has an API.
Data handling. Every agent gets the narrowest access that lets it do its job — read-only where reading is enough, scoped credentials rather than a shared login, and detailed audit logging so "who touched this record and why" has an answer months later. Data minimization means the agent holds only what the task in front of it requires. Where your setup needs a business associate agreement in place, we put one in place. None of that is a certification Calfy holds on your behalf — compliance is owned by your practice as the covered entity, and what we build is the access control, logging, and minimization that support you in meeting it.
Escalation. Every workflow has a defined edge — an authorization denial that needs a clinical appeal, a records request with an authorization that doesn't check out, a claim dispute that isn't a clean paperwork fix. When the agent hits that edge, it stops and hands the case to a person with the full trail attached, rather than guessing at what happens next.