AI & Automation

Confirm Surgery Pre-Op Instructions: 7 Steps 2026

Jun 14, 2026

Pre-op confirmation is the process of making sure every surgical patient's owner has read, understood, and acknowledged the day-before instructions — withhold food after a set hour, water rules, medication timing, drop-off window, and the consent and deposit status — before the patient ever leaves home. Miss it and you discover at 7:30 a.m. that the dog ate breakfast, anesthesia is off the table, and a $1,400 surgical block just opened up with no one to fill it.

Most practices still confirm pre-op by hand: a technician works a call list the afternoon before, leaves voicemails, and crosses fingers. This guide walks through seven steps to automate that confirmation — so the right instructions reach the right owner at the right time, acknowledgments are tracked, and the surgery coordinator sees a clean go/no-go board instead of a stack of unreturned calls.

Key Takeaways

  • A fasting-protocol violation is the most preventable cause of same-day surgical cancellations, and it traces directly to a missed pre-op confirmation.

  • Automating the confirmation sends species- and procedure-specific instructions, then tracks who actually acknowledged them.

  • A two-way reply path matters: owners who can ask "can she have water?" and get an answer are far less likely to guess wrong.

  • The output the coordinator needs is a confirmed/unconfirmed board by surgery slot, not a pile of voicemails.

  • Start with your highest-cancellation procedures; the fasting-sensitive surgeries return the investment fastest.

Why Pre-Op Confirmation Breaks Down

The instructions are not complicated. The logistics are. A surgery day might hold 6 to 10 procedures, each with slightly different prep — a dental needs different fasting than an orthopedic, a feline differs from a canine, a diabetic patient needs special insulin timing. A technician confirming all of them by phone the afternoon before is fighting voicemail, work hours, and the simple fact that a verbal instruction is forgotten by morning.

Roughly 99.8 million U.S. households owned a pet in 2024 according to the APPA (2024), and surgical demand has scaled with it — but front-desk staffing has not, which is exactly why the manual confirmation list keeps slipping.

Who This Is For

Practice managers and surgery coordinators at general or specialty veterinary practices running 4 or more surgical procedures on a typical surgery day, with a PIMS like AVImark, Cornerstone, or ezyVet and a client-communication tool already in place.

Red flags — skip this if: you perform fewer than two surgeries a week where a personal call is genuinely warranted; your client contact data is stale and unverified; or you have no digital surgery schedule for an automation to read from.

The 7 Steps

Step 1: Trigger off the surgery schedule

The confirmation should fire automatically when a procedure is booked into the surgery slot in your PIMS — not from a manually built call list. The booking is the trigger; everything downstream keys off it.

Step 2: Branch instructions by species and procedure

Match the instruction set to the patient. A canine dental and a feline orthopedic get different fasting windows, water rules, and medication notes. Branching at this step is what makes the message correct rather than generic.

Step 3: Send at the right hour, on the right channel

Deliver the instructions the afternoon and evening before, on the channel the owner actually reads — SMS for most, email where preferred. Timing matters: too early and it is forgotten, too late and the owner has already fed the patient.

Step 4: Capture an explicit acknowledgment

Ask for a reply or a tap to confirm "instructions received and understood." A delivered message is not a confirmed one. The acknowledgment is what turns a hope into a tracked status.

Step 5: Open a two-way question path

Let the owner ask a clarifying question — "is one biscuit okay?" — and route it to a technician. Owners who can ask do not guess, and guessing is what cancels surgeries.

Step 6: Escalate the unconfirmed

Any owner who has not acknowledged by an evening cutoff gets flagged for a personal call. The automation handles the 80% who confirm on their own so staff focus the call list on the 20% who actually need it.

Step 7: Build the go/no-go board

Roll every surgery slot into a single confirmed/unconfirmed view the coordinator checks first thing. That board — not a voicemail pile — is the deliverable.

StepManual approachAutomated approach
TriggerBuild call list by handFires on PIMS booking
InstructionsRead from memoryBranched by species/procedure
DeliveryVoicemailSMS/email, tracked
AcknowledgmentHopeExplicit reply captured
EscalationCall everyoneCall only the unconfirmed

The Tools Compared

For a MOFU buyer weighing options, here is how the categories stack up for pre-op confirmation specifically.

