AI & AutomationWhatsApp Business APIWhatsApp TemplatesPatient MessagingOpt-in ConsentHealthcare Software

WhatsApp 24-hour window, templates and opt-in for clinics

When a clinic can message patients on WhatsApp: the 24-hour window, approved templates, recording consent and handling STOP. Meta's rules as of Nov 2026.

Maulik Joshi

Maulik Joshi

Full-Stack Developer

13 min read
Tip

If your clinic wants to message patients on WhatsApp, this post explains the rules that decide what you may send and when. WhatsApp can refuse a message sent in the wrong form or at the wrong time, so the rules matter to anyone setting up reminders or booking replies. After reading, you will be able to check a planned message against those rules, record patient consent properly and handle a patient who asks you to stop.

WhatsApp only lets a clinic send a free-form message, meaning ordinary text or files you write yourself, while a 24-hour timer is running. The timer, called the 24-hour window, starts when a patient messages or calls your clinic's WhatsApp number and restarts each time they do it again. After it ends, only a template can go out, which is a message with fixed wording that Meta (the company behind WhatsApp) has approved in advance, and only to a patient who has opted in, meaning agreed to receive your messages. Your own record of the patient's last message decides which kind of message you send, so store it and check it before every send.

This post covers how the rules work in practice: the window, templates, opt-in records (your proof that a patient agreed), what to do when a patient says STOP, and what to record in your logs. What Meta's terms say about health information, what belongs in a clinic message, how booking works and what the no-show evidence shows are in my guide to WhatsApp for clinics, and I do not repeat them here. I checked every rule below against Meta's developer documentation and policy pages on November 22, 2026. It is not legal advice, and your clinic's compliance adviser decides what you may send and to whom.

#How the window opens, resets and closes

Meta's documentation says that when a WhatsApp user messages you or calls you, a 24-hour timer called a customer service window starts, and that another message or call from the user before the timer ends resets it to 24 hours. When the window closes, you can only send pre-approved template messages. Meta describes only the patient's message or call as the start, and your own replies do not extend it.

Inside the window, the free-form types Meta lists are text, images, audio, video, documents, stickers, contacts, locations, reactions and the interactive formats: reply buttons, lists, call-to-action URL buttons, location requests, call buttons and Flows. None of them needs pre-approval. Meta's policy also allows automation inside the window, as long as there is a prompt, clear way to reach a person.

Build the check on your side from a stored timestamp. Save the time of every inbound message from the webhook (and of inbound calls, if your integration receives them), work out last inbound plus 24 hours, and compare that with the current time before any free-form send. If your clock and Meta's disagree, Meta wins. A free-form send after the window has closed fails with error 131047, which Meta describes as more than 24 hours having passed since the recipient last replied to the sender number. Treat that error as the cue to fall back to a template, or to hand the task to a person.

#What you can send in each situation

Seven situations cover most of what a clinic sends. The rules and charges in the table are Meta's as of November 22, 2026. The opt-in advice in the first row and the staff-task fallback in the fifth are mine.

SituationWhat you may sendWhat it needs
Patient messaged or called in the last 24 hoursAny free-form service message: text, documents, reply buttons, lists, FlowsNo template. Meta's page says you can only message users who have opted in, and it does not say a patient's first message counts as opt-in, so I would record one anyway. Delivered service messages count toward 1,000 free per phone number each month, then are charged.
Window open, and you want to send a templateAn approved template of any categoryCharged by category. Since October 1, 2026, a utility template sent inside an open window is charged too.
Window closed, appointment reminderAn approved utility templateOpt-in on record, template status APPROVED, wording that is non-promotional and specific to the patient. Charged per delivered message by country. Sending it does not start a window; only a reply from the patient does.
Window closed, recall or offerAn approved marketing templateMeta recommends a separate opt-in for each category. Marketing templates are not currently delivered to US phone numbers (see below). A patient who has stopped marketing messages returns error 131050.
Window closed, no approved template fitsNothing on WhatsAppA task for staff to phone the patient, or to use another channel the patient agreed to.
Patient has asked you to stopNothing further, apart from one short confirmation if the request opened a windowMeta's policy says to respect opt-out requests made on or off WhatsApp. Record the time and cancel queued sends.
Template paused or disabledNothing that uses that templateError 132015 while paused and 132016 once disabled. Edit and resubmit it, or create a new one.

