WhatsApp as the primary channel for international enquiries

WhatsApp for international patients carries the entire relationship across a border, not a quick booking. Run it on one verified business number rather than personal phones, roster to your largest markets’ time zones, build approved templates in each supported language, move every report into the CRM the same day, and treat handover between coordinators as the point where cases are actually lost.

Ask any international desk in India where their enquiries actually live and the answer is the same. Not the web form. Not email. A messaging thread, usually on a phone, usually running from the moment a family first hears the hospital’s name until months after the patient has flown home.

WhatsApp for international patients is not the same product as WhatsApp for your domestic front door, even though it is the same app. At home the channel is mostly about speed and convenience: book me, remind me, send me the report. Across a border it is carrying the entire relationship. It is where the family sends photographs of reports they cannot post, where an estimate is discussed, where a coordinator proves a human being exists, where the son in another country joins the conversation, and where the hospital either earns the trip or loses it.

I have written before about WhatsApp as a hospital’s front door for domestic enquiries. Almost everything in that piece still applies. What follows is the part that is genuinely different when the person messaging you is in another country, in another time zone, in another language, with no way to walk in and check whether you are real.

Why WhatsApp for international patients is a different channel

Three things change. The first is asymmetry of trust. A family in your own city can drive past the hospital. A family abroad has only what appears on a screen, so every element of the thread, including the display name, the profile photograph, the grammar and the response time, is being read as evidence about whether you are a real institution or a middleman.

The second is the shape of the conversation. Domestic threads are short and transactional. Cross border threads run for weeks before anyone travels and for months afterwards. They accumulate documents. They pull in several people: the patient, a spouse, an adult child working in a third country who is paying, sometimes a local doctor, sometimes a sponsor’s office.

The third is cost and habit. In many source markets for medical value travel, a voice call to India is expensive and unreliable, while messaging over a data connection is normal for everything from family news to business. Voice notes matter enormously, because a mother who cannot type a long English message can speak one. If your desk treats voice notes as a nuisance, you are refusing the format half your market prefers.

The number is part of the brand

The single most common failure I see is a channel run on coordinators’ personal phones. It works, right up until it does not. The coordinator leaves and takes the relationship, the history and the documents with her. Two coordinators give two different answers on two numbers. Nothing reaches the CRM. Nobody can audit what was promised. And the family has no way to tell whether the number they were given belongs to the hospital at all.

Use one official business number per hospital or per international desk, verified, with a complete business profile: the legal hospital name, the address, the website, working hours stated with the time zone. Verification is not cosmetic. For a family who has been warned about fraud, the difference between a verified business profile and an unknown number is the difference between replying and not replying.

Publish that one number everywhere the market sees you, in international format with the country code, as a tappable link rather than text to copy. Resist the urge to run a separate number per market. It fragments the record, confuses the family who was given a different number by a referring doctor, and multiplies the cost of keeping profiles accurate. One number, several agents behind it, routed by language and market.

When a coordinator does need a direct thread with a family, it should still run through the official number as an assigned conversation, not a personal handset. The relationship belongs to the hospital.

Covering a working day that is not yours

Your desk works Indian hours. Your markets do not. East Africa is a little behind you, West Africa more so, Central Asia close, the Caucasus and eastern Europe further, and the Pacific islands are effectively a day away. Some of your markets treat Friday as the day nothing happens, others treat Sunday that way, and public holidays in a source market will empty your enquiry flow for a week if you do not know they are coming.

Two decisions follow. First, roster deliberately rather than by accident: stagger the desk so the busiest hours of your two or three largest markets are covered by someone who speaks the language, and accept that this means early mornings or late evenings for somebody. Second, be honest in the automatic reply. An auto reply that says a team will respond shortly, sent at two in the morning their time, tells the family nothing. An auto reply that states your working hours in their time zone and when they can expect a human answer is far better, and far easier to keep.

Speed matters most on the first message, because that is when the family is messaging several hospitals at once. What a good first reply to an international enquiry contains is worth settling as a policy rather than leaving to whoever is on shift. After the first reply, consistency beats speed: a family will wait if they know when the answer is coming.

Language in a written channel

Written language is harder than spoken language for most people, including your agents. A coordinator who handles a phone call in Arabic confidently may write it slowly and with errors. A family may read English well but write it badly, or write their own language in Latin script.

Build a library of approved message templates in each language you support, covering the recurring moments: acknowledgement, what documents to send, how an estimate is produced, what happens on arrival, admission instructions, and follow up after discharge. Have them written by a native speaker and reviewed by the desk, so an agent is composing from correct building blocks rather than translating on the fly at midnight.

