Documentation navigation
WhatsApp connection
WhatsApp can be connected without giving autonomous AI access to every incoming conversation. Clinics can enable all inbound conversations or restrict autonomy to known patients only — which makes it practical to use an existing personal or mixed-use WhatsApp number safely.
What the connection is used for
- Receive patient messages into the clinic communication workflow.
- Create a lead and conversation when a new person writes for the first time.
- Recognize an existing patient and continue or reuse the relevant conversation context.
- Automatically reply to new incoming messages when clinic autonomy and channel rules allow it — including new messages in an older conversation.
- Use clinic and patient context instead of treating every message as a new anonymous chat.
- Support scheduling and routine administrative questions from the conversation.
- Import previous WhatsApp history as context without treating the import itself as a reason to send new messages.
Choose who Menaela is allowed to answer
WhatsApp connection and WhatsApp autonomy are separate decisions. Connecting an account does not mean Menaela has to answer every person who writes to it.
The WhatsApp automation modes are mutually exclusive: off, all inbound, or known patients only.
| Mode | Autonomous behavior | Unknown senders |
|---|---|---|
| Off | No autonomous WhatsApp replies. | Messages remain available for staff; no automatic WhatsApp lead creation. |
| All inbound | Menaela can answer supported incoming conversations and continue patient or lead workflows. | An unknown sender can enter the lead flow when the clinic has enabled this mode. |
| Known patients only | Menaela answers only after the sender is matched to an existing patient. | No model run, no autonomous reply and no automatic lead creation. |
Known-patients-only mode checks patient identity before the autonomous agent is invoked. Unknown contacts stay out of the AI flow, while staff can still read and message manually.
Before connecting a live number
- Providers and services are configured correctly.
- The clinic timezone and default language are correct.
- Patient Chat Test has been used for normal and awkward booking conversations.
- The clinic knows which medical, payer and referral questions should escalate.
- Message style instructions are set if the clinic has specific wording requirements.
Patient identity and context
A phone number is useful context, but identity should still be resolved according to the workflow before sensitive patient data is exposed or an existing appointment is changed.
The goal is continuity without treating every incoming number as unquestionable proof of identity.
Keep messaging channel-appropriate
WhatsApp replies should be concise and readable on a phone. Avoid desktop-style formatting or unnecessarily long explanations. Clinic instructions can tune the voice, but safety and configured clinic facts still take priority.
A green integration status proves that messages can move. It does not prove that booking logic, patient context and escalation behave correctly.