Automated Bordetella Expiration Reminders With a Front-Desk Escalation

Yes — an automated text goes out 30 days before a client’s Bordetella expires, and if it lapses anyway, the client’s record turns a visible color the moment anyone on your front desk opens it, so nobody has to remember to check by hand. PocketSuite powers 7,000+ service businesses, including 1,000+ pet service businesses, whose clients have collectively processed nearly $1 billion in income and scheduled over 9.2 million appointments.

Bordetella tracking is one of those recurring compliance tasks that’s easy to build a manual process around and just as easy to let slip once the business gets busy. The goal isn’t just sending one reminder — it’s making sure an expired vaccine never quietly slips through a booking because nobody happened to notice.

Sub-accounts is where the vaccine record itself lives: a custom field on the client’s pet profile holds the Bordetella document with its own expiration date, set once at intake and updated whenever a new record comes in.

The Reminder That Goes Out on Its Own

Once that expiration date is on file, Scheduled Messages sends the client an automated text 30 days ahead of it, asking them to upload a fresh Bordetella record before their next stay — no one on staff has to remember to send it, and it goes out the same way for every client, every time.

Tayata Thomas, owner of The Lovable Dogs Club, described the value of that kind of automation directly: “sometimes I can put it on a set time and it’ll send out the invoice to the customer, you know, while I’m asleep. So, I like the fact that things can be done automatically.” The same logic applies to a compliance reminder — it goes out on schedule whether or not anyone is watching the clock.

According to the 2026 Pet Boarding, Daycare & Resort Industry Benchmarking Report, 54% of pet businesses report that 75% or more of their monthly revenue comes from repeat clients — the same long-tenured relationships a reliable compliance reminder is built to protect, since a lapsed vaccine record is exactly the kind of avoidable friction that can interrupt a repeat client’s next booking.

The same report found that only 4% of $1M-and-up boarding businesses report not typically being fully booked during peak periods, compared with 22% of businesses under $150K. At that kind of consistent peak-season volume, a manual, memory-dependent compliance process has the least room to fail, which is exactly when an automated reminder and flag matter most.

What Your Front Desk Sees If a Client Doesn’t Respond

The text reminder is only half of it. Icons puts a color-coded flag directly on the client’s profile tied to that same expiration date: yellow once the Bordetella record is within 30 days of expiring, red the moment it actually expires. That flag shows up automatically the instant anyone opens the reservation or client profile — no separate report to run, no list to cross-check.

That means whoever answers the phone at your front desk, whether or not they sent the original reminder, sees the same red or yellow flag the second they pull up the client’s file to confirm a booking. The reminder handles the client side; the flag handles the staff side, and both are reading from the exact same expiration date on the same record.

Because the flag lives on the client profile itself rather than a separate compliance spreadsheet, it’s visible everywhere that profile shows up — the booking screen, the calendar, the client list — so a lapsed Bordetella record is hard to miss no matter which screen your team happens to be working from that day.

Setting the Reminder Up Once, for Every Client

The reminder is built once, against the Bordetella expiration field, and it applies to every client whose pet has that field on file — there’s no separate reminder to configure client by client. As soon as a new client’s Bordetella record and expiration date are entered, the same 30-day reminder schedule applies to them automatically.

That consistency matters for a business handling dozens or hundreds of active clients at once. A manual reminder process, even a well-intentioned one, tends to slip during a busy week; an automated one sends on the same schedule whether the front desk is having its quietest week of the month or its busiest.

What Happens After the Client Uploads a New Record

Once a client uploads a fresh Bordetella document, the new expiration date replaces the old one on the pet’s profile, the flag on the record clears back to its normal state, and the reminder schedule resets against the new date. Nothing about the process needs to be manually reset by staff — the same field that triggered the reminder and the flag is what clears both once it’s updated.

That means the whole cycle — reminder, upload, cleared flag, next reminder scheduled — repeats on its own for as long as the client keeps boarding with the business, without anyone having to manually track where a given client is in that cycle at any given time.

Applying the Same Pattern to Other Vaccines

Bordetella is rarely the only document a boarding business tracks. Rabies, a distemper-combination vaccine, or a business’s own required behavior evaluation can each get the same treatment — a custom field on Sub-accounts with its own expiration date, its own reminder built on Scheduled Messages, and its own color-coded flag through Icons.

Because each document gets its own field rather than a shared one, a client whose Bordetella is current but whose rabies record is about to lapse shows exactly that distinction — not a single vague “compliance” status that leaves staff guessing which specific document actually needs attention.

What a Manual Process Tends to Miss

Businesses that track vaccine expirations by hand usually rely on someone remembering to check a spreadsheet or a paper file on a regular basis — a task that competes with everything else on a busy day and tends to slip exactly when the business is at its busiest, which is also when a lapsed vaccine is most likely to slip through unnoticed.

An automated reminder and an automatic flag don’t compete with the rest of the day’s workload the same way. The reminder goes out on schedule regardless of how busy the front desk is, and the flag is already sitting on the profile the next time anyone opens it, so there’s no separate task that has to get remembered in the middle of a full day.

What to Do When a Client Still Doesn’t Renew

Occasionally a client sees the reminder, sees the flag, and still shows up without an updated Bordetella record — usually because life got in the way rather than any intent to skip the requirement. Because the flag makes the gap obvious the moment staff open the reservation, that conversation happens at check-in rather than being discovered later, once the dog is already settled into boarding for the week.

Having a clear, consistent policy for that moment — whether it’s requiring the record before drop-off or accepting it within a short grace window — is easier to apply fairly when every staff member is working from the same visible flag, rather than each person handling a compliance gap differently depending on who happens to be at the front desk that day.

Why This Matters More as a Client Base Grows

A business with a handful of regular clients might genuinely be able to keep vaccine expirations straight from memory, at least for a while. That approach stops scaling the moment a business has dozens or hundreds of active clients, each renewing on their own schedule — no single person can reliably hold that many individual dates in their head, no matter how organized they try to be.

Automating the reminder and the flag removes the dependency on any one person’s memory entirely. The system tracks every client’s expiration date the same way regardless of how many clients there are, which is exactly the kind of process that needs to hold up as a boarding business grows rather than only working at a smaller scale.

Introducing the Requirement at the Very First Booking

The smoothest version of this whole cycle starts with a new client understanding the Bordetella requirement before their very first stay, not discovering it midway through booking. Building the document upload into the same intake flow a new client already completes means the requirement is presented once, clearly, at the moment it’s most relevant.

A client who uploads their Bordetella record at intake starts the whole reminder-and-flag cycle from a compliant baseline, which tends to make every renewal after that first one feel like a routine, expected step rather than a new requirement being introduced partway through the relationship.