NRI patients: the parent in India and the child paying from abroad

With NRI patients the person treated and the person paying sit in different countries. Hospitals lose these cases to slow written replies, verbal estimates, payment paths that reject foreign cards and older patients used as messengers. Tag by where the decision sits, hold patient, decision maker and payer as linked contacts, put the plan in writing and name one owner for the payer relationship.

The enquiry usually arrives at an odd hour. A daughter in another country has spent her evening reading about her father’s condition, collected two hospital names from friends, and filled in a form on a hospital website at what is the middle of the night in India. Her father, in a city some hours from that hospital, does not yet know she has written. Whoever picks up that form is dealing with two people at once: the person who will be treated, and the person who will decide, pay and worry from a distance.

Most hospitals in India file this under NRI patients and then hand it to whichever desk happens to be free. The international desk is built for someone flying in with a passport and an entry question. The domestic funnel is built for someone who lives nearby, calls, comes and pays. The diaspora case sits between the two and inherits the weaknesses of both.

Medical value travel is usually described as foreign nationals flying into India for treatment. This is the mirror image of it. The decision, the money and the scrutiny travel; the patient stays where they are. It deserves its own design, because nearly every step that fails here fails for a reason you can fix with process rather than with more advertising.

What follows is a growth and digital view of that process. The clinical decisions belong to the treating doctors and nothing here touches them.

Why NRI patients need a funnel of their own

Start with how these cases get recorded, because that is where the neglect begins. If the son abroad fills the form, the enquiry is often tagged international because of the phone number. If the father calls himself, it is logged as an ordinary local enquiry. The same case looks like two different things depending on who typed first. Nobody reports the segment, so nobody owns it, and the few steps that are specific to it never get built.

The tag that matters is not where the patient lives. It is where the decision sits. A case where the person choosing and paying is in another country behaves differently from a local admission in every way that counts. It takes longer. It involves more people. It demands far more in writing. It carries a different kind of brand risk, because diaspora communities are small and talkative, and a family that felt badly handled says so in a group that contains a great many future enquiries.

There is a measurement reason too. Buried inside domestic enquiries, these cases make your conversion look weak and your response time look acceptable, and both readings are wrong. Pull them out, report them as a group, and the specific failures become visible. The international patient funnel is a digital product, and the diaspora version of that product is one most groups have not built.

Two customers, one record

There are two people to serve and they want opposite things. The parent in India usually wants a phone call, in their own language, from someone who sounds patient and knows their name. They want to be told when to come and what to bring. The child abroad wants documents. They want the proposed plan in writing, a named person with a working window, a way to see reports without asking, and confirmation that something happened rather than an assurance that it will.

Serve only one and you lose the case. Serve the child and the parent feels talked over, which matters both as a matter of respect and because the parent can withdraw at any point. Serve the parent alone and the payer abroad is left with a second-hand account from someone who does not want to worry them.

In practice this is a data model question before it is a service question. One case record, with the patient, the decision maker and the person paying held as separate contacts with a stated relationship, and consent recorded for who may be told what. That last part is not a formality. Indian data protection rules are getting stricter about purpose and consent, and sending clinical detail to a relative simply because they are paying is not something you want to be improvising at the counter. An international desk that runs on your CRM is the difference between this being a policy and it being whatever the coordinator remembers.

One rule keeps the rest simple. Never make the elderly patient the relay. Do not send the estimate to the parent and expect them to forward it to the person paying.

Time zones are a staffing decision, not a scheduling excuse

The hours in which both parties are awake are narrow, and for some source countries they barely exist. Enquiries land when the Indian desk is closed. By the time someone replies, the family has often written to two other hospitals as well, and whoever answered first with something useful has set the terms.

Three things fix most of this, and none of them need a night shift. The first is a written first reply that is complete rather than prompt and empty: what you understood, what you need, what happens next, who owns it and when they will be in touch. The second is offering a call at a stated time in the caller’s local time, rather than asking a person half a world away to ring during office hours. The third is a handover note, so the next person does not restart the conversation from the beginning. The first response carries more weight in this segment than in any other, which is why what goes into the first reply is worth writing down as a standard rather than leaving to the confidence of whoever is on duty.

If you do run extended cover, be honest about the window and hold to it. A stated window that is always met beats a promise of constant availability that is met about half the time.

Put everything in writing, because the payer cannot walk in

A local family can read a face. They can see the ward, watch how staff speak to each other and decide, correctly or not, that this feels safe. The person paying from abroad has none of that. What they have is whatever you put in writing, so the written artefacts are the product.

