Blog · By IVF Automation team · 24 Oct 2026
Your IVF front desk runs on WhatsApp. India's data rules now have a deadline for it.
Most Indian IVF clinics already confirm consultations, send scan timings and answer fee questions on WhatsApp, often from a receptionist's phone. Many are now adding chatbots and automated reminders. That is sensible: it saves staff time and fewer messages get missed.
But a fertility clinic's chat history is not ordinary customer data. On 13 November 2025 the Ministry of Electronics and IT notified the Digital Personal Data Protection Rules, 2025. Most duties under the DPDP Act, 2023 start eighteen months later, on 13 May 2027. That is the window to set up front-desk automation properly, instead of fixing it later. This guide covers what the rules and WhatsApp's own policies require, in plain operational terms. It is general information, not legal advice. Check your setup with your own legal adviser.
The timeline in one paragraph
According to the commencement notification (G.S.R. 843(E)), the Act's definitions and the provisions setting up the Data Protection Board came into force on 13 November 2025. The consent manager provisions follow after one year. The core duties come after eighteen months: notice, consent, security safeguards, breach reporting, the rights of patients as "Data Principals", and penalties. The matching parts of the Rules (Rules 3 and 5 to 16, among others) follow the same eighteen-month timeline. In practice, any automation you build today should already meet the May 2027 standard.
What WhatsApp itself requires
Before the Indian law even applies, Meta's rules shape what an automated clinic assistant can do.
- Opt-in first. Meta's opt-in guidance says businesses may message people only if they gave their mobile number and agreed to receive messages from the business. Record when and how each patient agreed.
- Templates outside the 24-hour window. Under the WhatsApp Business Messaging Policy, a business can reply freely within 24 hours of a patient's last message. Outside that window it can only send pre-approved message templates.
- Three template categories. Meta's pricing documentation sorts templates into marketing, utility and authentication. Its categorisation guidelines say a utility message must be non-promotional and tied to the user's own service. A reminder that mixes in an offer counts as marketing.
- A human escape route. The policy allows automated replies but requires "prompt, clear, and direct escalation paths", such as a transfer to a human agent, a phone number or email.
For an IVF clinic, that means keeping appointment reminders separate from promotional messages about packages or camps, and making sure a worried patient can always reach a person.
What the DPDP Rules add for automation
A notice patients can understand on its own. Rule 3 says the notice must stand on its own, use clear and plain language, and list the personal data collected and the specific purpose of each use. It must also explain how to withdraw consent, and withdrawing must be as easy as consenting. A line hidden in a registration form is unlikely to be enough. A short, plain notice sent before the bot collects anything, with a "STOP" or "talk to staff" option, is easier to defend.
Security safeguards, including for your vendor. Rule 6 sets minimum safeguards: measures such as encryption or masking, access controls, logs and monitoring to detect unauthorised access, and backups. It also requires keeping those logs and the related personal data for one year (unless another law says otherwise), and a contract clause making your data processor take reasonable safeguards. If a chatbot company, CRM or LIMS vendor handles patient chats for you, it is your data processor. You are responsible for what it does.
Breach reporting within 72 hours. Rule 7 requires a clinic that becomes aware of a personal data breach to tell each affected patient without delay. It must also inform the Data Protection Board without delay and send a detailed report within 72 hours, unless the Board allows longer. A leaked reminder spreadsheet or a shared front-desk phone that goes missing can both trigger this. Your automation vendor needs to be able to tell you quickly what was exposed.
Where fertility clinics carry extra risk
An automated reminder can reveal more than it seems. A message preview that says "Your embryo transfer is tomorrow" on a shared family phone discloses treatment. The ART Act and Rules already place confidentiality and record-keeping duties on clinics and banks. Front-desk automation should be designed to respect them, not work around them.
Practical design choices that reduce risk without adding staff work:
- Use neutral reminder wording ("Your appointment at [clinic] is at 10:30 tomorrow") and keep procedure names out of templates.
- Ask each patient, at registration, which number to use and whether a partner may receive messages.
- Move booking off personal phones onto the WhatsApp Business Platform or an approved provider, so access can be controlled and logged.
- Keep the bot to scheduling, directions, documents and fee FAQs. Send every clinical question to staff, and never let it interpret reports or suggest treatment.
- Store chats in one system with role-based access, not in screenshots forwarded between staff.
- Write a short breach playbook: who checks, who calls the vendor, who drafts patient messages, and how the 72-hour clock is tracked.
Seven questions for any WhatsApp or chatbot vendor
- Are you an official WhatsApp Business Platform provider, or does your tool automate a regular WhatsApp app?
- Where are chat logs and attachments stored, and who on your side can see them?
- Will you sign a data processing agreement that covers Rule 6 safeguards and one-year log retention?
- How fast will you tell us about a breach, and what information will you give us?
- Can patients withdraw consent from inside the chat, and does that sync to our records?
- If the bot uses an AI model, is patient text used to train it? Can we switch that off?
- Can we export every conversation and consent record if we leave?
Keep the answers on file with your other vendor paperwork. Then use our free DPDPA readiness check to see where your clinic stands before May 2027.
Sources
- MeitY, Digital Personal Data Protection Rules, 2025 (notified 13 Nov 2025; corrigendum 16 Dec 2025)
- DPDP Rules 2025, G.S.R. 846(E), full text
- G.S.R. 843(E), DPDP Act commencement notification, 13 Nov 2025
- DPDP Rules Rule 3 (notice), Rule 6 (security safeguards) and Rule 7 (breach intimation)
- WhatsApp Business Messaging Policy
- Meta for Developers, Get opt-in for WhatsApp
- Meta for Developers, WhatsApp Business Platform pricing and message categories and template categorisation
Your next step
Run the free DPDPA readiness check. It takes a few minutes and shows the gaps to close before May 2027. Vendors offering compliant WhatsApp or clinic software can claim a free listing in our directory.
For more on automation, see our witnessing guide and the workflow library.
General operational information only; not medical, clinical or legal advice. Product and platform names are mentioned for information and are not endorsements. See our disclaimer.