WhatsApp Consent for Clinics: Care Messages and Promotions
Separate clinic care messages from promotions with English and Hindi reminder examples, permission checks and a worked opt-out timeline.
A patient recall system turns a clinician’s follow-up plan into assigned work with a due date or window, an appropriate contact arrangement and a recorded outcome. Track contact, booking, attendance and completion separately. A reminder or an unrelated visit does not prove that the original clinical purpose was addressed. The clinician sets the plan; the system helps the clinic keep unfinished work visible.
For physicians, family practices and reception teams coordinating ongoing follow-up in Indian outpatient clinics.
“Review later” leaves reception without enough information to act. A usable plan identifies what is to be reviewed, when, who is responsible and whether anything must happen before the appointment. The level of detail visible to reception should fit its role; the clinical record can contain information that does not belong in a reminder.
Avoid making the software’s convenient 30-, 60- or 90-day setting the clinical rule. Patients with the same diagnosis can have different plans. A changed treatment plan, a result requiring attention or a new concern can also make an older routine recall inappropriate. The responsible clinician determines the relevant next step.
Keep routine recalls separate from urgent clinical escalation and pending-result review. A scheduled reminder is not a substitute for an action that needs a different response. The clinic should know who can change a plan and how reception raises uncertainty.
A patient can have more than one legitimate follow-up purpose. Store enough context to avoid confusing them, while avoiding duplicate messages for the same task. The recall should link back to the encounter and plan that created it, rather than existing only as a phone number on a campaign spreadsheet.
Ownership is operational as well as clinical. Reception may own contacting and booking, while a doctor owns review of an unresolved clinical question. Assign the next action to the appropriate person, including cover when the usual owner is absent.
On a narrow screen, scroll the table horizontally to read all columns.
| Field | What it answers | Common failure it prevents |
|---|---|---|
| Origin and purpose | Which encounter and clinician-assigned next step created this work? | Closing the wrong recall after an unrelated visit. |
| Due window | When should this plan be acted on, according to the clinician? | Using one automatic interval for every patient. |
| Contact arrangement | Which recipient and channel are appropriate for coordination? | Sending sensitive context to a shared number by default. |
| Current outcome | Was contact attempted, a booking made, a visit attended or the purpose reviewed? | Treating message delivery as completed care. |
| Owner and next action | Who does what next, and when is unresolved work reviewed? | A failed contact attempt disappearing into an unowned list. |
A clinician’s plan needs enough structure for the next person to coordinate it without making a clinical decision. In the fictional example below, the recorded review window is 2–6 November. That window is an invented instruction for this example, not a recommended interval for a disease or patient group. Reception’s job is to arrange the specified next step and report obstacles, not to decide whether a later date is clinically equivalent.
A sent message is a communication event. A booking is a scheduling agreement. Attendance establishes that a visit occurred. Completion of the recall requires a recorded outcome for its purpose, such as the clinician reviewing the planned issue or changing the plan. These events may occur on different days.
Cancellation, decline and inability to reach someone also need meaningful outcomes. They should not be disguised as successful completion. Record the outcome and route any remaining clinical decision to the appropriate owner under the clinic’s procedure.
If a patient attends for something else, show the outstanding recall to the authorized team without automatically closing it. The clinician may address it during that encounter, defer it with a new plan or decide it no longer applies. Preserve that decision and its link to the original task.
On a narrow screen, scroll the table horizontally to read all columns.
| Event | What is known | What remains to establish |
|---|---|---|
| Contact attempted | A particular channel was tried at a recorded time. | Whether the intended person was reached and what was agreed. |
| Booked | An appointment is linked to the recall. | Whether the visit occurs and addresses the purpose. |
| Attended | The relevant visit occurred. | The documented review or change to the follow-up plan. |
| Purpose reviewed | The responsible clinician recorded the relevant outcome. | Any new plan or task created by that review. |
| Declined or unreachable | The communication outcome is recorded. | The next step required by the clinic’s clinical coordination process. |
At an agreed point in the working day, review newly due items and unresolved items whose next-action date has arrived. Remove duplicates only after checking that they represent the same purpose. Do not merge clinically different plans merely because they belong to one patient.
Prepare only the information needed for contact. A neutral appointment-coordination message often serves the administrative task without naming the condition. Confirm the recipient arrangement, especially for shared phones, and follow the chosen platform’s permission requirements.
Set a clinic-approved process for contact attempts and escalation rather than an endless automated retry. The number and timing of attempts should fit the actual plan and responsibilities; this article does not prescribe a universal attempt limit or clinical deadline.
A solo doctor can run the same logic with a modest list and protected review time. The key constraint is whether someone will act on the list, not whether the clinic has a large call centre. Start with a manageable scope before introducing more automation.
Suppose the same fictional patient has R-21 for review of an earlier plan and R-22 for a different clinician-recorded purpose. One appointment may address both, one or neither. Linking both recalls to that visit can help the doctor see them, but the link should not automatically close either purpose. The clinician records the disposition for each.
On a narrow screen, scroll the table horizontally to read all columns.
| Recall | Recorded outcome at the visit | Coordination consequence |
|---|---|---|
| R-21: earlier-plan review | The clinician documents that the intended review occurred and records any next plan. | Close this purpose against the review evidence; create or link any new work separately. |
| R-22: another planned review | The purpose was not addressed; the clinician records a revised arrangement. | Retain the revised task and suppress the superseded reminder without erasing the original plan. |
| A duplicate copy of R-21 | Authorised review establishes that it represents the same purpose and source encounter. | Resolve the administrative duplicate with a link to the retained record; do not count it as another completed clinical review. |
A rescheduled appointment and a revised clinical plan are different changes. If the patient moves a booking outside the recorded window, reception records the request and routes the timing mismatch through the appropriate process. It should not edit the clinical plan merely to make the booking appear within range.
When the clinician changes the plan, record the reason at the appropriate level, the new instruction and the link to the earlier task. Then inspect affected reminders, call lists and appointments. Cancelling the old reminder is only one part of the update; the replacement task still needs an owner and a usable contact arrangement.
For a patient who reports review at another clinic, record the source of that report and any document available through an appropriate route. The responsible clinician decides what it means for the outstanding purpose. Neither reception nor an automated rule should convert “patient says seen elsewhere” into an unsupported clinical completion.
A stored number can remain technically valid while becoming unsuitable for the agreed purpose. The patient may no longer use that family phone, may want a different language, or may no longer want a relative to coordinate appointments. Record the change against the affected patient and purpose; do not overwrite other relatives’ arrangements simply because they share the number.
A changed or unsuitable number is a contact exception. A request to stop a channel is a preference change. Neither tells reception to erase the underlying clinical task. Pause inappropriate automation, record the outcome and route the remaining coordination decision through the clinic’s process.
Check reminders already selected for sending as well as future recall runs. Updating a profile field may not withdraw a message already passed to a provider. Record what the configured system can suppress, what has already happened and which coordination task still needs an appropriate route.
“No answer” should record the attempted channel and time, whether the destination was the agreed one, and the next action under the clinic’s process. It should not imply that the patient declined care. A wrong number, an unanswered call and an explicit request to stop a channel are different outcomes with different follow-through.
If a family member answers, establish what the recorded arrangement permits before discussing the purpose. An administrative request to contact the clinic may be appropriate within that arrangement, while disclosing a diagnosis or report may not be. Use the clinician-approved communication plan and route uncertainty rather than improvising sensitive content during the call.
Assign the unresolved clinical coordination decision to the responsible clinician or cover when the agreed contact process cannot progress. The action may be to clarify the route, revise the plan or take another appropriate step. This guide supplies no universal number of calls, interval between attempts or deadline for clinical escalation.
Consider a fictional cohort of ten recalls due this week. Eight have a usable agreed contact route. Five produce a booking, four result in attendance and three have a documented review of the original purpose by the reporting cutoff. The two without an appropriate contact route remain visible for follow-through.
Booking is 5 of 10 due recalls, or 50%. Attendance is 4 of 10, or 40%. Documented review is 3 of 10, or 30%. If someone reports booking as 5 of 8 contactable recalls, that is 62.5% with a different denominator. Both calculations can be useful, but the denominator and cutoff must be stated.
Do not infer treatment outcomes or software-caused improvement from these figures. Some reviews may occur after the cutoff, and case mix or changes in clinic availability can affect the pattern. Follow the same cohort through later outcomes and keep exclusions visible.
Operationally, the example points to different work: clarify two contact arrangements, follow unresolved contacts or bookings, and determine the outcome of the attended visit without a recorded review. A single “messages delivered” score would conceal all of that.
Return to the ten-recall cohort. At the next reporting cutoff, suppose two additional original purposes have documented reviews. The cumulative result for that original group is now five of ten, or 50%, rather than three of ten, or 30%. If four new recalls become due in the meantime, show them as a new due group; adding them to the old denominator would answer a different question.
A rolling work list is still useful for daily coordination, but it is not the same as a cohort report. The work list shows what needs action now. The cohort report follows the selected original purposes through later outcomes, including unresolved, declined, superseded and reviewed states. State which view is being used before comparing percentages.
Preserve the distinction between clinical review and another authorised disposition. If one purpose is superseded by a new plan, show that outcome rather than counting it as a review that occurred. If the original list contains a confirmed administrative duplicate, record the exclusion and explain any denominator revision. A cleaner number is not sufficient reason to remove a difficult case.
Create fictional recalls covering a straightforward booking, an unrelated attended visit, a changed plan and an unsuitable contact route. Follow them through the same reception and doctor screens the team will use. Inspect who can change each state and whether the original purpose remains visible.
Then agree a small operational pilot with named owners and a review time. Assess missing plans, unassigned tasks, duplicate contacts and unexplained closures. Expanding the list before these issues are understood increases the amount of unfinished work rather than improving continuity.
Bractis’s follow-up page is first-party product context. Ask for evidence of the configured due list, patient matching, permissions and outcome history. Confirm how a booking and an attendance link back to the original recall.
A fictional patient attends for a new concern while a previously planned review is still due. Reception links the attendance to the actual encounter but does not close the older recall automatically. The doctor sees the outstanding purpose and records whether it was addressed or needs a revised plan. The recall history then explains the clinical disposition instead of merely showing that the patient entered the clinic.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
It can address both if the clinician records an outcome for each purpose. The appointment link or attendance alone is insufficient. Keep any unaddressed or revised purpose visible with its next action and owner.
Record the booking request separately. If it falls outside the clinician’s plan, route the mismatch for the appropriate decision. Reception should not silently change the clinical instruction to make the calendar and recall appear consistent.
No single interval fits every patient or condition. Use the responsible clinician’s recorded plan, and revise the recall when that plan changes.
No. Delivery, booking, attendance and review of the clinical purpose are different events. Retain the relevant evidence for each.
Yes. A small assigned due list with protected review time can support the same process. Start with a scope the doctor and reception can actually follow through.
Only when the recorded outcome explains what happened to that recall’s purpose. An unrelated attended visit should not silently close it.
Track the cohort due, usable contact arrangements, bookings, attendance, documented review and unresolved work. State the denominator and cutoff so the figures remain interpretable.
Updated on . The workflow and arithmetic examples are original illustrations. This guide does not prescribe disease-monitoring intervals or establish that software improves clinical outcomes. No independent clinical or legal review is claimed.
Primary platform reference for contact permission and opt-out handling, checked 26 October 2026. It does not set clinical recall intervals or validate the original cohort examples.
First-party workflow context; confirm the current configured capabilities and outcome history.
Separate clinic care messages from promotions with English and Hindi reminder examples, permission checks and a worked opt-out timeline.
Track pending clinic lab results with partial-report examples, corrected-version reviews, cover handovers and a six-order audit.
Map a solo clinic visit, handle staff handovers and track unfinished reports, documents and payments with worked OPD examples.
Trace a fictional recall through contact, booking and attendance, then test an unrelated visit and a changed contact preference. Inspect what remains open and who owns it.
Request a clinic demo