What is the WhatsApp Business API for hospitals?
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.
The short definition
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.
App versus API
| 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 |
How hospitals use it
- 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.
I cover the bigger picture of WhatsApp as the first point of contact in WhatsApp as the hospital front door.
The rules that matter
- 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.
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, 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.
Common mistakes
- 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.
The templates most hospitals need first
| 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, 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.
Measuring WhatsApp properly
| 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 |
Choosing a provider
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.
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.
Read my takes first in Google Search
