Vet Vaccination Reminders Going Out Twice: Symptom, Cause and Fix
Short answer: Duplicate or wrong vaccination reminders almost always come from the data behind them, not from the sending tool. The usual causes are one owner stored as two client records, a pet with several due items rolled into several messages, a reminder rule that fires from both the vaccine date and the booster date, and a due date that was never cleared after the visit. Find the pattern first by collecting five or six real complaints, match each to a cause in the table below, and fix the record or rule before touching the message wording. Test every change on a small group of dummy pets before the next batch runs.
Start with the complaints, not the settings
Open the last month of complaints and write one line for each: what the client received, what they expected, and which pet it was. Illustrative examples might read "got the same reminder on Tuesday and Thursday", "reminded for a rabbit vaccination that was done last week", or "two separate texts for the dog and the cat, an hour apart".
Do not guess from the outside. Pull the reminder log for each client and compare it with the patient record. The log shows when each message was created, which rule produced it, and which record it was attached to. That single comparison usually points to one of the causes below.
Symptom, cause and fix
| What the client sees | Likely cause | Fix |
|---|---|---|
| The same reminder twice on different days | Owner exists as two client records, often one with a typo in the phone or email | Merge the records, keep one preferred contact, add a duplicate check at registration |
| Two messages within the hour for different pets | Reminders are generated per animal, not per household | Group by owner and send one message listing each pet |
| Reminder for a vaccine already given | Due date not advanced after the visit, or the treatment was recorded as a free-text note instead of a coded item | Link each vaccination product to its next-due rule, and clear the old due item when the new one is recorded |
| Reminder sent after the booking was made | Reminder job runs before the booking sync, or only checks future bookings of one type | Skip anyone with any future appointment for that pet, and run the sync first |
| Wrong pet name or species in the text | Merge fields pulling from the first animal on the account | Pass the pet's own ID into the template |
| Reminder for a pet that has died or moved | Pet not marked inactive | Add a deceased/left status and exclude it, plus a gentle manual check for older accounts |
| Messages arrive in the middle of the night | Batch time set in the server's time zone | Set a send window in the practice's local time |
| Same message by email and SMS | Both channels are enabled with no priority | Choose one primary channel per owner, with the other as fallback only |
Merging duplicate clients safely
Duplicates are the biggest single source. They arise when a partner phones in and gets a new account, when a pet is registered at a boarding stay, or when an old import never matched. Before merging, export the list of suspected pairs: same surname with the same postcode or Eircode, or the same mobile number. Review them by hand. Never merge on name alone, since two households in one street can share a surname.
After a merge, check that the pets, history and communication preferences all moved across, and that the contact kept is the one the owner actually uses. Then add a prompt at the front desk: search by phone and surname before creating a new client.
Group the message by household
A person with a dog, a cat and a rabbit who gets three texts is far more likely to unsubscribe or complain than one who gets a single list. Change the rule so the job works in two steps: find every pet due in the next window, then group the results by owner and send one message.
A plain illustrative template:
"Hello Aoife, these pets are due a vaccination in the next three weeks: Finn (dog), Mochi (cat). Reply or use this link to choose a time."
Keep the list short. If a pet has several items due, the message can say "vaccination and health check" without a table of products.
Make "due" mean one thing
Many practices have two ideas of due: the date the vaccine expires and the date the practice wants to see the animal. If the reminder rule is fed by both, an animal can generate two reminders for one visit. Pick one field as the trigger, usually the date by which you would like the booking, and document how it is calculated for each product.
Also decide what clears a reminder: a completed visit, a future booking, or a note that the owner declined. Write those three conditions down and check that the software really applies them. Clinical decisions about which vaccines an animal needs and when belong to your vets, so the reminder rule should read from their recorded next-due date and never invent one.
A safe way to test
- Create three dummy pets in a test account using your own staff phone numbers.
- Give them cases from the table: two pets on one owner, a vaccination that has just been given, and a future booking.
- Run the reminder job in a preview or dry-run mode if your system has one, otherwise on a small filtered list.
- Check the logs, then the phones.
- Only then switch the real batch on, and watch the first full run for the first day.
Keep a note of the change and the date, so if complaints change in nature you can see what happened.
Checking deliverability
If clients say a message never arrived, that is a separate problem from duplication. Email may land in spam or be rejected, and SMS can be blocked by a number format error. For email, the sender authentication settings on your domain matter, and Google's email sender guidelines explain the basics. Send a test to a Gmail address and to an Outlook address before blaming the client.
FAQ
Is it safe to send one message for several pets?
Yes, and it usually reads better. Make sure each pet's own due date and name are correct in the list.
How many reminders should one pet get?
Most practices use one first reminder and one follow-up, then a staff call list. Choose what fits your clients and keep it consistent.
Do we need new software?
Often not. The data rules and merge discipline matter more than the product. Change tools only if your system cannot group by owner or exclude future bookings.
Can automation decide which vaccines a pet needs?
No. It should only read the next-due date your vet recorded and prompt a booking.
If your practice's reminders need a proper clean-up or a small custom layer on top of your current system, talk to us and we will start with a log review.