For US recall campaigns, the source is Meta's page on per-user marketing limits. It says WhatsApp does not currently deliver marketing template messages to WhatsApp users with United States phone numbers, and that trying to send one returns an error. The page states no end date, so check it again before you plan anything around it.

#A patient's day, in order

This sequence shows the mechanics. It is an illustration with an invented patient, not a client result, and the times are examples. Assume the patient ticked a WhatsApp reminders box on the clinic's booking form last week and your system stored it.

  1. Monday 10:00. The patient writes, "Can I come Thursday morning?" The window opens and runs until Tuesday 10:00. Your system stores 10:00 as the last inbound time.
  2. Monday 10:02. Your system replies with three free slots as a list message. It is a free-form service message, so no template is needed.
  3. Monday 10:06. The patient picks Thursday 10:30. That message restarts the timer, so the window now runs until Tuesday 10:06. Your system writes the booking to the calendar first, then sends the confirmation at 10:07, also free-form.
  4. Tuesday 10:06. The window closes. Nothing is sent and nothing needs to be; your stored timestamp is how you know.
  5. Wednesday 10:30. The 24-hour reminder is due. The window is closed, so the message must be an approved utility template with the date, time and place filled in. Your system checks the opt-in record and that the appointment is still booked, then sends it. The patient has no open window yet, because sending a template does not start one.
  6. Wednesday 10:41. The patient types, "Can I do 11 instead?" A new window opens and runs until Thursday 10:41, and each further message from the patient restarts it. Your system answers free-form with two slots from the calendar, the patient picks one, and the calendar is updated before the confirmation goes out.
  7. Thursday 08:00. A same-day reminder is due. The patient's last message on Wednesday keeps the window open, so a free-form reminder would be allowed. I would still send the template, so the wording is one Meta has reviewed and every patient gets the same text.
  8. Thursday 14:00. After the visit the patient writes "stop". That message opens a window, so your system can send one short confirmation that reminders have ended. It records the opt-out with its time and cancels anything still queued. Meta does not require the confirmation; it is my suggestion.

I used typed replies on purpose. A quick-reply button on a template arrives in the messages webhook as a message of type button, but the Meta pages I read do not say whether a tap starts a window, so test that in your own account before you design around it.

#Template categories and what gets a template rejected

Every template is assigned one category: authentication, marketing or utility. Authentication templates carry one-time passcodes and nothing else. A utility template must be non-promotional and either specific to or requested by the user, or essential to them. Marketing is the widest category, and Meta puts templates with mixed or unclear content there as well.

Meta's guides do not list appointment reminders as an example. Its utility template page uses a restaurant reservation confirmation as the only sample. A plain reminder with the date, time, place and a way to confirm or cancel fits the written utility test, but Meta's review decides, and one promotional line changes the answer. A reminder that also mentions a flu-shot offer is mixed content, which is marketing.

If Meta moves a utility template to marketing, the template stays APPROVED and keeps sending, billed as marketing. Accounts that Meta has already warned for misusing the utility category get no advance notice, and Meta's enforcement steps include moving every approved utility template on the account to marketing for 7 days, or 30 for repeat violations.

Review is automatic when you create or edit a template and can take up to 24 hours. These rejection reasons from Meta's review page are the ones a clinic template is most likely to hit:

  • A variable at the start or the end of the body. Meta does not allow dangling parameters, so finish the message with words, not {{4}}.
  • Variables that are not sequential, have mismatched braces, or contain characters such as #, $ or %.
  • Too many variables for the length of the message.
  • Requests for sensitive identifiers, such as full payment card numbers, financial account numbers or national ID numbers. Meta says asking for partial identifiers, such as the last four digits of a Social Security number, is fine.
  • A body and footer identical to an existing template, which is easy to do when each location gets its own copy of the same reminder.
  • Missing sample values. Every variable needs an example when you create the template, and an appeal must include a sample too.

