Capture Lapsed Vaccines: 3 Reminder Workflows for 2026

A dog overdue for its rabies booster does not feel sick, so its owner does not call. The vaccine quietly lapses, the protection window closes, and three months later that pet shows up at a competing clinic for a wellness visit you should have owned. Multiply that across a 4,000-active-patient practice and the leak is not a rounding error — it is a five-figure annual hole in core-service revenue that never appears on a P&L because the appointment simply never happened.

The reason it happens is mechanical, not clinical. Your medical records live in AviMark. Your phones and texts run through one channel. Your client-facing app and online booking sit in PetDesk. Each system knows part of the truth, but no system connects "Bella's DHPP is due on March 14" to "text Bella's owner on March 1 with a one-tap booking link." A staff member has to remember, pull a report, dial, leave a voicemail, and chase. They do not have time, so the work decays. This guide shows three concrete reminder workflows that wire AviMark, Twilio, and PetDesk together so a due date fires a timed message, books the slot, and updates the chart — without anyone running a manual recall list.

TL;DR

A vaccination reminder workflow reads upcoming and overdue due dates from your practice management system, sends timed text or email reminders with a booking link, and writes the result back to the patient record. Done right, it converts silent lapses into booked appointments. The three workflows below — proactive due-soon, lapsed-recovery, and post-visit next-due scheduling — cover the full lifecycle. Below: a glossary, a benchmark table, a worked example with real platform fields, and an honest section on when this is not worth building.

Key Takeaways

• A vaccine lapses because no single system connects the due date in AviMark to an outbound reminder and a booking link — the data exists but never moves.

• The fix is three linked workflows: proactive due-soon, lapsed-recovery, and post-visit next-due, each triggered by a date in the medical record.

• Vet practice software market: $1.8B in 2024 according to Grand View Research (2024), so the integration tooling to do this is mature and well-supported.

• A worked example shows a 4,200-patient clinic recovering 38 lapsed vaccinations a month by texting the right owner at the right time.

• US Tech Automations connects the AviMark due-date export, the Twilio send, and the PetDesk booking write-back into one workflow — for clinics already running all three, not a single-doctor mobile practice.

What a vaccination reminder workflow actually is

A vaccination reminder workflow is an automated sequence that reads vaccine due dates from your practice management system, sends timed reminders through text or email with a way to book, and records the outcome back in the patient chart. It is plumbing, not magic: the value is entirely in moving a date from one system to a message in the right pet owner's pocket at the right moment.

The piece most clinics get wrong is treating "reminders" as one thing. A pet whose rabies vaccine is due in two weeks needs a different message than a pet that lapsed four months ago, which needs a different message than a pet you just vaccinated today and want back in a year. Collapsing these into a single monthly blast trains owners to ignore you. Marketing texts average a 19% click-through rate according to EZ Texting (2024), but only when they are timely and relevant — a generic "your pet may be due" blast earns a fraction of that.

The three-workflow model below separates these moments so each message has a clear job. The data source is the same — AviMark's reminder fields — but the timing, copy, and escalation differ.

Who this is for

This guide is for general or specialty veterinary practices with 2,000+ active patients, at least 3 to 4 staff, and an existing stack that already includes AviMark (or a comparable practice management system), a messaging channel like Twilio or a vet-specific texting tool, and PetDesk for client engagement and online booking. If you are doing $700K or more in annual revenue and recall is currently a manual report someone runs "when they get to it," this is built for you.

Red flags — skip this if: you have fewer than 800 active patients (a manual call list is genuinely faster), your records are paper-only or in a system with no export or API, or you do under $400K a year where the per-reminder revenue does not justify integration setup. Automation amplifies an existing process; it cannot invent one that was never there.

The three reminder workflows

Each workflow is defined by its trigger — a specific date relationship in the AviMark record — and its sequence. Here is the structure before we go deep on each.

The proactive workflow is the cheapest revenue you will ever capture because the owner already intends to keep the pet current — they just forgot the date. The lapsed-recovery workflow is harder and lower-converting, but it pulls back patients who would otherwise drift to a competitor. The post-visit workflow is the compounding engine: every vaccine you give today seeds a reminder twelve months out, so the system fills itself over time.

Workflow 1: Proactive due-soon

This workflow scans AviMark daily for any reminder whose due date is exactly 14 days away, then starts a three-touch sequence. The first touch is an email with the pet's name, the specific vaccine due, and a PetDesk booking link. If no appointment is booked, an SMS goes out at 3 days, and a final SMS at the due date itself. The moment a booking lands in PetDesk, the sequence stops — over-messaging a client who already booked is the fastest way to get blocked.

