WhatsApp appointment booking for hospitals: how it works

WhatsApp appointment booking lets a patient message the hospital's number, choose a department, doctor and time from a menu, and receive a confirmation and a token, without a phone call or an app to install. It runs on the WhatsApp Business Platform, which means the hospital's messages follow Meta's template and pricing rules. This article explains the flow, those rules, and what it costs.

We have written before about why the app the patient already has open is a better front end than one you will ask them to install; that argument is in WhatsApp is the interface. This article is the practical companion for a hospital that wants to switch booking on.

How does the booking flow work?

1. The patient sends any message to the hospital's WhatsApp number, or taps a link or a QR code on the board outside the OPD.
2. The assistant replies with a menu: book an appointment, see my token, cancel, talk to the desk.
3. The patient picks a department, then a doctor, then a date. The assistant shows the free slots from the doctor's schedule in the HMIS.
4. The patient picks a slot and confirms their name and, for a first visit, their age and sex. Returning patients are recognised by their number.
5. The HMIS creates the appointment and a token, and the assistant sends a confirmation with the doctor, time, room and token number.
6. A reminder goes out before the visit. On the day, the patient can ask for the current token to decide when to leave home.
7. If anything falls outside the menu, one message hands the conversation to a person at the desk, with the history visible.

The same assistant, with the receptionist's login, can book from the desk by typing a name and a time, and in Healthixio a doctor can dictate a discharge summary to it as a voice note. The booking flow is the visible part of a module that does more.

What are the template and 24-hour window rules?

Meta does not let a business message anyone at any time. Two rules shape every design, and both are documented on the WhatsApp Business Platform pages.

• The customer service window. When a patient messages you, a 24-hour window opens in which you can reply with free-form messages. Outside that window, you can only send pre-approved templates. A reminder sent two days before a visit is a template; a reply to 'what is my token' is free-form.
• Templates are reviewed. Every template is submitted to Meta with placeholders for the patient's name, date and doctor, and reviewed before it can be used, which can take up to 24 hours. Templates are given a quality rating from customer feedback and can be paused if the rating falls. The message template documentation describes this.
• Opt-in. Patients should agree to receive messages, which is a tick box at registration, and should be able to stop them with one word.

What does it cost?

There are two costs: the software that runs the assistant, and the per-message charges that Meta levies. Since 1 July 2025, Meta prices template messages per message delivered, by category and by country. The categories and their treatment are in the table.

The actual rupee rates are on Meta's rate card for India, which changes from time to time, so we do not reproduce them here; look them up on the pricing page above. In practice a booking conversation is mostly service messages, which are free, plus one or two utility templates. What you should ask any vendor is who pays Meta's charges, whether they are shown to you message by message, and whether the software shows the cost of a campaign before the send button is pressed.

What should the hospital set up first?

• A WhatsApp Business account on a number the hospital controls, not a staff member's personal number.
• Doctor schedules in the HMIS that are true. The assistant can only offer slots that exist.
• Four or five templates submitted for review before go-live: confirmation, reminder, cancellation, report ready, and a general notice.
• The opt-in line on the registration form, and a stop keyword that works.
• A person at the desk who owns the handover queue during OPD hours, and an out-of-hours message that says when someone will reply.
• The waiting-area board and the token flow described in how to reduce OPD waiting time, so that the token the assistant sends means something when the patient arrives.

What else can the same channel do?

• Send the ABHA card after it is created at the desk.
• Deliver lab reports and discharge summaries as PDFs the moment they are signed.
• Send a payment link for an OPD bill or a deposit.
• Ask for feedback the day after a visit, with a one-tap rating.
• Remind a patient of a follow-up date set by the doctor.

The rule we follow in all of these is that the message is a copy and the HMIS is the record. Nothing is booked, billed or signed on WhatsApp; it is done in the system and confirmed on WhatsApp.

Frequently asked questions

Can we use our existing WhatsApp Business app for bookings?

The free WhatsApp Business app on a phone cannot connect to your HMIS or send automated replies at scale. Booking needs the WhatsApp Business Platform, which connects your software to the same number through Meta's API. The number can be moved from the app to the platform, so you can keep the number patients already know.

Will patients be annoyed by hospital messages?

Not if the messages are ones they asked for. A confirmation, a reminder and a report are welcome; a weekly promotion is not. Take opt-in at registration, keep marketing templates separate and rare, and make stopping messages a one-word reply. Meta's quality rating punishes templates that patients block, so restraint is also what keeps the number working.

What happens if the patient asks something the assistant cannot answer?

The assistant hands over to a person with one message, and the desk sees the whole conversation. This matters more than the cleverness of the menu. A patient asking whether a doctor treats a particular condition, or whether a report is ready, should reach a human within the same chat, not be told to call the hospital.