A pharmacy can organise availability, reservation, pickup, delivery, and document intake through WhatsApp, but it should not treat every question as ordinary retail service. The playbook must recognise when a conversation involves health data, prescription interpretation, use, interaction, risk, or a decision requiring a pharmacist.
Separate logistics from pharmacist guidance
Operations staff may communicate opening times, verified availability, order state, pickup, and an approved document channel. They should not interpret a prescription, suggest a substitution, or assess interactions, dosage, symptoms, or suitability. Those questions need a pharmacist with minimum context and explicit ownership.
Brazil's Law 13,021/2014 defines pharmacies as pharmaceutical-care service units and requires the responsibility and technical assistance of a licensed pharmacist. It assigns the pharmacist guidance about benefits, risks, storage, use, and interactions, as well as technical and legal review of prescriptions during dispensing.
Model four workflows with clear boundaries
| Intent | Standard action | Escalate when |
|---|---|---|
| Stock and reservation | Confirm location, exact product, and verified state | Alternative, substitution, or use question |
| Prescription and documents | Provide the approved channel and checklist | Interpretation, validity, mismatch, or sensitive data |
| Pickup or delivery | State status, identity check, and next action | Special storage, delay, damage, or missing order |
| Guidance and safety | Acknowledge and transfer to the pharmacist | Symptom, interaction, dosage, reaction, or urgency |
Every conversation needs a queue, owner, state, next action, and due time. “Forwarded” does not end ownership: the transfer is complete only when the new person or queue accepts the case. Department routing turns that handoff into a visible operating rule.
Treat health data as sensitive
Brazil's LGPD classifies health information as sensitive personal data and requires purpose, necessity, and security. Do not ask for a diagnosis to locate an order, copy prescriptions into personal groups, or expose a medicine name in unnecessary notifications. Define access, retention, deletion, and incident handling with the pharmacy's responsible professionals.
- Minimum data for each intent and purpose
- Individual access for orders, documents, and guidance
- An approved prescription and document channel
- A pharmacist queue with handoff acceptance
- Scripted replies limited to approved operational information
- A procedure for reactions, risk, or urgency
- Critical-action records without excessive detail
Check workflow eligibility before configuring the channel
The WhatsApp Business Messaging Policy treats drugs and medical products as regulated verticals. It prohibits using WhatsApp Business Services to buy, sell, promote, or facilitate their exchange except for limited exceptions described in the policy. Brazil is listed as an allowed country for Business Platform messages promoting over-the-counter drugs, but that exception does not apply to the WhatsApp Business App, does not permit a commerce experience, and requires age, geography, licensing, and legal controls. This playbook therefore covers approved customer service, request-status communication, and human routing after policy and compliance review; it is not a checkout, medicine catalog, or prescription-product sales workflow.
Respect expectations, consent, and the service window
The WhatsApp Business Messaging Policy says a business may only contact people who provided their number and opted in to subsequent messages. Opt-out requests must be honoured. On the Business Platform, business-initiated messages use approved templates; outside the 24-hour window after the user's last message, replies also require an approved template. When automation is used, the policy requires a prompt, clear, and direct route to a person. Record the authorised message category, explain its purpose, and connect the workflow to template governance.
Pilot stock, pickup, and pharmacist handoff
Start with availability and pickup questions in one location. Map what operations can resolve and the triggers that stop automation or a scripted reply.
Start with one location, shift, or high-volume intent. Test normal cases, missing information, unavailability, disputes, opt-out, and transfers. Supervisors should review a sample of real conversations and correct the source of each failure, not merely rewrite the final reply.
Review time to accept pharmacist handoff, located orders, repeat contacts, conversations exposed to the wrong person, availability failures, and exception causes. This article does not replace legal, regulatory, clinical, security, or responsible-pharmacist assessment.
Measure volume by intent, first reply, time to resolution, accepted transfers, unowned conversations, repeat contacts, and exception causes. Use consistent customer-service metric definitions, and do not reward fast closures that leave the problem unresolved.