Picture a chemist shop in Bhopal sending 1,200 SMS reminders every month — refills, expiry alerts, payment follow-ups — and paying ₹1,800 a month for the SMS gateway. At the end of the year the owner has spent ₹21,600 and cannot say how many of those messages were read. SMS gives delivery reports, not read receipts; some numbers sit on the DND registry, promotional filters catch others, and the rest land in an inbox customers check once a week.
Every patient that reminder failed to reach is refill revenue that may walk out the door. And that is before we count the legal exposure the owner did not even know he had.
If you are currently running an SMS pharmacy reminder program, or debating whether to switch to WhatsApp, the next five minutes will cost you nothing and may save you considerably more than that ₹21,600.
---
The DND Legal Trap Most Pharmacy Owners Walk Into Blindly
Picture this: a customer in your store on a Tuesday in Chennai fills a prescription for a Schedule H medicine. You note the mobile number, add them to your reminder list, and two weeks later your SMS blast goes out. What you may not know is that the number is registered on the TRAI DND (Do Not Disturb) registry.
Sending a commercial or promotional SMS to a DND-registered number violates TRAI's Telecom Commercial Communications Customer Preference Regulations, and repeated complaints can get your sender ID blocked — meaning every message you send, including transactional ones, stops going through. More relevantly, the Digital Personal Data Protection Act 2023 (DPDPA 2023) asks for a lawful basis — for reminders, in practice, the patient's specific consent, which they can withdraw — before you use their number this way. A patient who filled a prescription at your counter has not automatically given that consent.
The practical cost here is not just the fine risk. It is the operational overhead of maintaining a clean, consent-documented list, scrubbing it against the DND registry before every campaign, and keeping proof of consent for audit. Many retail pharmacies in India do none of this today.
---
What You Can Actually Measure With Each Channel
SMS tells you a message was delivered; it cannot tell you it was read. A refill reminder sent as promotional SMS is also filtered for numbers on the DND registry. WhatsApp shows you when a message is delivered and read, and it is where many Indian customers already talk to their pharmacy.
The cost structure is also different:
- Bulk SMS promotional: a per-message rate from your SMS provider, plus template registration with your telecom operator
- WhatsApp Business API: a per-message rate set by Meta for each template category, paid through a provider
- WhatsApp Business App or your own WhatsApp: no per-message cost, but each message is sent by hand, with no API automation
Rates change, so take current rate cards from your providers. Then compare the channels on cost per message actually read, not cost per message sent — the refill conversion that comes from a read message is the only number that actually pays the bill.
---
The Hidden Schedule H Register Problem Your Reminder Channel Makes Worse
Here is a compliance angle most pharmacy software vendors do not mention in the same breath as reminders: every time you send a refill reminder, you are implicitly acknowledging that a Schedule H or Schedule H1 medicine was previously dispensed. Under Rule 65 of the Drugs and Cosmetics Rules, every Schedule H and H1 sale is recorded with the drug, batch number, quantity, and the prescriber's and patient's details, and Schedule H1 supplies also go into a separate register kept for three years under Rule 65(3)(h). A falsified or incomplete register can put your licence at risk.
Now consider what happens when a drug inspector audits your pharmacy and cross-references your WhatsApp or SMS reminder logs with your dispensing register. If a refill reminder went out for a Schedule H1 medicine and that dispensing entry is incomplete or missing from your register, you have handed the inspector a clean paper trail that connects the gap.
This is not an argument against sending reminders. It is an argument for reminders being generated from the same system that maintains your register — so that every outbound message is traceable to a complete, timestamped dispensing record that will survive a three-year audit.
---
What Operations Look Like When This Is Running Correctly
Here is what the before-and-after can look like once the reminder workflow is fixed:
| Situation | Before | After |
|---|
| Refill reminders | Manual SMS blast, DND-unscreened, promotional category | WhatsApp message prepared from the dispensing record, sent to patients who agreed to it |
| Read status | Unknown | Delivered and read ticks visible |
| Register linkage | Separate spreadsheet, updated manually | Reminder drawn from the same bills that feed the H1 log |
| Monthly reminder cost | Per-SMS gateway charges | Per-message API charges, or none if sent from your own WhatsApp |
| DPDPA consent record | None | Consent asked for and noted at the counter |
| Staff time per week | Hours building lists and writing messages | Reviewing a short list of patients who are due |
The number that matters most in that table is not the read rate. It is the staff time. Picture a pharmacist in Thane spending three hours every Sunday preparing Monday's SMS blast — three hours on a task the system can prepare in a moment.
---
How Nesayo Handles This Without Thinking About It
The Refill Radar agent — included from Nesayo's Essential plan — reads your own dispensing history and flags patients who are likely due for a refill once their purchases show a regular pattern, or a days-supply has been recorded. When it lacks the evidence, it stays quiet rather than guessing.
No reminder leaves Nesayo on its own. When a patient is due, Nesayo prepares the message and opens WhatsApp on the pharmacy's own phone with the text ready, and staff tap send — from the number your patients already know, not a bulk gateway. Ask for the patient's consent at the counter before you start, and honour it when they say stop.
Because Nesayo's billing and Schedule H1 log are the same system — not two separate modules — the reminder draws on the same bills that feed the H1 log. Schedule H1 sales are logged at billing: date, medicine, batch, quantity and bill number, with the patient and prescriber names entered on the bill. Nesayo does not record the prescriber's address yet, so the pharmacist adds it to complete the register.
Billing on Nesayo is free, permanently. Refill Radar comes with the Essential plan at ₹249 a month, and all five AI agents (Morning Briefing, Expiry Guard, Refill Radar, Stock Sense, Payment Advisor) with the Full plan at ₹549 per month, as of October 2026 (pricing listed at nesayo.com/pricing). Do the arithmetic for your own counter: if 80 refill reminders a month bring back 48 patients at a ₹400 average basket, that is ₹19,200 a month against the plan price.
---
The Choice in Front of You Right Now
Every month you continue sending unscreened SMS reminders, you are paying for a channel whose reach you cannot measure, running DND exposure you may not have priced into your risk model, and disconnecting your reminder workflow from the register that a drug inspector will eventually ask to see. Switching to a WhatsApp reminder workflow that is linked to your billing and compliance system is not a large project — it is a configuration decision that takes an afternoon. The pharmacies that delay it are not saving money. They are deferring the cost into a less convenient moment.
Spend 10 minutes at nesayo.com/demo — a sample pharmacy is pre-loaded, no signup required — to see the billing and patient history Refill Radar reads from. Then count last month's chronic patients who did not come back. See the number, then decide.
---
FAQ
Will I lose my existing billing data if I migrate to Nesayo?
No. Nesayo imports your stock from a CSV, Excel or text export (or a photo of a stock list), and the Nesayo team moves your current software's data across for you, free (file and photo imports run during your free first month of Full, or on a paid plan). For pharmacies on legacy desktop software, the path is an export from the old system and an import into Nesayo, and your old software keeps its history. Your data does not disappear; it moves.
What if my staff has never used a pharmacy app and we lose internet mid-day?
Nesayo runs as a Progressive Web App (PWA), which means billing continues working offline and syncs when connectivity is restored. On the learning curve — billing is a search box and a bill, and on the paid plans voice billing in Hindi or English (beta) means staff do not need to type drug names or navigate dense menus. Let new staff practise on the demo pharmacy first.
What is the catch with free billing — and can I really trust an AI system for compliance-linked reminders?
The billing is free permanently because Nesayo's revenue comes from the paid plans (as of October 2026, per nesayo.com/pricing: Essential at ₹249/mo, Full at ₹549/mo, Chain at ₹2,999/month + ₹999/month per additional pharmacy). There is no bait-and-switch on the billing feature. On the compliance question: Schedule H1 logging at billing is a rule-based function drawn from your own bills — it does not make clinical judgments. Refill Radar identifies who may be due for a refill from your own dispensing history, and no reminder goes out on its own: the pharmacist sends each one from the pharmacy's own WhatsApp. The human remains in the loop for every outbound communication.