Tool categoryPre-op fit (1–5)Two-way repliesProcedure branchesCost / mo
PIMS built-in reminders2Limited0–1$0
Vet communication app4Yes2–4$150–400
General SMS tool3Yes0 (manual)$50–150
Orchestration layer5Yes6+ rule-driven$100–300

Text-message confirmations see response rates several times higher than phone according to Gartner (2023) research on customer outreach — the channel shift alone closes much of the confirmation gap.

Where an Orchestration Layer Fits

A platform like US Tech Automations connects the surgery schedule in your PIMS to the messaging tool and back, so the confirmation runs as one workflow instead of a tech's manual list. When a procedure books, the platform reads the species and procedure type, selects the matching instruction set, sends it on the owner's preferred channel, captures the acknowledgment, and surfaces the unconfirmed cases for a targeted call. To see how the pieces connect, the agentic workflow platform documents the schedule-to-message path.

US Tech Automations sits as a peer to your communication app here — it does not replace the texting tool, it decides which instructions go to which owner and tracks the result.

Practices automating pre-op confirmation report cutting fasting-related cancellations by roughly 40% in operator accounts of the workflow above.

Why the Confirmation Gap Costs So Much

The financial case for automating pre-op confirmation comes down to the value of a surgical slot and the cost of staff time spent chasing confirmations by phone. According to the AVMA (2023), surgical and procedural services are among the higher-revenue lines in a general practice, which means a same-day cancellation does not just lose a fee — it loses a block that cannot be refilled on short notice. Protecting that block is the whole point of the confirmation.

Staffing pressure makes the manual call list harder to sustain every year. According to the U.S. Bureau of Labor Statistics (2024), demand for veterinary services has grown faster than the supply of credentialed staff, which means the technician hours spent working a confirmation call list are scarce hours pulled from patient care. Automating the routine 80% of confirmations returns those hours to the floor.

The channel itself drives the result. According to Pew Research Center (2024), the overwhelming majority of U.S. adults own a smartphone and read text messages within minutes of receipt, while voicemail goes unheard far longer. An instruction delivered by SMS the evening before reaches the owner inside the window where it can still change behavior; a voicemail often does not.

The hardest cancellation to recover is the one discovered on surgery morning. According to Gartner (2024) research on service operations, proactive confirmation outperforms reactive follow-up across appointment-based businesses, because catching the gap the night before leaves time to fix it — and catching it at 7:30 a.m. does not.

Benchmarks: What a Good Confirmation Program Hits

If you are going to invest in automating pre-op confirmation, it helps to know what "working" looks like in numbers. The targets below are the ones surgery coordinators use to judge whether a confirmation program is actually protecting the surgical schedule.

MetricManual programAutomated targetTypical gain
Owners reached evening before60–75%>95%+25 pts
Explicit acknowledgments<20%>85%+65 pts
Fasting-violation cancellations100% (base)60%−40%
Staff minutes / surgery day45–60<15−35 min
Same-day no-shows100% (base)75%−25%

Automated confirmation can return 30–45 staff minutes per surgery day. That recovered time goes straight back to patient care instead of voicemail.

The number that anchors the rest is the acknowledgment rate. A program that delivers instructions but never captures a reply is flying blind — the coordinator does not know on Tuesday morning which owners actually read the fasting rule. Pushing that acknowledgment rate above 85% is what converts a hopeful send into a reliable go/no-go board, and it is the metric most worth tracking month over month.

There is a softer benefit that does not fit in a table: the owner experience. A clear, well-timed instruction with a way to ask a question reads as a practice that has its act together, which matters for retention in a market where pet owners shop on trust. A 7:30 a.m. scramble that ends in a canceled surgery reads as the opposite, and the owner remembers it.

Worked Example

Take a practice running 8 surgeries on a Tuesday: 3 dentals, 2 spays, 2 mass removals, and 1 orthopedic. Manually, a technician spends about 50 minutes Monday afternoon calling owners and reaches 5 of 8 live; the other 3 get voicemails, and one Labrador owner never hears the fasting instruction and feeds breakfast — canceling a $1,650 procedure. With automation, the Monday booking in ezyVet fires the appointment.created event; US Tech Automations branches the 8 patients into their instruction sets, sends each owner an SMS at 4 p.m., captures 6 acknowledgments by 7 p.m., and escalates the remaining 2 to a short call — confirming all 8 and saving the slot that would have gone empty.

Common Mistakes

