A referred patient who cannot get through calls the next practice on the list. This is the call where leakage starts or stops.
Caller My doctor referred me to you for my back. Dr. Amara Okoye's office said they were sending it over.
ClinicFlow Let me find it. Can I have your name and date of birth?
Caller Tom Herrera, 6/12/1969.
ClinicFlow Thank you. The referral from Dr. Okoye's office arrived this morning, for evaluation of lumbar radiculopathy.
Caller Good. How soon can I be seen?
ClinicFlow Our spine team has Tuesday at 8:45 AM or Wednesday at 3:30 PM. Before I book, one thing: the referral mentions an MRI from March, but the images didn't come with it. Do you know where it was done?
Caller St. Anne's.
ClinicFlow That's what I needed. I'm sending a records request to St. Anne's now, so the study is in your chart rather than the surgeon seeing it for the first time in the room.
Caller Tuesday morning, then.
ClinicFlow Booked, Tuesday at 8:45 AM with the spine team. Bring your insurance card, and if St. Anne's hasn't sent the MRI by Monday, bring the disc or the written report if you have either.
Caller Do I need to do anything before Tuesday?
ClinicFlow Only the intake forms, which come by text tonight. Filling them in beforehand means the visit starts with the examination instead of paperwork, and it gives the surgeon your symptom history before he walks in.
Caller Will Dr. Okoye know I'm scheduled?
ClinicFlow Yes. We confirm receipt and the appointment date back to her office, so nobody is left wondering whether the referral landed. Your chart now has the referral, the appointment, and the pending records request from St. Anne's.
The caller is matched to the referral already in your system, or the referral details are captured if it has not arrived yet.
The referral reason routes the patient to the correct sub-specialty using your rules.
Confirmation flows back to the referring practice, which is how referral relationships compound.
Referral source, reason, and scheduling outcome are structured data in your EMR, not a sticky note.
| Scenario | Destination |
|---|---|
| Referral on file | Booked immediately with the matched team |
| Referral mentioned but not yet received | Details captured, staff flagged to chase the fax |
| Urgent referral reasons | Escalated per your clinical criteria |
Referral leakage is mostly a phone problem: the referring office faxes, the patient calls, nobody answers, the patient calls the next name on the list. Answering every referral call and scheduling on the spot is the single highest-leverage fix. Our roadmap goes further: when the referral fax arrives, ClinicFlow will call the patient proactively and book them before they ever have to dial.
The AI captures the referring provider, reason, and patient details, books the visit when your rules allow it, and flags staff to obtain the referral documentation.
Scheduling confirmation flows back to the referring practice. Closing that loop is what keeps referrers referring.
Outbound referral scheduling, where ClinicFlow calls the patient as soon as the fax arrives, is in active development as part of our referral feature rollout.
A first-time caller with an injury is the most valuable call your practice gets. Here is how it becomes a booked visit in one conversation.
See this call type →The call that determines whether Thursday's visit generates revenue or a denial. Handled while the patient is still on the line.
See this call type →Patients call wanting their MRI results. The AI tells them everything about status, and nothing about findings. That line is the design.
See this call type →The demo line is the production agent. Call it, describe this exact scenario, and judge for yourself.
