An international desk that runs on your CRM

The international desk at most Indian hospital groups runs on phones. Not the group’s phones — the coordinators’ own, with the facilitators’ numbers saved under nicknames, the patients’ reports in the photo gallery, and the estimates as screenshots. When a coordinator goes on leave, the patients wait. When she resigns, a facilitator’s entire book of enquiries walks out of the building with her, and the group finds out when the admissions stop.

I have made the case for moving this onto the CRM three times, in three different rooms. Twice it was approved and stalled within a quarter, because the system was imposed on the desk and the desk quietly went back to the phones. The third time it held, and the difference was not the software. It was that the system was built to serve the relationships the desk already had, and the people in those relationships could see what they were getting for it.

This is a business that runs on trust between a coordinator in Hyderabad and an agent in Dhaka or Baghdad or Nairobi. You cannot replace that with a workflow. You can put a workflow underneath it, so that the group owns what the trust produces.

What the desk runs on today, honestly

Before designing anything, sit with the desk for a week and write down what actually happens. The picture is consistent across groups.

Enquiries arrive on messaging apps, addressed to a person, not a hospital. Reports arrive as photographs. The coordinator forwards them to a consultant on the same app; the consultant replies with a line or two; the coordinator turns that into an estimate on whatever template she has to hand, often one she inherited, and sends it back. The visa invitation letter is drafted by whoever is free and signed by whoever is in. The facilitator negotiates the estimate, sometimes with two or three hospitals in parallel. Nothing is logged until the patient is registered, at which point the domestic system takes over and the international history is lost. Commission is reconciled at month-end from a spreadsheet nobody else sees.

None of this is laziness. It is what a relationship business builds when nobody gives it anything better, and it works — until concentration, leave, resignation or a billing dispute reveals that the group never owned any of it.

Lead ownership comes first

The foundational question is who owns the lead: the hospital or the facilitator. In practice the facilitator owns it, because he found the patient and he is the one the patient trusts. That will not change. What can change is that every lead, whatever its source, exists as a record in the group’s CRM from the moment it arrives, with the facilitator attached as the source and the coordinator attached as the owner inside the hospital.

This sounds administrative and it is the whole point. A lead in the CRM has a status, a timestamp, a specialty, a country, a consultant, an estimate version and an outcome. Ten of them are a caseload. Five hundred of them are a demand map. A year of them is the evidence that decides which markets get language hires and which facilitators get renewed. Without the record, the international business is unmanageable at group level, whatever the individual coordinators achieve.

The rule I have insisted on is simple: no estimate, no visa letter and no consultant opinion is issued for a patient who does not exist in the system. It is unpopular for about a month. Then the coordinators discover that the system remembers things their phones did not.

Multilingual response as a product requirement

A desk that serves Bangladesh, Iraq, East Africa, the Gulf and Central Asia needs Bengali, Arabic, Swahili, French and Russian, and needs them during those markets’ working hours, which do not match Hyderabad’s. Most desks handle this by hiring a few native speakers and relying on the facilitators for the rest, which is one more way the facilitator ends up owning the relationship.

Treating language as a product requirement changes the design. The messaging channel is a group-owned business account, staffed by a roster that covers each language in its market’s day. Templates for the standard messages — acknowledgement, reports received, opinion ready, estimate attached, letter issued, arrival instructions — exist in each language, approved once, reused always. Translation tooling sits inside the CRM for the non-standard messages, with a native speaker reviewing what goes out for anything that touches the clinical opinion or the money. The consultant’s video opinion is subtitled or interpreted, not left in English for the family to guess at.

The contact centre, which the growth function already runs for domestic enquiries, is the obvious home for the first-response layer. The international desk resisted this in every group I have seen, on the grounds that its patients are different. They are. The acknowledgement message is not.

Document workflows and the privacy problem

An international patient’s file, before arrival, is a passport scan, a set of reports, sometimes imaging, a visa letter and an estimate. Today it lives in a photo gallery and a chat thread. That is a data protection problem the group has not yet been asked about, and it will be.

The workflow is not complicated. Documents received on the messaging thread are captured to the lead’s case file automatically, not forwarded. Consultants review from the case file, on a link, and record the opinion there, so that the estimate is built on a written opinion rather than a remembered chat. Visa letters are generated from the record — the patient’s name spelt as the passport spells it, the procedure as the consultant recorded it, the attendant named — and signed through a defined authority, with turnaround measured in hours. Access is by role. When the coordinator leaves, her access ends and the files do not.

