Shared Family Phone Numbers: Keep Each Patient Record Separate
Handle shared family phones with separate patient records, worked matching cases, purpose-specific contact changes and queued-message checks.
A clinic should decide who will receive a message, why it is being sent and which channel the recipient has agreed to use. Keep appointment coordination, clinical document delivery and promotion distinct in the contact record. Recheck that record when sending, including messages already queued. A telephone number collected for registration does not explain whether a family member may receive a report or whether the patient wants promotional messages.
For Indian clinic owners and reception teams designing patient reminders, shared-phone communication and messaging preferences.
Imagine three messages sent to the same number: an appointment time, a link to a laboratory report and an offer for a clinic package. The destination is identical, but the purpose, information disclosed and recipient expectations differ. A single “WhatsApp enabled” switch cannot explain all three decisions.
Write down the proposed message before designing the preference form. Identify the minimum information needed for its purpose, the expected recipient and the action the recipient can take. A reminder normally needs a recognizable clinic identity and practical appointment information; adding the diagnosis merely because it is available in the chart creates a separate disclosure.
Notification previews also matter. Read the message as someone looking at a shared phone would read it. A link may conceal the document itself while the accompanying text reveals the specialty, procedure or condition. Assess the text, preview and destination together.
Use this fictional writing exercise before asking a provider to configure a template: “Hello from [clinic]. Your appointment is on [date] at [time]. To change the arrangement, use [monitored contact route].” It identifies the sender, states the administrative event and gives a usable next step. It deliberately contains no diagnosis, investigation result or sales offer. It is not a provider-approved template or a legal consent notice.
A Hindi version to adapt for the clinic’s audience could read: “नमस्ते। [क्लिनिक] में आपकी अपॉइंटमेंट [तारीख] को [समय] पर है। समय बदलने के लिए [संपर्क का तरीका] का उपयोग करें।” Have staff fluent in the patient’s preferred language review the final wording and variable values. A translated template is useful only if the recipient can understand the arrangement and the clinic can respond through the route it offers.
On a narrow screen, scroll the table horizontally to read all columns.
| Message element | Why it is present | What to verify before use |
|---|---|---|
| Recognisable clinic identity | Helps the recipient understand who is contacting them. | The identity is accurate; consider what the clinic or specialty name itself reveals on a shared-phone preview. |
| Appointment date and time | States the specific coordination event. | These come from the current appointment, including any reschedule; the time means what the clinic actually promised. |
| Route to request a change | Gives the recipient a practical response path. | Staff monitor that route and know how to process the request; do not promise instant replies by default. |
| No appended offer or clinical summary | Keeps this example focused on its appointment purpose. | A later edit that adds another purpose receives a fresh content and eligibility review. |
Use categories that correspond to real clinic activity. The matrix below is an operational design example, not a statutory classification. It helps the desk explain a choice and prevents a campaign export from inheriting every number in the patient register.
Do not assume that selecting a category makes every proposed communication permissible. The clinic still needs to establish the appropriate recipient, provider capability and applicable requirements for that particular use. Clinical delivery, especially, needs a more considered process than an ordinary appointment reminder.
On a narrow screen, scroll the table horizontally to read all columns.
| Purpose | Useful preference detail | Boundary to preserve |
|---|---|---|
| Appointment coordination | Recipient, channel, number and agreed reminder arrangement. | A reminder preference does not authorize unrelated offers. |
| Follow-up coordination | Contact arrangement for the clinician-assigned next step. | Contact status does not establish that follow-up care occurred. |
| Clinical document delivery | Intended recipient and the clinic-approved delivery method. | Permission to book for a relative does not automatically establish permission to receive their records. |
| Promotional communication | A distinct choice about the proposed category of promotion. | A decline should not be silently overwritten when another appointment is booked. |
The WhatsApp Business Messaging Policy, updated 23 September 2026, requires recipient opt-in and respect for opt-out requests received on or off the platform. Its Business Platform rules also govern templates and conversation windows. The policy contains health-information and regulated-goods restrictions. Check the actual proposed use with the clinic’s responsible team and provider; recipient permission alone does not establish that a use is allowed.
Separate category choices are useful for clinic operations because a person may accept an appointment reminder but decline an offer. The wording and capture method should fit the actual channels and responsibilities. Do not present a generic checkbox as proof of compliance with every Indian legal requirement.
Keep the distinction between a platform rule, the clinic’s own operational design and applicable law visible in staff instructions. If a provider approves a template, that is not a clinical review of its contents or proof that the chosen recipient is appropriate.
The right question is not simply whether a contact has ever opted in. For the proposed action, staff need the patient reference, intended recipient, purpose, current channel choice, source event and exact message version. A reminder selected before rescheduling may still have valid contact permission but the wrong appointment time. A correct message can still have an unsuitable recipient.
Use three operational outcomes: eligible for the specified send, suppressed by a recorded instruction, or held because evidence is incomplete. These are proposed clinic workflow labels, not WhatsApp API statuses. A hold should identify the missing decision and its owner. It should not become a quiet default approval when a batch reaches its scheduled send time.
A software demonstration should show the reason behind each outcome. “Not sent: promotional category declined” tells staff what happened. “Error” does not tell them whether to correct the number, respect a preference, update an appointment or investigate the provider. Keep those explanations visible only to authorised staff and avoid exposing sensitive context on a public reception display.
The contact record needs more than yes or no. Retain the purpose, channel, destination, person making the choice, capture method and date, together with changes. Staff should be able to understand the current instruction without interpreting an old free-text conversation from scratch.
Use plain language the person understands. Explain the clinic identity, the type of message and how to change the arrangement. A staff script can support that conversation, but the saved outcome must reflect the actual answer rather than a preselected default.
The example below is a discussion aid to adapt and review. It deliberately leaves document delivery as a separate decision; it is not a legal consent form or a recommendation to use any particular channel for clinical information.
Consider a reminder selected on Monday for delivery on Wednesday. If the patient changes the number or stops that category on Tuesday, a system that only checked preferences on Monday can still send the wrong message. Test the point at which eligibility is evaluated and what staff can do with already queued work.
The same problem occurs when a list is exported to another provider. Identify who owns the suppression or cancellation process there. Changing the clinic screen may have no effect on a list already uploaded elsewhere. Keep enough batch information to locate and reconcile affected messages.
After a failed delivery, distinguish a technical failure from an unsuitable recipient or a withdrawn preference. Repeating an attempt may be appropriate for some provider failures under an agreed policy; it does not resolve an incorrect number. An unresolved care task needs a clinical coordination decision even if the messaging attempt is stopped.
In this fictional example, an appointment message is selected at 09:00 and the provider accepts it into a queue at 09:10. At 09:20, the recipient asks reception to stop WhatsApp contact. The scheduled send is 10:00. The critical issue is whether the recorded request reaches the action that is already outside the clinic’s local list.
On a narrow screen, scroll the table horizontally to read all columns.
| Event | Clinic action | Evidence needed before closure |
|---|---|---|
| 09:00 — message selected | Record the patient, event, purpose and content version used. | Selection is traceable; it is not a claim of delivery. |
| 09:10 — provider queue accepts the item | Retain the provider/batch reference and supported cancellation route. | The item can be found outside the local application. |
| 09:20 — stop request recorded | Suppress further affected sends and locate already queued work. | The scope of the instruction and affected item references are recorded. |
| Before the 10:00 scheduled send | Request cancellation through the supported provider process. | A confirmed cancellation is distinguished from a request or unknown outcome. |
| Outcome remains uncertain or the message was already sent | Keep the exception visible and investigate through the approved process. | Record what actually happened; changing the preference does not recall a delivered message. |
A provider can accept a message without delivering it. A device may receive it without the intended patient understanding or agreeing to the arrangement. Store the available provider status, its reference and observation time, then record any separate patient response. Use the documented meaning of the actual provider’s statuses instead of inventing a clinical outcome from an icon.
If a reply asks for a different appointment, the task becomes a scheduling request, not a completed reminder. If the person says they are not the intended recipient, stop the affected route and investigate the relationship. If a reply raises a clinical concern, route it through the clinic’s clinical process; reception should not answer it from a generic reminder script.
Make monitoring boundaries visible in the clinic’s operating procedure. Identify who checks responses during opening hours and what happens outside those hours. A message channel should not appear continuously monitored if the clinic does not provide that service. Any patient-facing urgent-care instructions need the responsible clinician’s approval and an appropriate local pathway.
A template can change meaning without changing its name. An administrator might append an offer, add a test name to the preview or replace a monitored contact route with an unattended number. Keep a version record and review the actual rendered message with representative fictional values before the revised version is used.
Check both old and newly created queued items. Some systems may retain the content selected earlier; others may render the current template at send time. Establish the actual behaviour, decide which version is intended and test a held item before resuming automation. A screenshot of the template editor cannot establish what a patient would receive from an already queued action.
Use fictional contacts to test a shared number, a declined promotional category, a number changed after scheduling and an opt-out recorded by reception. Inspect both the saved preference and the provider queue. The result should explain why a message was eligible, cancelled or held.
For legacy contacts without clear preference evidence, decide how the clinic will establish a suitable arrangement through an appropriate existing interaction. Do not label missing evidence as acceptance merely to increase the available audience.
Bractis’s engagement page describes product scope. In a demonstration, confirm the actual provider, preference fields, queue behaviour and charges. A useful acceptance record includes the outcome of a changed preference, rather than just a screenshot of the send button.
In a fictional family clinic, an adult patient agrees that appointment coordination can go to the family number but chooses a different approved arrangement for records. A relative later asks reception to stop promotional messages at that number. The desk records the change, checks any campaign already queued and preserves the distinct appointment and document arrangements that remain valid. It does not delete the patient’s chart or assume that every unfinished care task is cancelled. Any ambiguity about the request is clarified before further sending.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
Recheck the current instruction, recipient, source appointment or task, and content version before the supported send action. A reschedule, recipient change or stop request can make an earlier selection unsuitable. Already exported items need their own cancellation or update evidence.
No. Keep provider delivery, patient response, booking changes and actual attendance as separate events. If the reply asks for a change, assign the scheduling request instead of marking the original arrangement confirmed.
A stored number does not explain permission, recipient identity or purpose. Review the contact arrangement and applicable channel requirements before using a list, particularly for promotion.
Patients may want one category and decline another. Separate choices let reception apply that distinction and avoid overwriting it when someone books a new appointment.
Record the request through the clinic’s process and check messages already queued or exported. Clarify any ambiguous scope and arrange an appropriate alternative for unfinished care coordination.
Do not infer that from the reminder preference alone. Establish the intended recipient and the clinic-approved document-delivery arrangement separately.
No. Template approval does not establish that the patient, recipient, purpose, content and handling are appropriate in a particular case. Those decisions remain part of the clinic’s actual process.
Updated on . This is an operational design guide. The example categories and staff wording are not statutory consent forms or a determination of the legal suitability of a channel for a particular clinical communication. No independent clinical or legal review is claimed.
Primary platform policy, updated 23 September 2026 and checked 26 October 2026. Clinic categories, sample wording, eligibility labels and the timeline are original operational examples, not provider-approved templates.
First-party product context; confirm the actual provider, configuration, permissions and usage charges.
Handle shared family phones with separate patient records, worked matching cases, purpose-specific contact changes and queued-message checks.
Manage patient recalls with clinician-defined plans, overlapping purposes, unsuccessful-contact handovers and a worked follow-up cohort.
Compare EMR quotes with first-year and renewal calculations, monthly usage allowances, upfront commitments and invoice checks for Indian clinics.
Use fictional contacts to test different message preferences, a shared number and a change after scheduling. Inspect what reaches the configured provider queue.
Request a clinic demo