Personalized reminders lift booking rates by up to 30% according to PetDesk (2024), and the personalization that matters most is naming the exact vaccine and pet rather than sending "your pet may be due for something." That specificity comes directly from the AviMark reminder record, which is why the integration — not the copy — is the hard part.

Workflow 2: Lapsed-recovery

When a due date passes without a booking, the patient enters lapsed-recovery. This is a slower, lower-frequency cadence — you are not nagging, you are giving the owner a low-friction reason to come back before they form a habit of going elsewhere. Practices lose 11-15% of active patients to attrition each year according to AAHA (2023), and a meaningful share of that loss starts with a single missed reminder that compounds into "we just stopped going."

The recovery sequence intentionally spaces messages 30 to 60 days apart and varies the channel so the same dead text thread is not the only touchpoint. After 180 days with no response, the patient is flagged inactive and dropped from active recall to avoid wasting sends on owners who have moved or rehomed the pet.

Workflow 3: Post-visit next-due

The most durable workflow runs at checkout. When AviMark logs an administered vaccine, the system reads the protocol interval — one year for rabies, three years for the next rabies cycle, and so on — and schedules the proactive due-soon workflow to fire automatically when that next date approaches. This is what turns reminders from a one-time campaign into a self-sustaining loop. Every visit you complete today guarantees a timed reminder next year with zero additional staff effort.

Where US Tech Automations executes the workflow

The integration is the whole job, and it breaks into three concrete handoffs. First, US Tech Automations runs a scheduled query against AviMark's reminder export — pulling each patient ID, owner contact, vaccine type, and due date — and filters to the records matching today's trigger conditions for each of the three workflows. AviMark does not offer a clean public API, so this step reads the structured reminder report AviMark already generates, normalizes it, and deduplicates against pets that already have a future appointment. That filtered list is what every downstream message is built from.

Second, for each qualifying record, US Tech Automations composes the message from the patient's actual data and sends it through Twilio's Programmable Messaging API, attaching the PetDesk booking link with the pet's record pre-referenced so the owner lands on the right scheduling page in one tap. When the owner books, PetDesk emits the new appointment; US Tech Automations catches that event, halts any remaining reminders in the sequence, and writes a note back to the AviMark patient record so the front desk sees the reminder was answered. You can see how this trigger-action-output pattern generalizes across other clinic tasks in our overview of agentic workflow automation, which is the engine these three vaccination sequences run on. The result is that nobody at the clinic runs a recall report, dials a number, or manually clears a reminder — the loop closes itself.

Worked example

Consider Maple Ridge Animal Hospital, a two-doctor practice with 4,200 active patients running AviMark, Twilio, and PetDesk. Before automation, a technician spent roughly 6 hours a week pulling recall reports and leaving voicemails, recovering about 9 lapsed vaccinations a month. After wiring the three workflows together, the system scans AviMark each morning and finds, on an average day, 22 patients hitting the 14-day proactive trigger and 14 patients hitting a lapsed-recovery touchpoint. When an owner taps the booking link, PetDesk fires an appointment.created event; the workflow listens for that payload, matches it on patient_id, cancels the two remaining queued Twilio sends, and posts a confirmation note to AviMark. Over the first full month, Maple Ridge booked 38 lapsed or due-soon vaccinations it would otherwise have missed — at an average vaccine-visit value of $185, that is roughly $7,030 in recovered revenue against a workflow that now runs with zero technician hours on the recall list.

Glossary

Quick definitions for the terms that show up across these workflows and vendor docs.

How AviMark, Twilio, and PetDesk divide the work

Each tool owns one layer, and the integration's job is to keep them in sync. AviMark is the system of record for what is due and when. Twilio is the delivery layer for SMS and the fallback for owners who do not engage with email. PetDesk owns the client-facing booking experience and the appointment event that closes the loop. Here is how they compare on the role each plays in a reminder.

The gap between "what AviMark knows" and "what PetDesk can do" is exactly the space the automation fills. A standard SMS segment is 160 characters according to Twilio (2024), so reminder copy has to be tight — name the pet, name the vaccine, give the link, and stop. The integration handles the segmentation and the opt-out logic so a single noncompliant message does not put your whole sending number at risk.

Benchmarks: manual recall vs. automated workflows

The case for automating is easiest to see side by side. These figures reflect typical mid-sized general practices; your numbers will vary with reminder hygiene and protocol mix.

The personalization row is the one that moves revenue. Text messages see a 98% open rate according to Gartner (2023) — but an open is worthless if the message does not tell the owner exactly what their pet needs and give them a one-tap way to book it. The automation guarantees that specificity on every send because it is reading the actual reminder record rather than a staff member's best recollection.