The turnaround of the visa letter is worth singling out, because it is the conversion event. A family choosing between two hospitals will often go with the one whose letter arrived first. A desk that can issue a correct letter within a day of the estimate being accepted has a commercial advantage that no facilitator relationship can match.

Quote governance

The estimate is where the international business makes or loses its reputation, and it is where the desk has traditionally had the least governance. Coordinators quote from memory. Facilitators quote lower to win the patient. Consultants quote a package price the billing system does not recognise. The family arrives with one number and leaves with another.

Governance is a small set of rules, enforced by the system rather than by memos:

• One estimate template per procedure, maintained with finance, with inclusions and exclusions written in plain language and translated.
• Estimates generated from the template inside the CRM, versioned, so that what was sent to the patient is what the hospital can see.
• A defined authority for variation. A coordinator can issue the standard estimate. A discount beyond a threshold needs the international head. Beyond that, the unit head.
• Estimate-to-final-bill variance tracked on the international dashboard by procedure, by coordinator and by facilitator, reviewed monthly.
• A documented conversation at admission that walks the family through what could change the number.

The variance number is the one to take to the CFO. It converts a reputation problem into a finance problem, and finance problems get fixed.

The commission conversation

Facilitators are paid, and the payment has historically been opaque — rates negotiated individually, reconciled from a private spreadsheet, occasionally paid to people who did not appear on any agreement. The opacity is a legal exposure, a margin leak and a governance failure, and it is the part of this project that the international head will least want to discuss.

The conversation goes better when it is framed as protecting the facilitators rather than policing them. Every facilitator on a written agreement, with a rate schedule by procedure or by a share of a defined base, and with an expectation of conduct that includes accurate representation of the estimate. Commission calculated by the system from the lead record and the final bill, visible to the facilitator through a portal or a monthly statement, and paid on a schedule. Disputed cases surfaced and resolved rather than settled in cash.

The good facilitators want this. They have been chasing payments and arguing about which patients were theirs for years, and a hospital that pays accurately and on time is one they will send to first. The ones who resist are usually the ones whose numbers do not survive daylight, and the group is better off knowing that.

The line that has to be held is the same one as in the domestic referral business: the arrangement is a commercial contract for a service, disclosed and documented. It is never a payment for a clinical decision, and the consultants are never part of it.

Moving the relationships without losing them

Every failed version of this project I have watched failed the same way: the system was designed for the group and imposed on the desk, and the desk experienced it as surveillance. The coordinators lost their autonomy, the facilitators lost their direct line, and both went back to the phones within a quarter.

The version that held gave each party something they wanted before it asked for anything.

The coordinators got templates in their languages, a case file that survived their leave, a letter that generated itself, and an estimate they could issue without waiting for a consultant to reply on chat. The facilitators got a portal showing the status of every patient they had sent, faster visa letters, and a commission statement they could reconcile. The consultants got a written opinion workflow that took less of their time than the chat did. The international head got a dashboard showing his business by market and by source, which he took to the executive committee himself.

The group got the record. That was the price, and once everyone else had been paid in service, nobody argued about it.

The order of operations

1. Spend a week with the desk. Document how a lead actually moves, in their words, before proposing anything.
2. Move the messaging channel to a group-owned business account, logged to the CRM, with every coordinator on it. Do this first and alone; it is the foundation for everything else.
3. Make the lead record mandatory: country, specialty, source, coordinator, consultant. No estimate or letter without one.
4. Build the estimate templates with finance and the variance number on the dashboard.
5. Automate the visa letter from the record and measure its turnaround.
6. Put every facilitator on a written agreement and move commission calculation into the system.
7. Give the facilitators a portal or a statement. Give the coordinators the templates and the case file. Give the consultants the opinion workflow.
8. Only then, add the source-market content and the direct channel, so that the system you have built has a funnel of its own to run.

Two quarters of this and the international business becomes something the group can manage — by market, by facilitator, by margin — instead of something it hopes continues. The relationships will still matter. They will simply belong to the hospital as well as to the people who hold them.

The phones were never the problem. The problem was that the hospital was not on them.

Questions people ask