A body that clears those rules looks like the one below. It is an illustration. I have not submitted it, so I cannot say how Meta would categorize it.

appointment_reminder_24h (illustrative, not submitted)
text
1Hello {{1}}, this is a reminder of your appointment at {{2}} on {{3}} at {{4}}. Use the buttons below to confirm it, ask to reschedule, or stop reminders.
2
3Buttons (quick reply): Confirm | Reschedule | Stop reminders

A rejected template can be edited and resubmitted, or appealed, and Meta says it decides appeals within 24 hours.

#How template quality ratings and pauses work

Every template has a quality rating built from usage, patient feedback and engagement. A new template starts as unknown. After that it shows green (high), yellow (medium) or red (low). Yellow means negative feedback from multiple users or low read rates. Red means the template still sends but is in danger of being paused or disabled soon.

A paused template cannot be sent. The first pause lasts 3 hours, the second 6 hours, and the third disables the template. Meta notifies you through a message_template_status_update webhook, rejects sends while the template is paused without billing them, and tells you to halt automated sends that rely on it. The template unpauses on its own after the period, or you can unpause it through the API or in WhatsApp Manager. Editing and resubmitting it sets its status to In Review.

I would treat that webhook as an alert and design the fallback before it fires. A reminder batch due at 10:30 that meets a 3-hour pause that began at 10:00 needs somewhere to go, and a staff task list is the simplest place.

One inference for US clinics, which I have not seen Meta state directly: a reminder that Meta recategorizes as marketing would then fall under the US marketing rule above. Watch category changes on your templates and have the staff-task fallback ready.

#What an opt-in must capture and where to keep it

Meta's opt-in page asks for three things. You need the person's mobile number or username and their permission, confirming they want messages from a particular business. The opt-in must state clearly that the person is opting in and name the business. And it must comply with applicable law. Meta lets you choose the method, and lists SMS, a website, an interactive voice response flow on the phone, and in person or on paper with a signed document. It also recommends that the opt-in cover the types of message you will send, and asks for a separate opt-in for each category, which lowers the chance that people block you.

Meta's page says nothing about what to keep, so the record is yours to design. I would store one row per opt-in or opt-out event and never overwrite the last one. The example below uses synthetic data.

opt-in event (illustrative record, synthetic data)
json
1{
2 "patient_id": "pt_000123",
3 "whatsapp_phone": "+12125550123",
4 "whatsapp_user_id": "bsuid_example_001",
5 "category": "appointment_reminders",
6 "event": "opt_in",
7 "captured_at": "2026-11-16T09:14:00-05:00",
8 "channel": "website_booking_form",
9 "wording_shown": "Send me appointment reminders on WhatsApp from Example Clinic. I can tap Stop reminders at any time.",
10 "wording_version": "2026-11-v1",
11 "captured_by": "form",
12 "evidence_ref": "form_submission_8841"
13}

Keep it in your own database, linked to the patient record, and not only in a chat tool or your messaging provider's dashboard. For a paper form, store a scan or a form ID in evidence_ref. How long the records must be kept is a question for your compliance adviser.

Identifiers need a second look in 2026. Meta says it is rolling out WhatsApp usernames gradually this year. When a user adopts one, Meta says their phone number is not included in webhooks unless certain conditions are met, one of which is recent contact with that number (within the last 30 days). Meta tells you to use the business-scoped user ID (BSUID) in webhooks to identify the user. An opt-in recorded against a phone number on a paper form therefore has to be linked to the BSUID once the patient first writes to you, or a later webhook will match no one.

#How to handle STOP and other opt-outs

Meta does not require a keyword. Its policy says you must respect all requests, on or off WhatsApp, to block, discontinue or otherwise opt out, and that honoring a request includes removing the person from your contacts list. I read that as covering "stop" typed in any language, a Stop reminders button, a phone call to the front desk and a word at the counter. Each should end up in the same opt-out record.

  1. Write an opt-out event with the time, the channel and the category the patient named. If they named none, I would treat it as every category.
  2. Cancel queued sends, and check the opt-out status again at the moment of sending. A reminder scheduled on Monday for Wednesday must not go out because the patient opted out on Tuesday, so the send job reads the record at send time, not at scheduling time.
  3. If the request opened a window, send one short confirmation and nothing else.

