Every autumn the same thing happens at the kennels and daycares I talk to. The holiday calendar fills, the phone gets busy, and a chunk of the "booked" dogs turn out not to be bookable at all, because the owner never sent the vaccine records. Nobody decided to lose that revenue. The request just got buried in a text thread, and the dates were either held for someone who never completed the paperwork or released too late to resell.
As Gideon Wafula, AI Automation Engineer, I build small workflows for local service businesses, and this is one of the cleanest examples of revenue lost to an administrative step rather than a sales problem. The customer already wants to buy. The only thing missing is a document. This post walks through how I would automate that gate for boarding, daycare, and grooming businesses, and where the approach stops working.
Most pet-care facilities require current vaccinations before a stay, and many publish this in their reservation policies. That is a sensible rule. The trouble is how the requirement is enforced in practice. The owner books online or by phone, hears "we will need your records," and then has to contact their vet, wait for an email, and forward it. That is three steps with three chances to forget, and none of them are visible to the facility.
Meanwhile the facility often treats the reservation as confirmed. In peak weeks, holiday dates tend to fill well ahead, so a held kennel that is not actually cleared is a kennel you cannot offer to the next family asking. I am not quoting a statistic here, because I have not seen a clean public number and I would rather not invent one. The pattern is easy to check in your own data: count reservations for your last holiday period that were still missing records within a week of arrival.
Before any messaging, every reservation needs one of four states: not requested, requested, received and verified, or expired before arrival. Most booking tools can hold a custom field or tag for this. If yours cannot, a simple table in a sheet or database keyed on the reservation works. This step is dull and it is the whole foundation, because every later step reads from it.
The instant a reservation is created, the owner gets a text or email with a single link to upload the records, plus a one-line explanation of why. The message names the pet and the dates so it cannot be mistaken for spam. Where owners prefer WhatsApp, the same flow runs there, which I cover under my automation services.
When a photo or PDF arrives, a model step reads the vaccine names and expiry dates and compares them to your written requirements. Clear matches go into a short review queue for staff to approve in one click. Anything unreadable, missing a vaccine, or expiring before the checkout date is flagged with the specific reason. I keep a person on the approval, because a wrong pass here is a health risk to other animals, not just an annoyance. This is the same narrow, supervised pattern I describe in the narrow agents that make money.
If nothing arrives, two or three reminders go out on a schedule tied to the arrival date rather than the booking date. A stay in six weeks gets a gentle nudge; a stay in five days gets an urgent, plain one. Each reminder stops the moment the status changes. The final step before release is a staff task, not an automatic cancellation, so a person decides whether to call the owner first.
If the deadline passes and records are still missing, the dates are released and the next person on the waitlist is offered them. This connects directly to the approach in my post on cancellation backfill and waitlists. The point is that a held-but-uncleared kennel becomes either a confirmed stay or an offer to someone who wants it, with a clear date on which that happens.
Records that were valid at booking can lapse before arrival, and regular daycare and grooming clients carry records that quietly age out between visits. The same table can hold each pet's earliest upcoming expiry. A message a few weeks beforehand, "Bella's records expire on the 12th, here is the upload link," prevents a refused drop-off at the front desk, which is a bad moment for everyone. For grooming and daycare, it also protects recurring revenue, since a client turned away at the door is a client who may try another provider.
If you run a clinic-adjacent business, the reminder mechanics overlap with what I describe in the vet clinic missed-call and no-show post, though the data source differs.
Three things stay with people. First, deciding which vaccines and intervals you require; that is a policy and a health decision, ideally made with your veterinarian. Second, any conversation about an aggressive or medically fragile pet. Third, exceptions, such as a dog with a vet-documented reason for a delayed vaccine. The workflow should route those to staff with the context attached, not try to resolve them.
It also will not fix a capacity problem. If your holidays are full because you are genuinely understaffed, faster paperwork will not create more kennels. What it does is make sure the spots you have go to the dogs that can actually arrive. For the planning side of that, see my notes on seasonal pre-booking and capacity.
Pick two numbers from your own system and compare the same holiday window year over year: the share of reservations that were fully cleared a week before arrival, and the number of last-minute releases or refused check-ins. Do not trust a vendor claim or a blog figure, including mine; your records will tell you whether it helped. If the numbers do not move after a full season, the bottleneck is somewhere else.
The minimum version is the status field plus one automatic request message and one reminder. You can add extraction and waitlist release later, once staff trust the status column. Build time and cost depend heavily on your booking software, so I scope this after looking at how reservations and client records are stored today.
Gideon Wafula builds custom AI automation systems, n8n, WhatsApp, Voice AI, and more.
See Services →