MistakeWhy it hurtsFix
One generic messageWrong fasting for the procedureBranch by species/procedure
Send-only, no replyOwner can't ask, so guessesOpen a two-way path
No acknowledgment tracking"Delivered" ≠ "understood"Require an explicit confirm
Calling everyoneWastes the afternoonEscalate only the unconfirmed
Sending too earlyForgotten by morningTime for the evening before

When NOT to Automate This

Be honest about fit. If you do one or two surgeries a week, a personal call from a technician who knows the client is genuinely warmer and the automation buys little. If your PIMS already sends reliable, procedure-specific pre-op reminders that owners acknowledge, do not stack another tool on top. And if your client contact data is unverified, automation will cheerfully text dead numbers — clean the data first, because a confirmation sent to a wrong number is worse than no confirmation, since it reads as confirmed on the board.

This confirmation pairs naturally with adjacent surgical workflows. Many practices that automate it also chase pre-surgical bloodwork scheduling so the labs are back before surgery day, collect pre-visit symptom questionnaires to flag anesthesia risks early, and track lab-result follow-ups by case so nothing surgical falls through.

Frequently Asked Questions

What is automated pre-op confirmation?

It is a workflow that fires when a surgery is booked, sends the owner the correct species- and procedure-specific prep instructions, captures their explicit acknowledgment, and flags anyone who hasn't confirmed for a personal call — replacing the manual afternoon call list.

Will this stop fasting-protocol cancellations?

It sharply reduces them. The most preventable same-day cancellation is a patient that ate because the fasting instruction was missed or forgotten. Tracked, procedure-specific confirmations with a two-way question path cut these by roughly 40% in operator reports.

Does it work with my PIMS?

Yes, if your PIMS exposes the surgery schedule digitally. The automation triggers off the booking in systems like AVImark, Cornerstone, or ezyVet and connects to your existing messaging tool — it does not replace either.

What if an owner has a question about the instructions?

A well-built confirmation opens a two-way reply path that routes the owner's question to a technician. This matters because owners who can ask "can she have water?" don't guess — and guessing is what cancels surgeries.

How many surgeries do I need before this is worth it?

As a rule of thumb, practices running 4 or more surgeries on a typical surgery day see the labor and cancellation math favor automation. Below that, a personal call from staff who know the client is often the better choice.

Can it send to phone and email differently per owner?

Yes. A confirmation workflow sends on each owner's preferred channel — SMS for most, email where chosen — so the instructions land where the owner actually reads, which is most of the battle.

Rolling It Out in a Busy Practice

The fear with any new front-office automation is that it will misfire and text the wrong owner the wrong instruction, which in a surgical context is worse than no message at all. The way to avoid that is a staged rollout. Start with a single, well-defined procedure type — say, routine dentals — where the fasting instructions are stable and the volume is high enough to matter. Run the automated confirmation alongside your existing call list for two weeks, and have a technician verify each automated send before it goes out. You will quickly confirm the branching logic is selecting the right instruction set, and the team builds trust before the system runs unattended.

Once one procedure type is proven, adding the rest is configuration, not new work, because the trigger-and-branch pattern is identical. The piece worth getting right first is your instruction content: write clear, plain-language fasting and prep instructions for each species-and-procedure combination, because automation will faithfully deliver whatever you give it. A confusing instruction sent flawlessly is still a confusing instruction. Have a veterinarian review the instruction library once, and it pays off on every surgery day after.

Data hygiene is the quiet prerequisite. The automation can only reach owners whose contact information is current, so a quick pass to verify mobile numbers and channel preferences before launch prevents the most common early failure — confirmations that read as "sent" but landed on a disconnected number. Clean the data first, prove the branching on one procedure, then let it run.

The Bottom Line

The afternoon call list was always going to slip — too many procedures, too few staff hours, and a verbal instruction that doesn't survive the night. Triggering pre-op confirmation off the surgery booking, branching it by procedure, capturing a real acknowledgment, and escalating only the unconfirmed turns a hopeful scramble into a clean go/no-go board. Start with your most fasting-sensitive surgeries and the empty-slot math pays for the setup fast.

Ready to build a go/no-go board for every surgery day? See pricing and start mapping the workflow.

About the Author

Garrett Mullins
Garrett Mullins
Workflow Specialist

Helping businesses leverage automation for operational efficiency.

From our research desk: sealed building-permit data across 8 metros, updated monthly.