That means a plain explanation of the proposed pathway, what the admission involves, roughly how long it takes, what the patient will need at home afterwards and who to ask when something is unclear. It means an estimate that states what is included, what is not and what would change it. It means named, properly labelled attachments rather than photographs of paper taken on a phone.

Assume every document you send will be forwarded to a doctor the family knows in their own country. That is not a threat, it is normal caution, and it tells you how to write. Marketing language does not survive that reading. A document that explains itself does. I would rather a hospital sent a sober, slightly dull summary that another clinician can follow than a designed brochure with the substance removed.

Money crosses the border before the patient moves

The question the payer asks early is simply how to pay from where they are, and it is answered badly more often than anything else. Forms that demand an Indian mobile number for a one-time password. Payment pages that quietly decline foreign cards. No way to get a receipt in the payer’s name. No clarity on whether the person paying and the person admitted need to be linked on the paperwork at all.

Currency makes it worse. The family thinks in their own currency, the hospital quotes in rupees, and between the quoted figure and the amount that actually leaves their account sit conversion and bank charges that the hospital does not control. Saying so plainly, in advance, costs nothing and prevents the argument at discharge. Quoting a convenient foreign currency equivalent that you cannot hold to is the opposite: it feels helpful and creates a dispute. I have written separately about handling money before arrival honestly, and everything there applies with more force when the payer will never stand at your billing counter.

The related trap is the unused advance. Treatment plans change, stays get shorter, and a refund that takes an unexplained length of time to reach a foreign account will undo good clinical care in the family’s memory. State the process at the start, in writing, and name the person who tracks it.

The parent who will not tell anyone something is wrong

Older patients in India frequently minimise. They do not want to worry the child, they do not want to be trouble, and they will describe a difficult week as fine. The consequence for a hospital is that service problems stay invisible until they appear in a review written by someone who was never in the building.

So you cannot rely on the patient raising a hand. You have to go and look. A short daily contact from a named person who speaks the patient’s language, a brief written update to the person paying, and one question asked directly rather than generally. Not how are you finding it, which gets a polite answer, but whether anyone explained today’s plan and whether they have everything they need for the night.

There is a dignity point underneath the process point. The patient is the patient. Consent, explanation and choice belong to them, even when the money and the booking came from abroad. Talking past an older person to a relative on speakerphone is the kind of small failure that a family remembers long after they have forgotten the bill.

The attendant question is real here too. The relative in India who stays may be a cousin, a neighbour or a paid attendant, and the person paying will want to know who is actually in the room. The same care that goes into the experience of the family member who stays applies whether that relative flew in or drove two hours.

After the person paying flies home

Many of these cases involve the child flying in for the procedure week. That creates a scheduling conversation most hospitals pretend is not happening: the family is trying to fit a date to a flight and a limited period of leave. Either the desk acknowledges that openly and works with the consultant’s list, or the family rearranges everything themselves and blames you for the churn.

The week is the short part. The long part is what happens after the payer goes back. The parent stays in India, follow-up happens at a distance from the decision maker, and the hospital’s job is to keep proof flowing: reports available without a request, the discharge summary written so that another doctor can act on it, a follow-up appointment made before discharge rather than promised, and a clear route back to a human being. Where a review does not need the patient physically present, a scheduled remote consultation is usually the difference between a follow-up that happens and one that quietly does not.

This tail is also where the next case comes from. Diaspora referral runs on completed stories, not on advertising, and the story is completed by the follow-up rather than by the surgery.

Where to start on Monday morning

Pick one week and read every enquiry where the caller or the form filler was outside India but the patient was not. You will not need a report to find them; the contact centre knows exactly which ones they are. Read the full thread of each, including what was sent and when. That reading will tell you more than any dashboard.

Then change three things. Add a field that records where the decision maker sits, so the segment stops hiding inside domestic numbers, and make it mandatory at capture. Write one standard written reply for these cases and have it approved by the international desk and by finance, so the first response is complete without anyone improvising. Name one person who owns the payer relationship for each case, with a stated working window in the payer’s time.

After that, test your own payment and enquiry paths the way an outsider would. If your enquiry form cannot be completed without an Indian mobile number, nothing else you do in this segment matters very much. A basic pass through a CRM readiness check will usually surface the rest: missing consent capture, no relationship field, no way to attach documents to a case, no ownership after discharge.

None of this is expensive. It is the ordinary work of treating two people as one case and writing things down. The groups that do it well are not the ones with the largest international marketing budgets. They are the ones that decided this was a segment with an owner, rather than an accident that keeps happening at two in the morning.

Questions people ask