What automated referral intake looks like at a vet clinic

What referral intake costs before you touch it

A specialty or emergency practice takes referrals in whatever format the primary vet's office prefers that day: a fax, a PDF attached to an email, sometimes a phone call read out to whoever picks up. Someone on staff has to read it, open ezyVet, Cornerstone, AVImark or Instinct, and create or match the patient record by hand. If the referring vet forgot to attach bloodwork or imaging, someone has to spot the gap and call to ask for it, then call again in a few days if nothing shows up.

None of this is difficult work, but it is constant, and it competes with the same front desk staff who are also answering the phone and checking in walk-ins. Digitail's blog cites an estimate from Dr. Michelle Woodruff of Woodruff Vet Services that manual intake runs 5 to 10 minutes per appointment, just for gathering information a proper referral form should already carry. Records requests run the same way in reverse: once the visit happens, a specialist has to compile discharge instructions and get them back to the primary vet, often through the same fax or email that started the case. Across a full day of referral appointments, that is a real share of a receptionist's shift.

How the workflow actually runs, referral to discharge

Here is what the automated version looks like end to end. A referral arrives by fax, email or a web form. The system reads it, pulls out the patient name, owner contact and referring vet, and checks whether that patient already has a record in your PIMS. If so, it attaches the referral there; if not, it creates one, tagged with the referring clinic. It then sends a specific request back to the primary vet's office for whatever is missing, bloodwork or imaging, rather than a generic please-send-records message.

This is where a simple automation and an agentic one diverge. A basic automation sends one reminder and stops. An agentic workflow checks back: if the referring practice stays quiet for two or three days, it sends a second request, and if that goes unanswered too, it flags the case for a staff member instead of letting it age silently in an inbox. The estimate approval runs on the same pattern. Once the specialist's exam estimate is ready, the system sends it to the owner through whatever channel the practice already uses for client messages, often Instinct, and follows up before anyone has to pick up the phone. We go into the distinction itself in how workflow automation differs from agentic AI, because the checking-back part is what actually removes the phone calls.

We build this watch-and-escalate pattern as scheduled jobs wired straight into the software a practice already runs, not a separate portal staff have to log into. Across our own operations we run 197 scheduled jobs across 78 live integrations, so a referral case like this one is a single instance of a pattern we run at scale, not a one-off script.

Where a person still has to decide

The system does not decide whether a case needs to be seen today or next week. It does not read an ultrasound, and it does not judge whether a referral is a true emergency. Those calls belong to a vet, and they should stay there. What the workflow does is make sure the records and the paperwork are sitting in the file before the appointment starts, instead of a vet or technician chasing a fax mid-shift.

The same limit holds for discharge instructions. The system can format the note, pull the relevant fields from the record, and send it to the referring vet the moment the patient is discharged, so the primary vet has it before the owner even calls to ask. It cannot write the clinical content of that note; a clinician does that. We cover this boundary, where an agent can act and where it has to stop, in where AI agents fail when they touch real systems.

The part that actually eats staff time

Ask front desk staff at a specialty practice what they chase most, and estimate approvals come up as often as records. An owner gets a number for a workup, does not respond, and someone calls, gets voicemail, and calls back the next day. It is the same shape of problem as chasing a signed document in any service business: the task itself takes two minutes, the follow-up takes days. The delay costs more than staff time: it leaves a slot open on the calendar when the case can't move to scheduling until the estimate is signed. We've written about the chasing pattern more generally in the real cost of chasing client documents every season.

If you want to see where this hits your own clinic, pick one referral that came in this week and time it: minutes between the fax or email landing and the exam being booked in your PIMS, and how many calls it took to get the estimate approved. That number, from your own week, is the one worth automating first.