Pharmacy refill reminders on WhatsApp: a simple retention loop
Pharmacies build a refill loop by storing each customer's expected refill date as a custom field, then sending a Utility template a few days before it's due with Reorder and Pickup/Delivery buttons. The bot never advises on dosage or medical questions — it only handles reordering, and routes anything clinical to the pharmacist.
- Store a per-customer refill date as a custom field, calculated from the medicine's typical course length.
- Send the reminder a few days before the refill date, not on the day, so there's no gap in medication.
- Reorder buttons should offer both delivery and in-store pickup, matching how the customer bought last time.
- The bot must never answer dosage, interaction or medical questions — always hand these to the pharmacist.
- A simple loop like this increases repeat orders without needing broadcast campaigns or discounts.
Why refill reminders work well for pharmacies
Unlike most retail, pharmacy repeat purchases are predictable. A customer on a monthly medication needs a refill roughly every 28 to 30 days, give or take. This predictability makes WhatsApp reminders unusually effective: you're not guessing when someone might want to buy again, you know almost exactly when they will need to.
It also solves a real problem for customers: forgetting to reorder in time and running out is common, and a timely nudge genuinely helps rather than just selling. For chronic-condition medication especially, a missed refill can mean a real gap in treatment, which is a stronger reason to build this loop well than any retention metric on its own.
This is also one of the few automation loops where the customer usually welcomes the reminder rather than tolerating it, which means fewer opt-outs and a much longer useful life for the flow than a typical promotional broadcast.
Setting the refill-date field
When a customer first orders a recurring medicine, record two things as custom fields on their contact: the medicine name (without needing clinical detail, just what to reorder) and the expected refill date, calculated from the course length noted on the prescription or order. A 30-day course ordered on the 1st gets a refill date around the 28th, leaving a small buffer.
This field drives everything else in the loop, no manual tracking needed once it's set. Common course lengths and their suggested reminder timing:
| Course length | Refill date (from order) | Reminder sent |
|---|---|---|
| 30 days | Day 28 | Day 24-25 |
| 60 days | Day 56 | Day 52-53 |
| 90 days | Day 84 | Day 80-81 |
The reminder template
Three to five days before the refill date, send a Utility template: 'Hi [name], your [medicine] refill is coming up around [date]. Reorder now to avoid running out.' with Reorder and Not Now buttons. Keep it factual and free of any dosage or health claims: it's a reminder to reorder, not medical guidance.
Utility is the correct template category here since it relates to an existing, ongoing transaction rather than a promotional message. See the template categories guide if you're unsure which category applies. If a customer taps 'Not Now', log the response rather than repeating the same reminder daily; a single follow-up closer to when the medicine would actually run out is enough.
Delivery or pickup — match their pattern
- On Reorder, branch with a Buttons block: 'Home Delivery' or 'Store Pickup', defaulting to whichever the customer chose last time via a stored variable.
- For delivery, confirm the address on file and send a Razorpay payment link if payment is collected online, or confirm cash-on-delivery.
- For pickup, confirm which store branch and give an estimated ready time.
- Log the new order in your CRM and update the refill-date field for the next cycle automatically.
Sample reply wording that keeps this step quick: 'Got it, reordering your usual course. Would you like it delivered home, or will you pick it up from the store this time?' Matching the customer's last choice by default cuts one extra question for most repeat customers.
The no-medical-advice rule
This is the most important guardrail for a pharmacy bot. If a customer asks anything beyond reordering, 'can I take this with paracetamol', 'what if I miss a dose', 'is this safe during pregnancy', the bot should immediately hand off rather than attempt an answer. Set up a keyword trigger or an AI agent instruction that recognises medical questions and routes them to live-chat handoff with the pharmacist, with a clear message like 'That's a question for our pharmacist, connecting you now.'
This rule should be tested explicitly with Preview / Try-it before launch. Type a handful of realistic medical questions into the test conversation and confirm every one of them hands off instead of getting an automated answer, since this is the one failure mode that carries real consequences.
Building it on Convo360
On Convo360, this entire loop can run as a Guided (no-AI) bot since the logic is simple and deterministic: refill date, reminder, reorder, delivery choice. Add an AI Reply node only as a fallback for questions outside the menu, with strict instructions to redirect clinical queries rather than answer them. Trigger the whole sequence from a Wait / Delay block set against the stored refill date, so no manual scheduling is needed once a customer's first order is logged. See /docs/compliance/ for guidance on health-related messaging.
Measuring the retention loop
Track reorder rate against reminders sent using Flow Logs and CRM order history: what share of customers who received a reminder reordered within a few days, and how that compares to customers who never got a reminder at all. Also watch how often the medical-question handoff fires. A rising rate might mean customers have questions your FAQ menu could answer safely, or it might simply reflect normal, expected clinical curiosity that always belongs with the pharmacist.
A steady reorder rate over a few months, without needing discounts or broadcast campaigns to prop it up, is the sign this loop is doing its job quietly in the background.
Step by step
- Record the refill date per customerSet a custom field with the expected refill date based on the medicine's course length.
- Create the reminder Utility templateDraft a factual reorder reminder with Reorder and Not Now buttons and submit for Meta approval.
- Trigger the reminder before the dateUse Wait/Delay to send the reminder three to five days ahead of the stored refill date.
- Branch to delivery or pickupOffer both options, defaulting to the customer's last choice, and confirm details.
- Route medical questions to the pharmacistSet up keyword or AI-instruction handoff so clinical questions never get an automated answer.
Example conversation
Industry guide: AI agents for Clinics & Hospitals — Appointment booking, reminders & 24/7 FAQs.
Set up refill reminders for your pharmacy
Start free in minutes — no code, no credit card. Bring your own AI keys and pay no per-message markup.
Frequently asked questions
Can the bot answer questions about dosage or side effects?
No. These should always be routed to the pharmacist through a live-chat handoff, with a clear message that a pharmacist is being connected. The bot's role stays limited to reminders, reordering and delivery logistics, never clinical advice of any kind.
How is the refill date calculated?
From the course length noted on the original prescription or order — for example, a 30-day supply ordered on a given date gets a refill reminder roughly three to five days before it runs out.
Does this need an AI agent?
Not for the core loop — it can run entirely as a Guided (no-AI) bot. An AI Reply is only useful as a fallback that redirects unexpected questions appropriately.
What if the customer's medication or dosage changes?
Update the custom field manually or through your pharmacy system whenever a prescription changes, since the reminder logic depends entirely on this field staying current, and a stale refill date can nudge a reorder for the wrong course length.
Is this compliant with WhatsApp's rules for health-related messages?
Refill reminders for an existing order are transactional and can use Utility templates, but avoid any medical claims or promotional health content, which fall under stricter review.
How do I know if the reminders are actually increasing reorders?
Compare reorder rate within a few days of a reminder against customers who didn't receive one, using Flow Logs and CRM order history, and track this over a few months rather than a single cycle.
Related reading
Available across India — see WhatsApp & AI calling automation by state and city.