Free · the real ones
Patient message templates that pass review
The appointment reminder, the payment reminder, the review ask and the recall — as MedAppz actually sends them, with the consent purpose each one rides and what the engine checks in the second before it goes.
These ship as email templates
Every clinic on MedAppz is set up with these four, on email, approved from day one. The same body is what you register with your WhatsApp Business Solution Provider — and until that provider has registered it and its template id is recorded against the row, the WhatsApp copy stays submitted and the send path refuses loudly rather than quietly sending something else. That refusal is deliberate: the alternative is a clinic believing it is on WhatsApp when it is not.
Appointment reminder
appointment.reminderSubject — Your appointment at {{practiceName}}{{practiceName}}: {{patientName}}, your appointment with {{doctorName}} is at {{when}}. Please arrive a few minutes early.
Placeholders: {{practiceName}} · {{patientName}} · {{doctorName}} · {{when}}Rides the “Transactional messages” consent. We will message you about your own appointments, reports and bills. These are part of your care, not promotions. Implied consent is accepted for this one, and it never expires. A patient can still withdraw it, and withdrawal cancels what is already queued.It names the practice first, because a message that opens with a patient’s name and no sender reads like a scam. It asks for nothing and links to nothing, which is why it survives review almost everywhere. See the app →Before you submit it for review: A reminder about an appointment the patient made is the least contentious category there is. Keep the variable count low and do not add an offer to it — one promotional sentence turns the whole template into a marketing one.Payment reminder
payment.reminderSubject — A pending bill at {{practiceName}}{{practiceName}}: {{patientName}}, a bill of ₹{{amount}} is pending. Pay here when convenient: {{payLink}}
Placeholders: {{practiceName}} · {{patientName}} · {{amount}} · {{payLink}}Rides the “Transactional messages” consent. We will message you about your own appointments, reports and bills. These are part of your care, not promotions. Implied consent is accepted for this one, and it never expires. A patient can still withdraw it, and withdrawal cancels what is already queued."When convenient" is doing real work: a payment reminder that reads as a demand is the one patients complain about, and the complaint lands on the clinic, not on the software. The link is the clinic’s own pay link, not a third party’s. See the app →Before you submit it for review: A payment link inside a template is normal, but the domain it points at is looked at. Use your own, keep it stable, and do not shorten it through a redirector — a URL shortener in a healthcare template is the commonest rejection.Review request
reviewmagnet.askSubject — A minute to rate your visit?Hello — thank you for visiting {{practiceName}}. If you have a minute, a public review helps others find the right care: {{reviewUrl}}
Placeholders: {{practiceName}} · {{reviewUrl}}Rides the “Transactional messages” consent. We will message you about your own appointments, reports and bills. These are part of your care, not promotions. Implied consent is accepted for this one, and it never expires. A patient can still withdraw it, and withdrawal cancels what is already queued.There is no rating step before the link and there is no version of this that only goes to happy patients — gating reviews by sentiment is against every review platform’s rules and is the fastest way to have a listing penalised. The limits are a unique index, not a setting. See the app →Before you submit it for review: This is the one of the four to think about. As shipped it rides the care-message consent because it follows a visit, and that is a defensible reading — but a review ask is not clinically necessary, and a clinic that would rather it rode the campaigns consent can publish it under that purpose instead. Decide it on purpose rather than inheriting it.Recall invitation
recallwave.inviteSubject — Time to book: {{reason}}Hello — your care team asks you to book a visit: {{reason}}. Please call the clinic or reply to arrange a time.
Placeholders: {{reason}}Rides the “Transactional messages” consent. We will message you about your own appointments, reports and bills. These are part of your care, not promotions. Implied consent is accepted for this one, and it never expires. A patient can still withdraw it, and withdrawal cancels what is already queued.The reason is a variable, so the patient is told what they are being recalled for rather than being summoned. It asks them to call or reply, which keeps the conversation on a channel a person answers. See the app →Before you submit it for review: A recall is clinical follow-up, not a campaign — but the wording is what makes that true. "Your care team asks you to book" is follow-up; "book now and save" is a campaign wearing a clinical hat, and it will be graded as one.What happens in the second before a message goes
The consent check, and the row it writesThe template names a purpose; the engine asks the consent engine about that purpose for that patient and writes a check row either way — allowed or denied, with the reason and what was being attempted. There is no read-only variant that skips the row, so a message with no check row did not happen.The patient’s own preferenceA patient who has opted out of a channel or a purpose is suppressed with that reason on the dispatch, rather than being silently skipped.Frequency capsA daily and a weekly cap per purpose, counted from what was actually sent. A clinical alert is exempt by design: a patient who has already had three messages today still needs to know a result is critical.Quiet hoursA message that would land inside the patient’s quiet hours is moved to the next open time in their own timezone — deferred, never dropped, and the record keeps the time it was meant to go as well as the time it went.Withdrawal reaches back into the queueA withdrawal cancels everything already queued for that purpose and marks it cancelled for that reason. Stopping only the next send is what leaves tomorrow morning’s batch going out anyway.An unapproved WhatsApp template refusesA WhatsApp template is only approved once the provider has registered it and its provider template id is on the row. Until then the send path refuses loudly and the clinic falls back to a channel that works — never silently sends something else.
What this does not do
These are the bodies a MedAppz tenant ships with, not a WhatsApp policy guide. Whether your Business Solution Provider approves a template, and under which category, is their decision and Meta’s — we can tell you what ours look like and why, not what yours will be graded.
Get the pack as one printable page, with the consent notes beside each template
Everything above stays free and open — this page works without giving us anything. Tell us who you are and the printable version opens right here, on this page, with no email to wait for.