Every clinic has a due-list problem. Not a reminder problem — a due-list problem. The reminders are easy once you know who is due, for what, and on which date. The hard part is that the data to build that list already exists in your records, but nobody has turned it into a working queue.
This post is about the operational plumbing: how the list gets built, who touches it on which day of the week, what a good WhatsApp message looks like, and how you measure whether the effort is actually producing bookings. There's a worked week at the end — explicitly illustrative, not a real clinic.
Why the Due-List Doesn't Build Itself
When a vet gives a deworming tablet or a DHPPi booster, the clinical record captures what was done today. What it rarely captures — unless someone explicitly sets it — is the forward date: when this patient is next due. That's the gap. The visit is logged; the future obligation is not.
In a paper or spreadsheet clinic, the receptionist would need to flip back through every record from three months ago to find deworming candidates, or twelve months ago for annuals. Nobody does this consistently because it takes forty minutes and the waiting room is already full. So the list never gets built, and the bookings never happen.
The fix isn't a reminder tool. It's a habit of writing the next-due date at the point of service — either into your PMS or onto a physical card — so that a list can be pulled by date range rather than reconstructed by memory.
What Goes on a Due-List (and What Doesn't)
Keep it to high-compliance, predictable-interval services. If the interval is fuzzy or owner-dependent, it creates awkward messages and low conversion.
- Deworming — typically every 3 months for adults, monthly for puppies/kittens under 6 months
- Core vaccines — annual boosters (DHPPi, Rabies) and the puppy/kitten primary series
- Anti-rabies — often on a separate annual cycle from the combo vaccine
- Tick/flea prevention — monthly or quarterly depending on product used
- Dental checks — annual, easy to batch with a vaccine visit
Leave off: post-surgical follow-ups (those need a personal call, not a batch message), chronic-disease recheck reminders (same reason), and anything where the interval varies by patient. Those are handled separately in the consult notes.
Building the List from Your Records
If you're on a PMS that captures next-due dates, run a filter: service type + due date = next 14 days. Export it. That's your working list for the week.
If you're on paper or a spreadsheet, you need a separate due-date register — one row per patient per service, columns for patient name, owner name, WhatsApp number, service, last-done date, and next-due date. It's a one-time setup cost of a few hours, then a five-minute daily sort by due date. The pet-vaccination-record-software-register-format post has a register template you can adapt.
Either way, the output is the same: a list of names, numbers, and what they're due for, sorted by date. This is what your front desk works from.
Who Works It, on Which Day
Assign one person — usually the receptionist or a vet tech with a quieter afternoon shift — and give them a fixed slot. Not "when they have time." A fixed slot.
- Monday, 2–3 PM: Pull the due-list for the next 14 days. Remove anyone who already has an appointment booked. Print or open the working list.
- Tuesday, 2–3 PM: Send the first batch of WhatsApp messages — aim for no more than 15–20 at a time so replies are manageable.
- Wednesday, 10–11 AM: Check replies, book confirmed appointments, flag non-responders.
- Thursday, 2–3 PM: Send a single follow-up to non-responders. One follow-up only.
- Friday, end of day: Count the week's bookings that came from the due-list. Log it.
Five slots, each under an hour. That's the whole system. The discipline is keeping those slots protected — they get dropped the moment a busy Tuesday walk-in surge hits, which is why the Tuesday slot is at 2 PM, not 11 AM.
What to Say on WhatsApp
Short, specific, personal. The message should read like it came from a person who knows the pet, not a broadcast from a software system.
Hi [Owner name], this is [Receptionist name] from [Clinic name]. Bruno's 3-month deworming is due around [date]. We have slots on Wednesday and Friday morning — want me to book one? Just reply with a time that works.
Notice what's in that message: the pet's name, the specific service, an approximate due date, two concrete slot options, and a low-friction ask. What's not in it: a promotional tone, a discount, or a generic "it's time for your pet's health check."
For the follow-up on Thursday, keep it even shorter:
Hi [Owner name], just following up on Bruno's deworming — happy to book whenever suits. No pressure, just let us know.
Two messages maximum per reminder cycle. If there's no reply after the follow-up, move them to a 30-day "try again" list. Don't keep messaging — it damages the relationship. The vaccination-reminders-that-get-pets-back-in post goes deeper on message tone and timing if you want to refine further.
A Worked Week — Explicitly Illustrative
Take a two-vet clinic seeing roughly 20 patients a day. In this example, Monday's pull shows 40 patients due for something in the next 14 days — 18 deworming, 14 annual vaccines, 8 anti-rabies. Twelve of them already have appointments booked. That leaves 28 to contact.
Tuesday afternoon, the receptionist sends 20 messages (leaving 8 for a second batch). By Wednesday morning, she has 11 replies: 8 confirm a booking, 2 say they'll call back, 1 says they've moved to another clinic. She books the 8 immediately — that's roughly 40 minutes of work.
Wednesday she sends the remaining 8 messages. By Thursday she has 5 replies, 3 of which convert to bookings. Thursday afternoon she sends follow-ups to the non-responders from Tuesday's batch — 9 messages. By Friday she picks up 3 more bookings from those.
In this illustrative scenario: 28 messages sent, 14 bookings confirmed. Assume an average visit value of ₹600 (deworming + consultation at conservative rates) — that's ₹8,400 in confirmed revenue from roughly 3 hours of receptionist time across the week. The math changes with your actual visit value and your actual reply rate, but the structure holds.
How to Count the Bookings It Produced
You need a way to tag appointments that came from the due-list, separate from walk-ins and self-booked returns. The simplest method: a column in your appointment book or PMS notes that says "DL" (due-list). At end of week, count the DL appointments that showed up and paid.
Track two numbers weekly. First: bookings confirmed per messages sent — this tells you whether your message is working. If you're sending 30 messages and getting 2 bookings, the message or the list quality is the problem, not the process. Second: show-up rate for DL appointments versus walk-ins — due-list patients tend to show up at a higher rate because they've actively confirmed, which is worth knowing when you're planning your schedule.
If your no-response rate is high even after the follow-up, check whether the due dates in your records are accurate. A message that arrives two weeks after a pet was already dewormed elsewhere will always be ignored — and enough of those will erode trust in your reminders over time.
When the List Gets Too Long to Work Manually
A two-vet clinic with good records will eventually have a due-list of 60–80 patients per fortnight. That's manageable manually. At 120+, the Tuesday batch-sending slot starts to overflow, replies stack up unread, and the system breaks down — not because the process is wrong but because the volume has outgrown the tool.
That's the point at which a PMS that auto-generates the due-list and queues WhatsApp reminders earns its keep. CliniCore's WhatsApp-native reminders pull directly from the next-due dates recorded at consult, so the Monday pull and the Tuesday send become one step rather than two. The receptionist's time shifts from building the list to handling the replies — which is the part that actually requires a human.
The due-list is also where revenue leakage becomes visible in a different way: not unbilled items from yesterday's consult, but services that were delivered, recorded, and then never followed up — so the next cycle never happened. A practice that deworms 200 patients a year but only follows up on 120 of them is leaving 80 deworming visits' worth of revenue on the table every year, without any single moment where it felt like a loss.
If you want to see how much your current records could produce in forward bookings, the free 60-second audit is a practical starting point — it's designed for exactly this kind of gap between what your data holds and what your schedule reflects.