What is the WhatsApp Business API for hospitals?
Reviewed on by Gaurav Phogat. Statistics checked against their original sources on the same date.
Updated 24 October 2026: merged in our guide on WhatsApp as the hospital front door and added number strategy, conversation design, handoff, safety rules and a rollout order.
See every healthcare digital growth guide in one place.
The WhatsApp Business API, now part of Meta’s WhatsApp Business Platform, is the version of WhatsApp built for organisations. It lets a hospital connect WhatsApp to its CRM and contact centre, run a shared inbox across many agents, send approved template messages such as appointment reminders, and automate routine replies. The free WhatsApp Business app on a phone cannot do this at hospital scale.
What is the WhatsApp Business API for hospitals?
The WhatsApp Business API is an interface that connects a verified business phone number to software rather than to a single handset. Messages flow into a system the hospital controls, where they can be routed, logged, answered by teams and triggered by events such as a booking or a discharge.
Should a hospital use the WhatsApp Business app or the API?
A single small clinic can start with the free WhatsApp Business app on one phone, but a hospital needs the API. The API connects a verified number to software, so many agents can share one inbox, conversations are logged in the CRM, templates trigger confirmations and reminders automatically, and data stays with the hospital rather than on staff phones.
| WhatsApp Business app | WhatsApp Business API | |
|---|---|---|
| Who uses it | One person or a small clinic on a phone | Teams, contact centres, multi-unit groups |
| Inbox | On the device, limited linked devices | Shared inbox inside a CRM or support tool |
| Integration | None | CRM, hospital information system, booking engine |
| Outbound messages | Manual | Approved templates, sent individually or by trigger |
| Automation | Basic away and greeting messages | Chatbots, routing, reminders and follow-up flows |
| Records | Stay on the phone | Logged against the patient record |
| Cost | Free | Charged by Meta per template message by category, plus the software provider’s fees |
Why running WhatsApp on staff phones is a problem
Walk through the OPD of almost any Indian hospital and WhatsApp is already doing front desk work. The coordinator sends a report to a family from her own phone. A doctor’s assistant confirms the evening slot from a personal number. The billing desk shares an estimate as a photo of a printout. None of it is designed, none of it is recorded, and all of it happens because patients prefer it to a call. Patients have settled whether a hospital should use WhatsApp; the real question is whether it runs WhatsApp as a front door, with the same care it gives the reception area, or keeps letting it happen in pockets.
The informal version feels efficient, but the costs show up elsewhere. Patient data sits on personal devices, and when a coordinator leaves, the conversations, reports and phone numbers leave with her. There is no record to review when a complaint arrives. Under the DPDP regime the hospital is responsible for personal data processed on its behalf, and a report sent from a personal phone is very hard to defend. Commercially, enquiries on individual phones never reach the CRM, so a unit can be receiving good demand through WhatsApp and look weak on every dashboard. I would rather have that demand visible, even if the first view is messy.
How hospitals use it
Hospitals use the WhatsApp Business API for enquiry capture from the website, ads and Google Business Profile; appointment confirmations and reminders; pre-visit directions and preparation instructions; secure links to reports and bills; post-visit feedback and follow-up reminders; and as the default channel for many international patient enquiries, with every conversation logged centrally.
- Enquiry capture: click-to-WhatsApp from the website, ads and Google Business Profile, with every chat creating a CRM record and source.
- Appointment confirmations and reminders: utility templates triggered by the booking system, one of the most effective ways to cut no-shows.
- Pre-visit information: directions, what to bring, preparation instructions written by clinicians.
- Reports and bills: secure links rather than attachments, where the systems support it.
- Post-visit follow-up: feedback requests and reminders for follow-up consultations.
- International patients: the default channel for many overseas enquiries; see WhatsApp for international patient enquiries.
Further down, I cover the bigger picture: WhatsApp as the hospital’s front door, from the menu to the handoff to a person.
The rules that matter
Five rules matter: WhatsApp’s business policy requires recorded opt-in before messaging; messages outside an active conversation must use pre-approved templates; the hospital can reply freely within the service window after a patient writes; India’s DPDP Act requires purpose-specific consent and easy withdrawal; and bots may route and inform but must never diagnose.
- Opt-in: WhatsApp’s own business policy requires permission before a business messages someone. Record when and how each patient opted in.
- Templates: messages sent outside an active conversation must use pre-approved templates, categorised as marketing, utility or authentication.
- Service window: when a patient messages you, the hospital can reply freely for a limited window; after that, only templates.
- DPDP Act: consent must be specific to the purpose, and patients must be able to withdraw it. Health details in chats need the same protection as any patient record.
- Clinical boundaries: bots should route and inform, never diagnose. Anything clinical goes to a qualified person.
For the consent side, see the WhatsApp consent flow template and DPDP consent and hospital marketing.
Written rules for emergencies, reports and marketing
A few rules should be written down, approved by the medical director and legal, and built into the tooling rather than left to judgement.
- Emergencies: any message that looks urgent gets an immediate automated reply with the emergency number and ambulance route, and is flagged to a supervisor. A patient should never wait in a queue for that.
- Clinical questions: agents book a consultation, arrange a call-back from a clinical team where the hospital offers one, or direct to emergency care. Doctors who want to message their own patients do it from an approved hospital account, with the conversation recorded.
- Reports and documents: verify identity before release, prefer a secure link with a one-time code to an attachment, and never send a report to a number not registered to that patient without a verification step. Record every release against the patient record.
- Marketing: promotional messages go only to patients who opted in for them, at a sensible frequency, with an easy opt-out. Blasting health check offers to everyone who ever enquired is the fastest way to get the number’s quality rating downgraded and messaging limits reduced.
How to set it up
Choose a Meta business solution provider or a CRM with native WhatsApp support, verify the business and register a dedicated number per brand or unit. Write and submit templates for confirmations, reminders and follow-up, connect the inbox to the CRM, define routing and response-time targets, train agents, and only then automate routine, non-clinical questions.
- Choose a Meta business solution provider or a CRM with native WhatsApp support.
- Verify the business and register a dedicated number per brand or unit, as your structure requires.
- Write and submit templates for confirmations, reminders and follow-up.
- Connect it to the CRM so every conversation is logged against a patient record with its source.
- Define routing: which unit, which department, which language, and response-time targets.
- Train agents, then add automation only for routine, non-clinical questions.
One number or many
Multi-unit groups choose between a single group number and a number per unit. A single number is easier to publicise, builds one relationship with the patient and keeps the quality rating in one place. Per-unit numbers feel local and let each unit own its queue, but they fragment the patient’s history and multiply the governance work.
My preference is one group number with routing: the first question establishes which unit or city the patient is asking about, and the conversation lands in that unit’s queue. Local teams keep ownership, the patient keeps one thread with the hospital, and the group sees the whole picture. Print that number everywhere the old personal numbers used to appear, and ask doctors and coordinators to redirect patients to it.
Entry points that carry their source
Patients arrive from a click-to-chat button on the website, the doctor page, the Google Business Profile, a QR code at reception or in the OPD waiting area, printed prescriptions and campaign ads. Give each entry point a pre-filled first message or a tag, so the conversation opens already knowing where the patient came from and roughly what they want. That saves an exchange of messages and makes attribution possible later.
Common mistakes
The most common mistakes are running WhatsApp on staff phones so conversations and data leave with employees, sending promotional blasts to people who never opted in, launching a chatbot before the human inbox is answered reliably, and failing to connect WhatsApp to the CRM, which means enquiries never reach attribution or follow-up reporting.
- Running WhatsApp on staff phones, so conversations and data leave with the employee.
- Sending promotional blasts to people who never opted in.
- Launching a chatbot before the human inbox is answered reliably.
- Not connecting WhatsApp to the CRM, so enquiries never reach attribution.
Designing the conversation
Most hospital WhatsApp journeys fail in the first few messages: a wall of text with a numbered menu of a dozen options, or a chatbot that answers everything with “please call our helpline”. The better pattern is a short button menu for the intents that make up most of the traffic, and a clear route to a person for everything else. For a typical unit the menu is small:
- Book or change an appointment
- Get my reports
- Bills, estimates and insurance
- Directions and timings
- Talk to someone
Booking should open with a specialty or doctor choice, show available slots where the scheduling system can expose them, and confirm with a template the patient can find later. Directions and timings should answer instantly with a map link. Bills and insurance nearly always need a person, so route them quickly rather than pretending a bot can explain a TPA query.
Free text deserves care. Patients will type “my mother has fever since three days, which doctor” in a mix of Hindi and English. An AI layer can classify that intent and route it well, but it should not answer the clinical part. I have written about where AI belongs in the patient journey, and on WhatsApp the line is the same: understand the request, route it, book it, never advise.
The templates most hospitals need first
Most hospitals first need utility templates for an out-of-hours enquiry acknowledgement, appointment confirmation, reminder, reschedule prompt, pre-visit instructions, report-ready notice and follow-up reminder. Updates about health camps or packages are marketing messages that need separate opt-in. Keep every template short, factual and free of claims, and use marketing templates sparingly.
| Template | Category | When it is sent |
|---|---|---|
| Enquiry acknowledgement with timings | Utility | Immediately after a patient messages outside staffed hours |
| Appointment confirmation | Utility | When a booking is made, with date, time, doctor and location |
| Appointment reminder | Utility | The day before and a few hours before the visit |
| Reschedule prompt | Utility | When a patient misses an appointment |
| Pre-visit instructions | Utility | For procedures that need preparation, written by clinicians |
| Report ready notice | Utility | When a report is available through a secure link |
| Follow-up reminder | Utility | When a follow-up consultation is due |
| Health camp or package update | Marketing | Only to patients who opted in to marketing |
Keep templates short, factual and free of claims. Marketing templates need separate opt-in and should be used sparingly.
How to staff the inbox
Treat WhatsApp as a contact-centre queue with the same response targets as calls. Route by unit and language from the first message, give agents approved answers for timings, doctors, packages, directions and insurance, escalate anything clinical to a nurse or doctor line, and review response times and unresolved chats daily by unit and shift.
- Treat WhatsApp as a contact-centre queue with the same response targets as calls.
- Route by unit and language from the first message, using a short menu or keywords.
- Give agents approved answers for common questions: timings, doctors, packages, directions, insurance.
- Escalate anything clinical to a nurse or doctor line, and never let agents give medical advice.
- Review response times and unresolved chats daily, by unit and shift.
The handoff to a person
The handoff is where the channel earns or loses trust. A patient who chooses “talk to someone” and waits in silence will call instead, and will remember the silence. Agents should see the patient’s history (previous visits, open appointments, earlier conversations) before they type, which needs the CRM integration. The automated reply outside staffed hours should say when a person will reply and what to do if the matter is urgent.
Distress, complaints, billing disputes and anything clinical should reach a person early, the same judgement I described for voice in when automation should not answer the phone. A bot that measures success by how many conversations it kept away from staff looks good on a slide and poorly with patients; see containment versus resolution.
Language, tone and the written voice
Phone scripts rarely translate to chat. On the phone, a warm voice covers for a clumsy script; in writing, every word sits on the screen and gets forwarded to the family group. Give agents a short written style guide: greet by name, answer the question first, keep messages short, confirm what will happen next and when, and never paste a paragraph of policy.
Patients will write in Hindi, Tamil, Bengali or a mix typed in Roman script. Offer the menu and templates in the main languages of each unit’s catchment, chosen by the patient at the start, and route regional language conversations to agents who can read and reply in them. Keep the tone consistent with the brand, not the individual agent: emojis, slang and over-familiar sign-offs look friendly in one chat and careless in a complaint review. Supervisors should review a sample of conversations every week, the way they review call recordings.
Measuring WhatsApp properly
Measure WhatsApp by outcomes rather than message volume: first response time, the share of chats that become bookings, how many booked patients arrive after reminders, treated patients by entry point and the opt-out rate. Message counts and read receipts show activity, not whether the channel is helping patients reach care or adding revenue.
| Metric | Why it matters |
|---|---|
| First response time | The single biggest driver of conversion on chat |
| Chats to bookings | Shows whether conversations turn into appointments |
| Booked to arrived after reminders | Shows the effect of confirmation and reminder templates |
| Treated patients by entry point | Shows which channels feed WhatsApp enquiries that become patients |
| Opt-outs | An early warning of over-messaging |
Two more measures belong in a unit head’s review: how many conversations ended unresolved or moved to a phone call, and how much of the informal traffic on personal phones has moved to the official number. Read every measure by unit and separate staffed hours from out-of-hours. One unit with slow human replies drags down the group number’s reputation for everyone, and its head should see that in their own review.
What to switch on first
Resist launching every use case at once. A front door that does three things well beats one that does ten things badly. Start with the official account, one number with unit routing and a staffed inbox during OPD hours. Add appointment confirmations and reminders as utility templates, because they are low risk, useful to every patient and quick to show value. Put the new number on signage, doctor pages, prescriptions and the Google profile, and make moving patients off personal phones the first operational rule.
Once the handoff works and response times are steady, add report delivery with proper verification, then booking inside the chat. Marketing messages come last, and only to patients who opted in. At each step, check the numbers that matter: appointments and completed visits, human response time and opt-outs.
Choosing a provider
Judge WhatsApp providers on CRM integration, shared inbox quality, template management, routing and reporting, data residency and consent records, and the quality of support available in India. Most hospitals connect through a Meta business solution provider or a CRM with native WhatsApp, and should weight integration and consent handling above messaging price.
Most hospitals connect through a Meta business solution provider or a CRM with native WhatsApp. Judge providers on CRM integration, shared inbox quality, template management, routing and reporting, data residency and consent records, and support in India. The CRM vendor scorecard includes WhatsApp as a weighted criterion.
The full guide: Hospital digital marketing in India: a channel-by-channel guide.
Key statistics, with sources
WhatsApp’s reach makes it the natural front door for Indian hospitals. Almost all online adults in India chat with a business every week, mobile and broadband subscriptions now exceed a billion, and more than half of internet users live in rural India, where messaging is often easier than calling or filling in a web form.
- 91% of online adults in India chat with a business every week, according to a 2025 Kantar study cited by Meta. Source: Meta, citing Kantar 2025, May 2026.
- India had 1,306.27 million wireless subscribers and 1,094.48 million broadband subscribers at the end of July 2026, according to TRAI. Source: TRAI, Press Release No. 116/2026, August 2026.
- Rural India accounted for 55% of the country’s active internet users in 2024, or 488 million people, according to IAMAI and Kantar. Source: IAMAI and Kantar, Internet in India 2024, reported by MediaNama, January 2025.
Further reading from primary sources
- WhatsApp Business Messaging Policy: opt-in rules for messaging people.
- DPDP Rules, 2025 (Press Information Bureau): India’s notified data protection rules and timeline.
Questions people ask
It is the organisational version of WhatsApp, part of Meta’s WhatsApp Business Platform, that connects a business number to software such as a CRM or contact-centre tool.
The app runs on a phone for small businesses. The API supports shared team inboxes, integrations, approved templates and automation at scale.
To answer enquiries as a team, log every conversation against a patient record, and send reminders and follow-ups reliably.
Meta charges for template messages by category, and software providers charge their own fees. Check current rates with Meta or your provider.
Yes. WhatsApp’s business policy requires permission, and the DPDP Act requires purpose-specific consent that patients can withdraw.
Pre-approved message formats used to contact someone outside an active conversation, such as appointment reminders.
Yes, for routine questions such as timings, directions and booking, with instant handover to a person and no clinical advice.
Many do, ideally through secure links rather than attachments, with patient consent and proper data protection.
It depends on the brand structure. Many groups use one number with routing by unit; others use unit numbers for local recognition.
Confirmation and reminder templates sent at the right times, with an easy way to reschedule, reduce missed appointments.
The channel can be used compliantly if consent, purpose limitation, security and withdrawal are handled properly by the hospital.
Connect WhatsApp to the CRM and use separate entry points or tagged links per channel so each chat carries its source.
The contact centre usually runs the inbox, with the growth or digital team owning templates, automation and reporting.
Because the hospital cannot see, record or protect what happens there. Patient data sits on personal devices, conversations leave with staff, complaints cannot be reviewed and enquiries never reach the CRM. The official channel keeps the responsiveness patients like while fixing those gaps.
A basic launch with the official account, a number with unit routing, a staffed inbox and appointment reminders can be done in a matter of weeks if the CRM and appointment system are accessible. Report delivery and in-chat booking take longer because they need deeper integration and sign-off. Plan in phases and let each phase prove itself.
Doctors who want to stay in touch with their patients should do it through an approved hospital account or through the central team, so conversations are recorded and protected. Start by redirecting new patients to the official number and giving doctors a quick way to ask the team to send confirmations or follow-up reminders.
Read my takes first in Google Search