Common mistakes that quietly kill recall

These are the failure patterns that show up most often when a clinic tries to do this manually or with a half-built integration.

• Sending one monthly blast instead of timed triggers. A batch reminder reaches a pet 27 days before it is due or 12 days after it lapsed — almost never at the moment that books an appointment.

• Not suppressing after a booking. Texting an owner three more times after they already scheduled is the fastest path to an opt-out and a complaint.

• Ignoring the post-visit loop. Without scheduling the next-due reminder at checkout, your recall list shrinks every year instead of compounding.

• Generic copy. "Your pet may be due" converts a fraction of "Bella is due for her rabies booster — tap to book."

• No write-back. If the front desk cannot see that a reminder was answered, they re-contact booked clients and look disorganized.

If you have already mapped your no-show patterns, these recall mistakes will look familiar — the same timing discipline that fixes lapsed vaccines also drives the tactics in our guide to reducing veterinary no-shows.

When NOT to use US Tech Automations

Automation is not always the right answer, and pretending otherwise wastes your money. If you run a solo mobile practice with a few hundred patients, a manual call list a technician works through in an afternoon is cheaper and warmer than any integration — the per-reminder economics simply do not support setup. If your messaging needs are limited to one-off vaccine campaigns a couple of times a year rather than continuous triggered recall, PetDesk's built-in reminder features alone may cover you without a custom workflow layer. And if your records live in a system with no usable export, the cost of getting clean data out can exceed the revenue you would recover — fix the data layer first. The honest test: if a staff member could comfortably run your full recall list by hand in under two hours a month, you do not need this yet.

This same boarding-and-reservation logic — reading a date, sending a timed confirmation, writing the result back — is detailed for the front-desk side in our breakdown of route and boarding reservation confirmations, and the lapsed-list mechanics carry over directly to building lapsed-patient reminder lists.

Frequently asked questions

How does the workflow read due dates out of AviMark?

It reads the structured reminder report AviMark already generates, rather than calling a public API. AviMark exposes reminders as a report containing each patient's ID, owner contact, vaccine type, and due date; the workflow pulls that export on a schedule, normalizes it, and filters to the records matching each trigger condition. This avoids any direct database modification and works within AviMark's supported reporting.

Will pet owners get spammed with too many texts?

No, because every sequence suppresses itself the moment the owner books. When PetDesk fires the appointment-created event, the workflow cancels any remaining queued Twilio messages for that pet and stops the sequence. Owners only ever receive the touches they need to take action — typically one to three per cycle, not a continuous stream.

Do I need all three tools, or can I use just one?

You need a system of record (AviMark or equivalent), a messaging channel (Twilio or a vet-specific texting tool), and a booking surface (PetDesk). PetDesk alone can send basic reminders, but it cannot read AviMark's full reminder report or run the timed, suppressing sequences described here. The three-tool stack is what enables per-patient, per-vaccine timing with booking write-back.

How quickly do clinics see recovered revenue?

Most clinics see the proactive due-soon workflow produce booked appointments within the first two weeks, because those owners already intend to stay current and just needed the nudge. Lapsed-recovery takes longer to show results since you are reactivating colder patients, and the post-visit next-due loop compounds over a full vaccine cycle — so the biggest gains land 6 to 12 months in.

Is automated texting compliant with consent rules?

Yes, when built correctly. Twilio handles opt-out keywords automatically, and the workflow only messages owners who are existing clients with a transactional relationship — vaccine reminders for their own pet. You should still maintain a clear opt-out path and honor it across all three workflows, which the integration enforces by checking opt-out status before every send.

What happens to a patient who never responds?

After 180 days in the lapsed-recovery sequence with no booking, the patient is flagged inactive and dropped from active recall. This keeps your sending reputation clean and your reminder volume focused on reachable owners. The record stays in AviMark, so if that pet ever returns, the post-visit workflow re-enrolls it in the cycle automatically.

Bringing it together

The leak is mechanical and so is the fix. A vaccine due date sitting in AviMark is worthless until something moves it to the right owner's phone at the right moment with a one-tap way to book — and then writes the result back so your front desk stays in sync. The three workflows here cover the full lifecycle: catch pets before they lapse, recover the ones that did, and seed next year's reminder at every checkout so the system fills itself.

If you are already running AviMark, Twilio, and PetDesk and your recall is still a manual report someone runs when they get to it, the gap between those three tools is costing you real revenue every month. Compare what it costs to close that gap and decide whether the recovered vaccinations pay for the build — for most mid-sized practices, the math is not close.