Every other clinic on this blog sends a message to the person it is about. A veterinary practice does not, and almost everything awkward about vaccination reminders follows from that one fact.
The patient is the animal. The recipient is the owner. One owner may hold four patients, on four schedules, of two species — and the system that gets this wrong sends four messages on a Tuesday morning and teaches somebody to mute the practice.
The schedule belongs to the animal, not to the practice
A clinic-wide annual default is the commonest mistake, and it is wrong in both directions at once. A puppy on a primary course needs contact in weeks, not a year. An indoor cat and an outdoor cat of the same age do not carry the same risk and should not carry the same schedule. A rabbit is on neither.
- Species first. What is due, and when, differs before anything else does.
- Then lifestage. Primary courses, the first booster, and adult maintenance are three different cadences, and a puppy or kitten moves between them within a year.
- Then exposure. Indoor versus outdoor, boarding, breeding, travel. These change the schedule and they change over the animal's life.
- Then the legal floor. Where rabies vaccination is a legal requirement rather than a clinical recommendation, that date is not yours to reason about.
Guidance on how far boosters can be spaced has moved over the last two decades, and it differs by vaccine, by country and by whether titre testing is available to you. This is a subject to take from your own veterinary association rather than from a software company — what a system owes you is the ability to hold whatever schedule you decide on, per animal.
One household, one message
The multi-pet household is where good intentions produce an unsubscribe. Four animals due within a fortnight, four separate reminders, and the owner has an inbox that reads like a subscription they did not ask for.
The fix is to make the household the unit of communication while keeping the animal the unit of record. One message listing what is due for whom, one appointment booked for the lot where that is clinically sensible, and a single conversation rather than four.
Example
The same household, both ways
- Owner has two dogs and a cat
- Boosters fall on 4th, 11th and 19th of the month
- Per-animal: three messages across three weeks
- Per-household: one message, one visit, three vaccinations
- The second also fills one appointment slot instead of three
That last line matters more than it looks. Bringing three animals into one visit is better for the diary and better for the owner, and it only happens if the system can see that the three belong together.
The message nobody remembered to stop
This is the failure that has no equivalent in any other speciality, and it is the one worth building against first: a vaccination reminder for an animal that has died.
It arrives from a practice that was often present at the end, and it lands as evidence that nobody there noticed. No amount of good clinical work survives it well, and it is not a rare edge case — it is a certainty at some volume, which makes it a system design question rather than a matter of care.
- Mark it once, and have it stop everything. Deceased status must reach reminders, recalls and any promotional list in the same action. A flag that only stops one stream is worse than no flag, because staff believe it worked.
- Check it before a sweep, not after a complaint. A short list of animals with no contact for an unusually long time is worth a human glance before anything sends.
- Make it reversible only by a person. Nothing automated should un-set it — a returning visit for a sibling animal must not resurrect a record.
If you take one thing from this piece: test that path with a real record before you trust the system. Mark a test animal deceased, then run whatever sends. The five minutes this takes is the cheapest insurance in the practice.
What to send, and what not to
The message itself is unremarkable and short: who it is about, what is due, roughly when, and a way to book that does not involve the phone at nine in the morning. Two things are worth being careful about.
| Instead of | Write | Why |
|---|---|---|
| Your pet is due for vaccination | Bella is due her booster in early March | The name is the whole message. A household with four animals cannot act on "your pet". |
| Overdue — book now to keep protection | Bella's booster was due in January — here is how to book | Urgency about an animal's health reads as pressure, and it is the tone owners complain about. |
| A reminder plus this month's dental offer | The reminder, and nothing else | Attaching an offer turns a clinical message into marketing, with the consent and opt-out that implies. |
What to measure
Not messages sent. The figure that says whether this works is the share of animals due in a period who were actually seen — and it should be read per species, because a practice can be excellent with dogs and quietly losing every rabbit on its list.
vaccination compliance = animals vaccinated ÷ animals due, per speciesThen look at the households you have not seen in eighteen months. Some moved, some changed practice, and some have an animal you have no record of losing. That list is worth a person going through it once a year, and it is the same list that quietly inflates every other number you report.
The order worth doing it in
- Test the deceased path with a real record, today.
- Move schedules off a clinic-wide default and onto species and lifestage.
- Group by household so one owner gets one message.
- Put the animal's name in the first line.
- Measure compliance per species, and read the eighteen-month list once a year.
The first step is not there for tidiness. Everything else on this list improves a number; that one prevents the message that costs you a client you had for a decade. What the rest of this looks like for a veterinary practice is written out separately, and the general distinction between a recall and a reminder is worth reading first if the two are being used interchangeably in your practice.
Common questions
- How often should vaccination reminders be sent?
- The interval belongs to the animal — species, lifestage and exposure — rather than to the practice. A puppy on a primary course needs contact in weeks; an adult indoor cat does not. Guidance on booster spacing differs by vaccine and by country, so take the schedule from your veterinary association and keep it per animal.
- How do we handle owners with several animals?
- Make the household the unit of communication and keep the animal the unit of record: one message listing what is due for whom, and one visit where that is clinically sensible. Four separate messages in a fortnight is how a practice teaches somebody to mute it.
- How do we stop reminders for an animal that has died?
- Mark the record once and have that single action reach every stream — reminders, recalls and anything promotional. A flag that stops one but not the others is worse than none, because staff believe it worked. Test the path with a real record rather than trusting it.
- Should a vaccination reminder mention an offer?
- No. A reminder about care that is due is part of providing that care; attaching a promotion turns it into marketing, with the consent and opt-out that implies. Keep them separate and keep their switches separate, or you risk losing the ability to send either.
- What should we measure?
- The share of animals due who were actually seen, per species — not the number of messages sent. Reading it per species is what surfaces the case where a practice is excellent with dogs and quietly losing every rabbit on its list.
Read next
Records that know the difference between the patient and the reader.
Clinic+ holds the animal as the record and the owner as the contact, with species-aware schedules and weight tracked across visits — so what is due follows the animal rather than a clinic-wide default. Free to start, no card.
Clinic+ for veterinary clinics