Marketing has a separate route that Meta handles. A patient can stop marketing messages from a business inside WhatsApp, and Meta then sends a user_preferences webhook with the category marketing_messages and the value stop (or resume if they change their mind). A marketing template sent to that patient returns error 131050, and Meta says not to retry. That webhook covers marketing only, so a patient who stops reminders by typing a word is invisible to it, and your own handling above is the only thing that catches it.

#What to log for the window and the templates

The consent log in my WhatsApp guide for clinics covers who agreed to what. These are the extra records the window and the templates need.

  • Every inbound message: its ID, timestamp and type, including button taps, which arrive with type button. The newest timestamp is your window clock.
  • Every outbound message: the message ID, whether it was free-form or a template, and for templates the name, language, category and the ID of the appointment it was about. I would log the appointment ID and not a copy of the message text, so the log does not become a second patient record.
  • The status webhooks for each message (sent, delivered, read, failed) with any error code, so a 131047 or a 132015 is visible. The status webhook also reports whether the message was charged and under which category, which lets you check what you were billed against what you sent.
  • Template changes: status, quality rating and category updates, with timestamps, from the template webhooks.
  • The identifiers as they arrive: phone number and BSUID.

#A send check in four steps

This is the order of checks I would build into a send function. It is a design, not code I have run.

  1. Is the patient opted out for this category? If yes, stop.
  2. Is the current time before the last inbound time plus 24 hours, and is a free-form message what you need to send? If yes, send it free-form.
  3. Otherwise, is there an approved, unpaused template in the right category? If yes, send it.
  4. If there is no such template, or Meta returns 131047 or a template error, create a task for staff and log it.

#Questions clinics ask

#Next step

If you are building a booking and reminder flow and want the window, template and opt-in handling designed properly, send your booking system, the countries you serve and what your compliance adviser has said with an estimate request or through the contact page, and I will tell you what is feasible and what it is likely to cost. My WhatsApp patient engagement service page describes the build, and the workflow automation page covers reminder scheduling. The WhatsApp window checker in the AI Lab is a scripted demo that applies the window, template and opt-in rules to a message you describe.

Last checked against Meta's documentation and policy pages on November 22, 2026. Meta changes its rules and rates, and its developer documentation has moved to a new address, so verify against the sources before you build. This is not legal advice.

#Sources

  • Meta, Service messages and the customer service window, developers.facebook.com/documentation/business-messaging/whatsapp/messages/send-messages
  • Meta, Obtaining user opt-in, developers.facebook.com/documentation/business-messaging/whatsapp/getting-opt-in
  • Meta, Template fundamentals, Categorization, Quality rating, Pausing and Review, developers.facebook.com/documentation/business-messaging/whatsapp/templates/
  • Meta, Utility templates, and Marketing templates per-user limits (US numbers), developers.facebook.com/documentation/business-messaging/whatsapp/templates/
  • Meta, Pricing (rates effective October 1, 2026), developers.facebook.com/documentation/business-messaging/whatsapp/pricing
  • Meta, Business-scoped user IDs and usernames, the messages webhook (button) and the user_preferences webhook, developers.facebook.com/documentation/business-messaging/whatsapp/
  • Meta, WhatsApp Business Cloud API error codes (131047, 131049, 131050, 132015, 132016) and message status webhook reference
  • WhatsApp Business Messaging Policy (last updated September 23, 2026), whatsappbusiness.com/policy
Part of the AI LabFree demos and plain-English guides on AI automation. Everything uses made-up data.
Newsletter

Stay updated with new posts

Get notified when I publish new articles about web development, system design, and AI. No spam, unsubscribe anytime.

Related Articles

Wondering what your project will cost?

Get a free price range and timeline in 24 to 48 hours. No commitment.

Get a Free Estimate