Measuring international demand honestly: enquiries, arrivals and the gap between
Measuring international demand honestly means separating three layers: interest, expressed intent and arrivals. Define what an enquiry is before counting one, date it from first contact, flag residence outside India at registration, merge duplicate touches into one case, and report by cohort because international journeys are slow. The gap between enquiry and arrival is a diagnosis, not a failure.
Almost every international desk I have worked with can tell you how many enquiries it received last month. Far fewer can tell you, without a pause and a spreadsheet rebuilt on the spot, how many of those people landed in India and walked into the hospital. Measuring international demand honestly starts with that discomfort, because the two numbers describe different things and only one of them pays for anything.
An enquiry is an act of hope. Someone sent a scan on WhatsApp at midnight from another time zone, or filled a form in a language your team cannot read, or asked a cousin living in Delhi to call on their behalf. An arrival is an act of trust that survived documents, money movement, a flight, a family decision and, almost always, a quotation from at least one other hospital. The distance between those two events is the real subject of medical value travel measurement.
That distance is not a failure to be hidden in a footnote. It is a description of what you are asking a family to do. Read properly, it tells you which part of your process is slow, which promise is not holding, and which market you are serving with a page and a phone number but no actual capability.
What follows is how I would count: what to define before counting anything, why arrival is the unit that settles arguments, where the same patient gets counted twice, and how to write the monthly view so it survives the first question from the finance seat.
What measuring international demand actually means
Demand is not enquiry volume. Enquiry volume is the portion of demand that found you, in a month when you happened to be spending, through a channel you happened to be tagging. A hospital that measures only its own enquiries is measuring its own marketing and calling it a market.
I find it useful to hold three layers apart. There is interest, which shows up as searches, video views, messages and saved contact numbers. There is expressed intent, which is a person with a condition, a country and a way to be reached. There is realised demand, which is an arrival. Each layer is measured differently, and each one answers a different question. Interest tells you whether you are visible where the decision starts. Intent tells you whether your first reply and your estimate hold. Arrival tells you whether the whole promise was deliverable.
My earlier piece on reading international demand from data, not anecdotes is about where to look for the signal in the first place, before a single enquiry reaches your inbox. This article assumes that signal has reached you and asks a narrower question: once demand arrives as messages and calls, how do you count it in a way you would defend in front of a board.
Define an enquiry before you count one
Most international numbers are unreliable for a boring reason. Nobody wrote down what an enquiry is. So the desk counts messages, the marketing team counts form fills, the facilitator counts cases forwarded, and the monthly review becomes an argument about arithmetic rather than about patients.
Write a definition and put it in the CRM as a field, not in a deck. Mine is usually close to this: an enquiry is an identifiable person, with a country of residence, with a stated medical problem or a report attached, and a working way to reach them. A greeting with no content is a contact, not an enquiry. A duplicate message from the same family in the same week is a touch on an existing case, not a new one. A batch of cases forwarded together by a partner is a set of enquiries only if each one carries a real patient behind it.
Then decide the date an enquiry belongs to. The day the first message landed, not the day someone finally opened it. Teams that date enquiries by the day of first response quietly delete their own response time problem, and the whole point of the first reply is that it is the part of the journey you control completely. I have written separately about what a first reply to an international enquiry should contain, and the count only tells the truth if it starts at the moment the family reached out.
Why arrival is the unit that settles arguments
An arrival is a patient from another country who is physically registered at your hospital for consultation, investigation or admission. It is recorded by people who do not report to marketing, in a system that exists for billing and clinical records. That independence is what makes it useful. Nobody can lobby it upwards at the end of a quarter.
Domestically I argue for the honoured appointment as the unit that keeps everyone truthful, and the method in how to calculate cost per honoured appointment transfers with one change: for an international case, the appointment is not the event worth counting, because a video consultation can be honoured from home and change nothing. The travel is the commitment. The money version of this sits in cost per arrived international patient, which takes the same unit and puts spend on top of it.
To count arrivals you need one thing the hospital often lacks: a reliable flag on the registration record for residence outside India, entered at the front desk rather than inferred later from a phone code or a passport photocopy in a drawer. If that field is optional, it will be empty. If it is mandatory and badly designed, it will say the wrong thing. It is worth a week of someone senior sitting with the registration team to get it right, because every other number in this article rests on it.
Reading the gap between enquiry and arrival
The interesting work is not the ratio. It is the shape of the drop. Break the journey into stages that a person can actually observe: first reply sent, medical opinion given, estimate issued, documents requested for travel, payment intent confirmed, travel dates shared, arrival. Then look at where each market stalls.
The patterns repeat. A market that stalls before the medical opinion usually has a language or a specialist availability problem, not a pricing problem. A market that stalls after the estimate is telling you either that the estimate was not believable or that it moved after the family showed it to someone. A market that stalls after the estimate is accepted is usually stuck on paperwork and money movement, which are logistics problems your desk can help with even though they sit outside the hospital. A market where families reach travel dates and then vanish is often losing to a competitor who answered faster on the same day.
Each of those is a different piece of work, owned by a different person. That is the value of stage measurement: it converts a single disappointing ratio into four or five specific tasks. What it will not do is let you rank countries against each other, and the reasons for that deserve their own treatment in why one market’s conversion rate cannot be compared with another’s.
The same patient, counted twice
Duplication is the quiet killer of international reporting, and it inflates the top of the funnel in exactly the way that makes the bottom look weak.
A family rarely uses one channel. The patient’s son messages the number on your website. The patient’s brother in the Gulf fills a form. A partner who has been shown the same reports forwards the case to your desk. The attendant calls the switchboard because the reply has not come. That is one case and four records. If you count four, you have both overstated demand and understated your conversion, and then you will spend a review meeting explaining a problem that does not exist.
The fix is a case identity created at the first contact and matched on the things that are stable: the patient’s name, the country, the condition, and the reports. Match conservatively, review the near matches by hand for a while, and keep a visible merge trail so the desk trusts it. Resist the urge to key everything to a passport or an identity document. You do not need it to run a funnel, storing it creates an obligation you may not be ready to carry, and the compliance line in international patient marketing is easier to hold when you have collected less in the first place.
Lag, cohorts and the month that lies
An international journey takes longer than a domestic one, and the length varies by market because documents and travel do. So the arrivals you record this month mostly answer a question you asked with spend some months ago. Dividing this month’s arrivals by this month’s enquiries produces a number that is not wrong so much as meaningless.
Report by cohort instead. Take the enquiries created in a month, follow that group forward, and show how it matures. The current month will always look poor and everyone should expect it to. Older cohorts settle. When you present, say plainly which cohorts are still open and which have closed, and let the closed ones carry the argument.
Cohorts also protect you from a common misjudgement. A campaign that looks weak in its first weeks may simply be reaching families at an earlier stage of their decision, and a channel that looks strong may be collecting people who were already coming. Give the cohort time before you move the budget. The discipline is the same one I use for any slow-cycle demand, and international demand is the slowest cycle most hospital marketing teams will handle.
The demand that never shows up in the CRM
Some of your international patients were never enquiries at all. A visitor already in India for a wedding develops chest pain and walks in. A relative settled here arranges everything and never touches a digital channel. A patient you treated two years ago returns for follow up and goes straight to the consultant’s secretary. A doctor abroad sends a case directly to a surgeon he trained with. None of these reach the desk as an enquiry, and all of them are real medical value travel volume.
If you ignore this, two things go wrong. Your arrival count is lower than the truth, which makes every cost number look worse than it is. And you lose sight of the referral routes that are actually working, because they are invisible by design.
The repair is mostly human. Ask the origin question at registration, in words a clerk can use without embarrassment, and let it be answered as free text if that is what it takes. Have the desk log every case it touches, including the ones that arrived without warning. Give consultants a simple way to hand a case to the desk without feeling they are handing over the relationship. A desk that runs on your CRM can absorb these cases; a desk that runs on a shared inbox and goodwill cannot.
What I would fix in the first month
Start with definitions, because everything else is downstream of them. Then fix the two data points that cannot be reconstructed later: the date of first contact and the flag for residence outside India.
- Write one page that defines an enquiry, a qualified case, an arrival and a duplicate, and get the desk, marketing and finance to sign it.
- Make the residence field mandatory at registration and sit with the front desk while they use it for a week.
- Create one case identity per family and merge the touches into it.
- Publish a cohort view of enquiries by month of first contact, marked open or closed.
- Name one owner for the number, and let that person present it every month whether it is flattering or not.
Expect the first honest report to be worse than the one it replaces. That is the point, and it is worth saying out loud to the leadership team before you circulate it, not after. The count you can defend is more useful than the count that pleases, because only the first one tells you what to build next.
Questions people ask
Measuring international demand means counting the interest, the expressed intent and the arrivals that a hospital receives from patients living outside the country, using definitions everyone has agreed in advance. It separates enquiry volume, which reflects your own marketing and tagging, from realised demand, which is a patient who actually travelled and registered. The gap between the two is read as a diagnosis rather than hidden as a failure.
An enquiry only records the part of demand that found you, through channels you were spending on and tagging, in the window you were looking. It is inflated by duplicates when one family uses several channels, and it says nothing about whether your estimate held or whether the family could travel. Two hospitals with identical enquiry counts can have very different arrival counts and very different economics.
Arrivals by month of first contact, with the stage where cases stalled shown alongside. That one view tells you whether demand is growing, whether the desk is converting it, and which part of the journey needs work. Enquiry volume alone will push your team towards collecting more messages. Arrivals push them towards finishing cases, which is the behaviour you want from an international desk.
A count that can be reconciled with the hospital information system rather than one that lives only in a marketing tool. Arrivals are recorded at registration by people outside the marketing line, so the number survives scrutiny. It also lets finance see the lag between spend and revenue for international work, which is longer than for domestic demand and affects how the year is phased.
Create one case identity at first contact and attach every later touch to it, matching on patient name, country, condition and the reports shared. Review near matches by hand until the team trusts the rule, and keep a visible record of merges. Count cases, not messages. Avoid building the match around identity documents, because collecting those creates obligations you may not be ready to meet.
Country of residence rather than nationality, because a patient may hold one passport and live somewhere else entirely, and the marketing question is about where the journey started. Make the field mandatory, keep the list short enough to use quickly at a busy counter, and add one free text question about how the family reached the hospital. Train the counter staff rather than relying on the form alone.
It should barely touch them. The measurement sits in registration and in the desk workflow, not in the consultation. What clinicians gain is a clearer picture of which conditions travel to them and where cases fall away before arrival, which helps in planning slots and second opinion capacity. Nothing in this measurement asks a clinician to promise an outcome or to alter a clinical decision.
Less than most teams fear. A residence field on the registration record, a case object in the CRM that can absorb several contacts, a first contact timestamp that cannot be edited, and a scheduled extract that joins the two systems on a shared key. The hard part is agreeing the key and the definitions. Once that is settled, the reporting itself is routine work.
Allow one full quarter. The first weeks are spent fixing definitions and registration behaviour, the next weeks produce a count that still disagrees with the old one, and by the end of the quarter you have closed cohorts to compare. Anyone promising a clean view within weeks has not tried to reconcile a hospital system with a CRM while both are being used every day.
Meaningful at first and small afterwards. Logging every case, including walk ins and consultant referrals, feels like extra work until the desk sees its own load reflected honestly for the first time. Most teams find the discipline pays for itself because it ends the argument about whether the desk is busy, and it gives the desk a way to ask for people with evidence.
A tool can hold the data, but the definitions have to be yours and the ownership has to sit inside the hospital. I would ask any vendor to show how their system handles one family contacting through several channels, how it stores a first contact date, and how it exports so that your own analyst can rebuild the numbers independently. If the answer is a dashboard you cannot audit, keep looking.
One page. Arrivals by cohort, the stage where cases stall, the markets showing a change in direction, and a short note on what is being fixed. No league tables of countries, because the mix of specialties, payment routes and travel conditions behind each market is different. Boards respond well to a number that is presented with its own caveats attached.
They count as arrivals and should be logged as cases even though no enquiry preceded them. Visitors already in the country, relatives who arranged everything locally, returning follow up patients and doctor to doctor referrals all arrive this way. Leaving them out makes acquisition cost look worse than it is and hides the referral routes that are quietly working best for you.
The first report usually looks worse than the one it replaces, so brief leadership before circulating it. After that it protects the team, because a count that reconciles with registration cannot be argued away in a review. Teams that measure arrivals tend to get better resourcing conversations, since they can show exactly which part of the journey is losing families and why.
