Business account
Off personal phones; records, permissions and handover become possible.
Medical-tourism agency service
WhatsApp and Messaging Automation
Most first contact in medical tourism arrives through messaging apps. Automation moves that traffic off personal phones onto a business API, speeds the first reply with template messages, and binds every conversation to a CRM record.
Patient correspondence run from a personal account creates three problems: nothing is recorded, history disappears when a staff member leaves, and the arrangement is not defensible on data protection.
Why a business API is necessary
A personal app account was not designed for institutional use. Several people answering from one number, conversations entering the record and permission limits are only possible through the official business interface.
The number can usually be preserved during migration; whether past conversations move across is a separate decision that belongs with your data protection lead.
Automation does not mean a robot
The aim is not to make patients talk to a bot. Automation exists to avoid delaying the first reply, to manage out-of-hours expectations and to route an incoming message to the right person.
In practice three things happen: a greeting states the expected response time, a short classification message routes the request to the relevant unit, and when a person takes over the conversation opens with its history attached.
Scope of the setup
- Business account and number verification
- Greeting, out-of-hours and expected-response-time messages
- Approved template messages and their language versions
- Request classification and unit routing flow
- CRM integration: every conversation lands in one record
- Permission and access design; no data left on personal devices
- A separate, notified channel for clinical information and imagery
Health data starts here
A patient may send an X-ray or a photograph in the first message. That is the moment health data enters institutional responsibility, and it usually happens with no notice given at all.
Part of the setup is ordering that flow: where the image is stored, who can access it, how long it is kept and how the patient is informed are all put in writing.
Fast first reply
Template messages manage expectation without removing the human.
Imagery flow
A separate, notified channel is defined for X-rays and photographs.
Working sequence
How we move, step by step
- 01Current flow
Who answers, from which number and how, is mapped.
- 02Account setup
The business account and number verification are completed.
- 03Message set
Greeting, out-of-hours and classification messages are written.
- 04CRM connection
Conversations bind to one record and ownership is defined.
- 05Team hand-over
Usage rules and a data behaviour guide are delivered.
Frequently asked questions
What institutions ask most about this
Can we keep our existing number?
Usually yes. The number can move to a business account; migrating past conversations is a separate decision requiring a data protection assessment.
Will a bot talk to patients?
No. Automation only handles the initial greeting, out-of-hours notice and routing. Every clinically-shaped question is handed to a person.
How many languages can be set up?
Template messages are prepared in your target market languages. We advise against opening a channel in a language the team cannot answer.
What happens if a patient sends an X-ray?
Health data must move to an institutional, access-controlled environment and the patient must be informed. The setup writes that flow down; your data protection lead approves it.
How long does setup take?
Typically three to six weeks including account verification and template approvals. The timeline is set by platform approval processes rather than by the agency.
Does the agency see our messages?
No. Setup runs on test records; access to real patient correspondence is not requested.
Next step
Move messaging off personal phones
Share your current communication flow and we will build the institutional order together.