Patient Communication Preferences: Record Purpose, Recipient and Channel
Capture shared-phone arrangements, preferred language, permission and opt-outs without treating one contact number as authority for every patient.
Indian clinics should plan bulk SMS and WhatsApp Business Platform messaging as separate services. SMS involves the applicable telecom sender, header, template and routing requirements; WhatsApp has its own business setup and messaging policy. Neither registration nor an approved template proves that a patient has authorised the intended contact, that a message arrived, or that the clinic can manage replies. Start with the message purpose and an accountable clinic-owned setup record.
Indian clinic owners and administrators choosing a provider for appointment reminders, service updates and other patient communications.
A proposal saying 'WhatsApp and SMS enabled' hides several decisions. Is the clinic buying a staffed WhatsApp Business App workflow, a Business Platform integration, a bulk SMS service, or a combination? Who controls the business identity and destination number? Which system receives replies? A receptionist cannot resolve a failed appointment reminder by knowing only the vendor's feature name.
Describe the first intended use in one sentence: for example, a neutral reminder for an already booked OPD appointment, with a working route to request a change. Keep a public awareness campaign, an offer and a clinical exchange as separate uses. The right questions about permissions, message wording and response ownership depend on what the message does.
TRAI's sender guidance lists principal-entity registration, a header, a content template and transmission of the relevant identifiers for bulk telecom messaging, with consent arrangements where applicable. This is a starting point for an SMS discussion, not evidence that a clinic has completed the process or that an SMS registration authorises a different messaging platform.
The TRAI notification dated 18 September 2026 is a third amendment to the 2018 regulations. Its first page sets different commencement periods of 30, 60 and 90 days from publication in the Official Gazette for different provisions. The notification's heading date alone is therefore insufficient to calculate when a particular change applies. Do not treat the March 2026 consultation draft or a May consolidation as the complete current position.
For your actual service, ask the access provider or messaging provider to identify the applicable category, current process and supporting official notification. Record the document date, relevant provision, Gazette-publication evidence where needed, and the person who confirmed the implementation requirement. A screenshot of a green registration badge is not that record.
This guide does not assign every clinic reminder to a universal legal category, provide a final commencement calendar or recommend sending through ordinary personal numbers to avoid registration. It gives the clinic a way to obtain a specific, dated answer. If a provider's explanation conflicts with an official source, keep that discrepancy open before enabling the affected use.
Source: TRAI: Third Amendment Regulations, 18 September 2026
Maintain a short evidence register rather than a folder of unexplained screenshots. The owner should be able to identify the registered entity, account administrator, approved use, current template, destination-selection rule and support contact without relying on one employee's personal login. Give each uncertainty a named owner and a practical next action.
WhatsApp's September 2026 policy requires recipient opt-in and respect for opt-outs. Its Business Platform uses approved templates for initiated conversations; free-form replies are limited to the customer-service window, which resets with a user message. It also places conditions on health information and restricted activities. Template acceptance is not permission to run every healthcare workflow.
On a narrow screen, scroll the table horizontally to read all columns.
| Question | Evidence to retain | What it does not prove |
|---|---|---|
| Who is the sender? | Clinic entity, business identity, authorised administrator and provider account. | Permission to contact every number in an imported file. |
| What may be sent? | Current purpose, category and applicable template record. | Suitability of any text inserted into variables. |
| Why this recipient? | Patient-specific contact arrangement and applicable permission record. | That every family member using the phone has agreed. |
| Was it accepted for sending? | Provider reference and submission result. | Delivery, reading or patient understanding. |
| Who handles the answer? | Staffed reply route, hours and exception owner. | Continuous clinical monitoring. |
| Can the clinic leave? | Account ownership, export scope and provider-exit terms. | Automatic portability of every template or history. |
Use a synthetic appointment and authorised test numbers before a live rollout. Insert a long doctor name, a changed date, the real clinic timezone, a missing optional field and the longest location description you intend to allow. Check the resulting message on the receiving device. A preview with neat placeholder values may conceal truncation, a wrong branch address or an unresolved variable.
Ask the provider to show its own delivery evidence. For example, Twilio documents different initial and later message states; those are provider-specific examples, not evidence that Bractis uses Twilio. Your acceptance record should name the actual provider, reference, status meaning and destination. Keep screenshots free of patient data when using them for vendor evaluation.
Exercise the return journey as well. A patient who requests cancellation needs a supported channel and a clear appointment outcome. If SMS replies are unsupported on the selected route, the message must direct them elsewhere. If a WhatsApp reply reaches a separate inbox, staff need an agreed method to connect it to the correct booking without copying the conversation into an unrelated patient record.
Separate provider setup, recurring access, platform charges, message units, staff work and exception handling. Ask whether tax is included and which failed, retried or multi-part messages are billable under the actual contract. Do not multiply the number of appointments by a headline unit price and call it the total operating cost.
Twilio's reference explains that a long SMS can use multiple chargeable segments. That is a useful reason to ask your own provider for a rendered-message cost check, especially when using regional scripts; it is not a universal tariff. A concise Hindi message and a longer English message can have different encoding and segmentation consequences. Measure the actual text and route instead of imposing an unverified character allowance.
In a fictional planning example, 600 appointment reminders and 120 schedule-change notices create 720 intended communications before retries. If 10% need a three-minute staff follow-up, that is 72 tasks or 216 minutes. This is a workload estimate, not a provider bill or an expected failure rate. It exposes why a cheap sender without a usable exception queue can consume reception capacity.
Keep administrator recovery and provider support accessible to the clinic owner through authorised accounts. Define who can edit templates, export contact information and start a batch. A staff departure should not leave the clinic unable to pause messages or prove which entity controls the service.
Start with a bounded appointment workflow. Stop the affected sends if the destination mapping is wrong, permission cannot be established, the template no longer matches the appointment, or replies have no responsible person. A provider outage calls for a documented alternative; it does not justify sending the same private information through every available channel.
A clinic group receives a successful test reminder from the provider, but it names the first branch for both locations. The registered sender and template approval are valid for the demonstrated setup, yet the location variable is mapped incorrectly. The group pauses the second-branch workflow, corrects the source field, tests both branches and records the resulting message references. It has found an operational defect that registration checks alone would not reveal; it does not need to call the whole platform compliant or non-compliant to explain the decision.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
Treat the two services separately. An SMS sender registration does not establish your WhatsApp business setup, recipient permission, template status or ability to handle replies. Ask for channel-specific evidence in the proposal.
A provider may assist with the process it offers, but the clinic should know the registered entity, authorised accounts and responsibilities. Obtain a clear explanation of ownership and recovery instead of accepting an account controlled only by an individual salesperson.
No. It is evidence of a platform or telecom approval for a stated purpose. The recipient, inserted values, actual healthcare use, privacy arrangements and applicable professional requirements still need separate consideration.
Only if the estimate also states message count, segments where relevant, provider terms, changes, retries and staff follow-up. Ask for a sample calculation using your actual planned wording and route; the fictional workload here is not a price quote.
Verify the sender and destination, current appointment details, permitted purpose, opt-out handling, failure worklist and reply route with synthetic data. Record which cases worked and what the clinic will do when a message or reply remains unresolved.
Updated on . Dated source review and original clinic procurement analysis. TRAI commencement must be tied to the relevant Gazette publication and provision; no complete legal determination, messaging integration or delivery guarantee is claimed. No independent clinical or legal review is claimed.
Sender, header and template registration guidance. Read with current amendments and the access provider's applicable procedures.
The notification's first page specifies phased commencement from Gazette publication, not its heading date. Downloaded from TRAI and checked in text and page image.
Current policy, updated 23 September 2026; the official URL redirects to whatsappbusiness.com. Platform terms do not establish Indian medical or privacy compliance.
A named-provider example of status transitions and supported read receipts, not proof of Bractis's provider or capabilities.
Provider-specific message identifiers, status and segment information; actual routes and billing need their own evidence.
Capture shared-phone arrangements, preferred language, permission and opt-outs without treating one contact number as authority for every patient.
Distinguish queued, sent, delivered, failed and unknown messages; assign recovery work and avoid duplicate reminders after timeouts.
Review appointment messages by purpose, language, variable meanings and live status; prevent stale templates and wrong-recipient batches.
Bring one appointment message and its expected reply path. Ask Bractis to demonstrate the proposed provider setup, patient selection, message evidence and failure handling within the scope actually offered.
Request a clinic demo