Patients from Iraq and Yemen: sponsorship, escorts and trust in the process
Patients from Iraq and Yemen usually reach an Indian hospital as a case, not a lead: a sponsor or family fund behind the payment, two or more attendants travelling, and weeks of documents before anyone flies. The desks that win this work hold the file visibly, work in Arabic properly, and put every promise in writing before arrival.
Most international desks in India are built around one traveller with one phone number. Patients from Iraq and Yemen usually arrive as a group instead: the patient, one or two attendants, a relative who speaks the best English or Hindi and does most of the messaging, and somewhere behind all of them a person or an office that has agreed to pay. If your process assumes a single decision maker, it will lose the case somewhere between the first message and the boarding pass.
I have heard these enquiries described as slow, difficult or unreliable. They are none of those things. They are long. A file that has not moved in three weeks is usually not a cold file. It is a file waiting on a report, a translation, a signature or an appointment at an office that is not yours. The desks that do well here stay visibly present across that wait without pestering anyone.
Medical value travel from this part of the world runs on three things: sponsorship, escorts and evidence. Sponsorship, because the payer is often not the patient. Escorts, because nobody travels alone for serious treatment. Evidence, because the family cannot verify a word you say by walking into your building first. Design for all three and the rest of the process gets easier.
What patients from Iraq and Yemen are actually arranging
Before anyone books a flight, a family is assembling four things: a diagnosis they trust, a hospital they can name to relatives, money they can release, and permission to travel. Those four move at different speeds and almost never in order.
The diagnosis usually exists already. Reports have been done at home, sometimes twice, sometimes in two different places, and they reach you as photographs of printouts taken on a phone at an angle, in mixed Arabic and English. Your first job is to make those readable and get a clinician to say something useful about them. The hospital they can name comes from people rather than advertising: a neighbour who travelled, a relative working in another country, a local doctor who has sent cases before. Money is the slowest part and rarely one person’s decision. Permission to travel is paperwork, and paperwork from some places simply takes longer and passes through more offices.
So the enquiry in front of you is not a lead with a decision date. It is a case file that will stay open for weeks, and the family will judge you on whether it feels like somebody is holding it. The most useful change I have seen a desk make is to stop scoring these enquiries by days to conversion and start scoring them by whether the file moved this week, and who moved it.
Sponsorship: the name on the file is not the name on the bed
Payment here comes in several shapes. It may be a public office that has agreed to fund treatment abroad. It may be an employer. It may be a community or family fund collected across several countries. It may be a relative working elsewhere who transfers money in instalments. Each of those behaves differently, and your team needs to know which one it is in the first few conversations, not at the billing counter.
A sponsored case usually comes with a written authorisation of some kind, a defined treatment it covers, and a process for anything outside that definition. What your team must establish is simple and rarely asked: who receives the bill, who approves a change to the plan, how long that approval takes, and what happens clinically while it is pending. A family fund behaves the opposite way. Money arrives in parts, the transfer itself takes time, and the patient may land before the full amount does. Your finance team should have a position on that before the case is confirmed rather than improvising at admission.
One rule I would treat as absolute: never state entry requirements, document lists or sponsorship rules as fact in your content or your chat replies. They change, they vary by case, and a wrong answer given confidently is worse than no answer. Say what the shape of the process is, then tell the family to confirm the current position with the relevant authority and with your own international desk, and make sure the desk actually knows.
Escorts and attendants are part of the case, not around it
Plan for more than one attendant. Frequently there are two, sometimes more, and at least one of them is staying for the whole length of treatment. This is not a preference to be accommodated grudgingly. It is the structure of the case, and it affects your room mix, your food service, your visitor policy, your cashier queue and your discharge process.
Practically: know before arrival how many people are travelling and who among them is the person your coordinator will speak to daily. Know who signs and who pays, because they are often different people. Give attendants somewhere to sleep, somewhere to pray, somewhere to make food or buy food they recognise, and a laundry answer. Long stays turn small gaps into real complaints. The attendant is also the person writing the review, sending voice notes to the extended family, and deciding whether the next relative comes to you or goes somewhere else, which is why I treat the attendant as a customer with a service design of their own.
The other thing attendants need is a predictable day. Tell them when rounds happen, when reports come, when the bill updates, and who to find when nobody answers. Uncertainty is what turns a patient family into a crowd at the nursing station.
Arabic cover that is real, not a line on a brochure
Every hospital brochure claims Arabic support. Few can prove it at nine in the evening on a Sunday. Real cover means a named roster, a defined set of hours, a written escalation when the roster is off, and a way to handle the dialect differences that exist inside any large language. It also means deciding what an interpreter is allowed to do and not do, because an interpreter who starts explaining a treatment is a clinical risk, not a service.
Translate the things that get read: the estimate, the admission instructions, the consent explanations delivered verbally and recorded as delivered, the discharge summary, and the follow-up plan. Do not machine translate a clinical document and publish it. Do machine translate nothing that carries a signature. I would rather a hospital had fewer Arabic pages that were correct than a whole site that reads like it was passed through a plugin.
The economics only work if you stop treating language as a favour asked of whichever staff member happens to speak it. That is how you burn out the two people who do, and how cover disappears the week they take leave. It belongs in a rota with a cost line, which is the argument I make in treating interpreters as a service you can scale.
The wait before the flight, and how to be useful inside it
Between the first enquiry and the flight there is a period where nothing visible happens. Documents are being collected, translated, attested, submitted. Appointments are being waited for. Money is being gathered. Most desks go quiet here because there is nothing to report, and the family reads silence as abandonment.
Fill that gap deliberately. A short weekly message in Arabic that says what you are waiting for, what you have already done, and what the next step will be costs almost nothing and changes the relationship entirely. Keep a single case reference the family can quote. Keep the same coordinator name attached to it. If the coordinator is on leave, say who is covering before the family finds out by not getting a reply.
This is also the period where a pre-travel teleconsultation earns its place. A short conversation with the treating clinician, with an interpreter present, does more for confidence than any amount of content. It also protects you: it surfaces the cases that should not travel at all, before a family spends money getting here. The same discipline applies to long documentation timelines from other markets, which I have written about in the context of families travelling from Afghanistan and the long stay that follows.
Trust is built in writing, before anyone lands
The family cannot inspect you. They cannot ask a colleague to drop in. Everything they believe about your hospital comes from documents, pictures and the behaviour of one coordinator. So write things down.
A written estimate in Arabic and English that states what is included, what is excluded, what would change it and who must approve a change is the single most valuable document your desk produces. Photographs of the actual room category being quoted, not a marketing render, sit beside it. A plain note on how payment can be made, how receipts are issued and how refunds work if the plan changes belongs there too. None of this requires a price claim or a comparison with anywhere else. It requires that what you said in March is still what you say in June.
Verification matters more than persuasion here. Families check what you send with a relative who has travelled, a local doctor, and increasingly with an assistant that summarises whatever it can find about you online. If your written estimate and your public content disagree, you lose. That consistency is the real product, and it is why I think of the international patient funnel as a digital product rather than a brochure.
Routes, seasons and the length of stay you should plan for
Very few of these journeys are a single hop. Most involve a connection, an overnight wait somewhere, and an arrival at an hour when your outpatient block is closed and your best people are asleep. If your airport pickup and your admission desk cannot handle a family landing in the small hours with a patient on a wheelchair, your first impression is made by a security guard who does not speak the language.
Length of stay tends to run long. Treatment plans that involve cycles, staged procedures or a review a few weeks later push the family into a stay measured in months rather than days, often with attendants rotating in and out. That changes what you should have ready: accommodation options near the campus at more than one price level, a way to extend a stay without repeating the whole admission process, and a clear answer on what happens between cycles.
Travel also clusters. School terms, the religious calendar and weather in both countries move volumes around the year in ways your own data will show you if you look. Do not plan staffing off an annual average. Look at arrivals by week for the last two years and staff the peaks.
Where I would start
Start with three small things that do not need a budget approval. First, add two fields to your enquiry record: who is paying, and how many people are travelling. Ask them in the first reply, politely, as part of a normal set of questions. Most desks discover they have never captured either, which is why forecasting arrivals from this market is guesswork.
Second, write one Arabic language estimate template and one weekly update template, have both reviewed by someone who speaks the language natively, and make them the default rather than something a coordinator types fresh each time. Third, put a name and a covering name on every open file, and review open files weekly on one question only: what moved.
Then do the harder thing, which is to agree internally what you will not promise. No entry rules stated as fact, no timelines you cannot control, no clinical expectations before a doctor has seen the reports. A desk that says less and keeps all of it will beat a desk that says everything, every time, in a market where the only thing a family can check is whether you did what you said.
Questions people ask
The case is usually a group rather than an individual, with attendants travelling and a sponsor or family fund behind the payment. Documentation before travel takes longer, so the file stays open for weeks. Arabic cover has to be genuine and rostered, not improvised. The practical difference is that these enquiries need holding over time rather than closing quickly, and they are judged on consistency.
Measure movement, not speed. For each open file, track whether something changed this week and who changed it: a report received, a translation done, an opinion given, an estimate revised. Report arrivals separately from enquiries, and by the month the enquiry started rather than the month of arrival. Otherwise a strong quarter of enquiries looks like a weak quarter of conversions and you draw the wrong conclusion.
Who receives the bill, who approves any change to the treatment plan, how long that approval typically takes and what happens clinically while it is pending. Also whether payment arrives before or after discharge, and what documentation the payer needs to release it. Agree a written position on partial payments and on cases where the plan changes after admission, because both will happen.
Either can work, but the cover has to be rostered and accountable. If you use an external service, define response times, the hours covered, who escalates and how clinical conversations are handled. If you hire, do not let language sit as an extra duty on two people, because it disappears the week they take leave. Whichever route you choose, put the cost in a budget line rather than hiding it.
Two things. First, who may say what before a clinician has reviewed the reports, so nobody on the commercial side sets a clinical expectation. Second, how pre-travel teleconsultations run: which specialties offer them, how an interpreter is used, and how a case that should not travel is declined kindly and in writing. Both protect the patient and the hospital equally.
Less than most people expect, because much of it is process rather than spend: knowing the number of attendants before arrival, a predictable daily rhythm, prayer space, food they recognise, laundry and a place to sleep. The cost that does appear is accommodation support and space. Weigh it against the fact that the attendant writes the review and decides where the next relative in the family goes.
Describe the shape of the process and nothing more. Do not publish document lists, eligibility rules, categories or timelines as current fact, because they change and a confident wrong answer damages you. Say that the current position must be confirmed with the relevant authority and with your international desk, then make sure the desk is trained and reachable. Accuracy is a better differentiator than completeness here.
The international desk owns the case, but it cannot own the outcome alone. Finance owns the payment position, clinical leadership owns what may be promised, facilities owns the attendant experience and marketing owns the content that sets expectations. The useful structure is one accountable owner for the file with a standing weekly review that the other functions attend. Without that, every difficult case becomes a corridor conversation.
Fields that reflect how the case actually works: payer type, number of travellers, language, document status, case reference and covering coordinator. Message history from the channel the family actually uses, held against the same record. Consent captured and stored properly. If your system cannot show one person the whole file in one screen, coordinators will keep a private spreadsheet and your reporting will stay fiction.
Expect a quarter to get the basics honest: fields, templates, a language roster, a weekly file review and an agreed line on what will not be promised. Expect a year before referral patterns respond, because trust here travels between families and doctors rather than through advertising. The early wins are operational, and you will see them in how few cases go silent, not in arrivals.
Often yes, at least partly, because the referral chain is personal and local. The question is what you keep. Keep the estimate, the clinical opinion and the written promises under your control, whoever introduced the case. Keep a record of the patient relationship rather than only the intermediary relationship. A facilitator who brings cases is a channel, and like any channel it needs terms, measurement and a review.
This is where most desks stop and where the next case is won. Send a discharge summary the doctor at home can act on, in a form that travels. Offer a follow-up consultation with an interpreter present. Answer report questions for a defined period afterwards. Families talk to each other across borders, and the case you closed well becomes the introduction you did not have to buy.
Show enquiries, arrivals and the gap between them, with the reason the gap exists rather than an apology for it. Show the length of the file, the share of cases with a sponsor, and what your desk actually controls. Avoid presenting this as a fast growth channel. It is a relationship channel with long lead times, and boards respond well to being told that plainly.