Accept voice notes both ways. A coordinator who replies to a long voice note with a short spoken answer in the family’s language does more for trust than any brochure. Where you do not have the language in house, bring an interpreter into the workflow rather than leaving an agent to improvise with a translation app. The decision about which languages you can genuinely support belongs with the design of a multilingual international patient desk, not with the channel.

One rule I would not bend: no clinical opinion in chat from anyone who is not a clinician. Agents collect, describe the process and route. They do not interpret a scan, comment on a diagnosis or say whether surgery is needed, however directly they are asked and however long the family has been waiting.

Reports, photographs and the record

Almost every international case begins with medical records arriving as photographs. Blurry, partial, rotated, taken in poor light, sometimes in a language nobody at your desk reads. This is not a problem to complain about. It is the normal condition of the channel, and your process should assume it.

Tell the family exactly what you need, in plain words and in their language: which pages of which report, the most recent ones first, the scan images if they have them on a disc or a portal, and the doctor’s own note. Ask for one file at a time if the connection is weak. Give a simple naming instruction. When something is unreadable, say what specifically is missing rather than asking them to send everything again.

Then get it out of the phone. Every document, and the key facts around it, belongs in the patient record and the CRM, attached to an enquiry that has a source country, a language, a specialty and an owner. This is the unglamorous heart of the thing, and it is why an international desk that runs on your CRM outperforms one that runs on goodwill. A thread on a phone is not a record. It cannot be reported, audited or handed over.

The same applies in the other direction. Documents you send matter: the estimate, the appointment confirmation, admission instructions, and later the discharge paperwork. Send them as proper documents rather than screenshots, because the family will forward them to a sponsor, an employer, a referring doctor or an authority, and a screenshot of a screenshot is worth nothing to any of them.

Handover, which is where most cases are lost

A single international case passes through more hands than a domestic one: first responder, market coordinator, clinical coordinator, the consultant’s secretary, admissions, billing, the arrival team, and after discharge whoever handles follow up. Each handover is a point where the family has to repeat themselves, and each repetition costs confidence.

Fix it with three habits. Keep one thread per case, not one per topic, so the history travels. Introduce the next person inside the thread by name and role before they take over, rather than letting a stranger appear mid conversation. And write a short internal summary at each handover in the CRM, so the person picking it up knows what has been promised without reading forty messages.

Group threads deserve a decision. Families will want the son abroad and sometimes the local doctor in the conversation, which is genuinely useful. It also means clinical and financial information is visible to people who have not consented and may not be entitled to it. My practice is to keep the main thread with the named contact, ask explicitly before adding anyone, and record who is authorised to receive what.

After discharge the thread should not simply stop. The family is going home to a doctor who was not part of any of this, and the handover that matters most is the paperwork: the discharge summary the home country doctor can act on, sent as a document, in a form that travels.

Consent and privacy across a border

Personal and health data collected from a family abroad still sits under your obligations here. Under DPDP you need a stated purpose, a consent you can evidence, a retention position and a way for someone to withdraw. Collect consent in the language of the conversation, in plain words, and log it against the enquiry rather than leaving it in a chat bubble.

Be careful with the ordinary habits of a busy desk: screenshots shared in internal groups, reports forwarded to personal numbers, patient photographs kept on a coordinator’s phone. Those are the breaches that actually happen. Devices used for the channel should be managed, agents should have no ability to export the media library, and access should end the day someone leaves.

Say plainly in the thread what you will do with the reports and who will see them. Families are more willing to share when they are told, and the hospital is in a far better position later if a question is ever asked.

Measuring a channel that does not look like a funnel

Web style metrics mislead here. Sessions and click through rates tell you nothing about a conversation that runs for two months. Measure first response time in the family’s own daytime, not in yours. Measure how many enquiries arrive with usable reports attached, because that is a test of your instructions rather than of your agents. Measure the time from first message to estimate sent, and from estimate to a decision either way.

Then measure the gap everyone avoids: enquiries that produce an estimate but never an arrival, by market and by reason. Some of that is price, some is paperwork, some is a competitor replying faster, and some of it is a family who was never going to travel. You cannot fix it without naming it. Report by source market, never in aggregate, because one market’s pattern says nothing about another’s.

What I would fix in the first week

Move the channel onto one verified business number and take it off personal phones. Rewrite the automatic reply so it states working hours in the family’s time zone and when a human will answer. Publish the number, in international format, on every international page and in every profile. Agree the language cover for your two largest markets and roster to it. Build the first dozen message templates in those languages and have a native speaker check them.

Then make one rule stick: every document that arrives in the thread goes into the record the same day, and every enquiry carries a source country and an owner. That single habit converts a phone full of conversations into something the hospital can manage, report on and improve. Everything else in this article is easier once it is true.

Questions people ask