Implementing CRM across a multi-hospital group: lead ownership, call-centre routing and attribution
Reviewed on by Gaurav Phogat. Rules and figures checked against their original sources on the same date.
A multi-hospital CRM succeeds or fails on three decisions that a single hospital never has to make: who owns a lead when a patient touches two units, how the call centre routes an enquiry between them, and how a treated patient is credited back to the channel and the unit that earned it. Get those three written down before go-live and the software becomes the record everyone trusts. Leave them to be “sorted out in the pilot” and they become the reason units keep their own registers.
This article is part of the healthcare digital growth series, best read in order from the pillar.
Last updated: 14 October 2026.
My phased plan for hospital CRM implementation covers the sequence: data model, pilot unit, rollout. This piece goes into the three group-level rules that sit underneath it. They are less about software and more about the agreement between central marketing, the contact centre and the unit heads.
Key facts at a glance
| Decision | What to agree | Who signs off |
|---|---|---|
| Lead ownership | One owner at every stage, a response window for each, and a rule for every cross-unit case | Group growth head with unit heads |
| Call-centre routing | Which enquiries the central desk closes, which it hands to units, and how handover is confirmed | Contact centre head and unit operations |
| Attribution | One source taxonomy, credit at the treated-patient level, and a split between central and unit spend | Growth head and finance |
| Data quality | Weekly exception report by unit: missing source, duplicates, stuck stages, missing consent | CRM lead |
Why a group is not just a bigger hospital
In a single hospital, an enquiry has one possible destination. In a group, the same patient can search the brand, call the central number, message a unit’s WhatsApp, and walk into a different unit than the one they enquired about. Each of those touches creates a record, often in a different system, and each unit believes the patient is theirs.
Three things go wrong as a result. Leads get worked twice or not at all, because two teams think the other is calling back. Units hoard enquiries rather than passing them to a sister hospital with an earlier slot, because their targets reward their own footfall. And central marketing cannot prove its contribution, because the treated patient shows up in a unit’s billing with no link to the campaign that found them. The multi-unit funnel piece shows how averaging those units hides the problem. The fix starts with ownership.
An illustrative example: a patient in the west of a city fills a cardiac form on the group website, gets a callback from the central desk, is booked at the flagship, then walks into the newer unit two kilometres from home because a relative works there. Without ownership and identity rules, the flagship logs a no-show, the newer unit logs a walk-in, and the cardiac campaign gets no credit. With them, it is one patient, one journey and one credited source.
Lead ownership: the rules to write down
Ownership means one named team or person is accountable for the next action on a lead, with a clock running. It does not mean the unit that “gets the revenue”. Separating the two is what stops the turf war.
The default rules
- The central desk owns every new enquiry until first contact. Whatever the channel, the clock starts at capture and the contact centre is accountable for the first response.
- Ownership passes to a unit only when an appointment is booked there, or when the enquiry needs a unit-specific conversation such as a surgical estimate or a second opinion.
- The patient’s choice beats the campaign. If a patient wants the unit near home, they go there, even if the campaign was paid for by another unit.
- Doctor-led enquiries follow the doctor’s slot, not the doctor’s base. Senior consultants who practise at two units are booked where the earliest suitable slot is, unless the patient asks otherwise.
- International, corporate and insurer-referred enquiries have their own owner at group level, because they need specialist desks and their own response windows.
The cross-unit cases
Most disputes come from a handful of situations. Write a rule for each before go-live, not after the first escalation.
| Situation | Ownership rule |
|---|---|
| Same patient enquires at two units | Merge on identity; the earlier open record owns until booking |
| Patient books at one unit, attends another | The attending unit owns the visit; the original source keeps the acquisition credit |
| Unit cannot offer a slot within the patient’s window | Contact centre offers the nearest sister unit; refusal to release is escalated daily |
| Repeat patient enquires about a new specialty | Treat as a new enquiry for routing; keep the patient history visible |
| Lead untouched past its response window | Auto-reassigned to the overflow team, flagged on the unit’s weekly report |
Response windows should be set by enquiry type, not one number for all. A chest pain call needs a different clock from a health check query. Measure them at unit and shift level, because averages hide the evening shift where most leads die.
Call-centre routing: central, unit or hub and spoke
There are three workable models, and most groups end up with the third.
| Model | Works when | Breaks when |
|---|---|---|
| Fully central | Units are in one city and offer similar services | Patients need local language, local directions or a unit-specific estimate |
| Fully unit-run | Units are far apart with distinct catchments | Nights, weekends and overflow; no group view of demand |
| Hub and spoke | Central desk answers and books; unit desks handle estimates, admissions and follow-up | Handover is not confirmed, so leads fall between the two |
Routing rules that hold up
- Route by need, then language, then location. An IVR or WhatsApp menu that asks specialty first and language second gets patients to a capable agent faster than one that asks for the unit.
- Use a tracking number per unit and per major campaign. Each number carries its source into the CRM automatically, which is what makes attribution work later.
- Skills-based queues for high-value lines. Oncology, cardiac surgery, IVF and international patients go to trained agents, not the general queue.
- Warm handover, confirmed in the CRM. When the central desk passes a lead to a unit, the unit must accept it within a set time or it bounces back. No acceptance, no transfer.
- After-hours capture with a morning queue. Every enquiry after the desk closes gets an instant acknowledgement and lands at the top of the first shift’s list. The after-hours enquiry problem has the detail.
- WhatsApp routed like calls. Unit WhatsApp numbers should sit in the same CRM inbox with the same queues, not on a coordinator’s personal phone.
Slot visibility is the routing input most groups miss. If the central agent cannot see doctor availability across units, they cannot offer the sister hospital, and the patient goes to a competitor who can see them on Thursday. Connecting appointment data from each unit’s hospital information system is not optional for a group CRM.
Attribution: crediting the treated patient
Attribution in a group has two questions, not one: which channel found the patient, and which budget paid for it. Mixing them is why central marketing and units argue about every number.
One taxonomy for the whole group
Every source and campaign has one name, set centrally, used by forms, tracking numbers, WhatsApp entry links, agencies and the desk. Desk staff choose from a fixed list rather than typing. Without this, “Google”, “google ads”, “GA” and “online” become four sources and nothing reconciles.
Credit at the treated patient, not the lead
Link the CRM record to the hospital information system through the patient’s registration ID, so a lead can be traced to an attended visit and a bill. Then report cost per treated patient by source and unit. Lead counts flatter channels; cost per treated patient does not. Feeding booked and treated outcomes back to ad platforms through offline conversion import makes bidding learn from patients, not form fills.
Splitting credit between centre and unit
I keep the rule simple: the original source keeps acquisition credit, and the attending unit gets the patient for revenue. Central marketing is judged on treated patients across the group from its spend; each unit is judged on conversion from enquiries it owns and on patients it treats. A sister-unit referral counts in the receiving unit’s revenue and as a “released” lead for the sending unit, so releasing a patient never looks like failure.
What to do with walk-ins and “heard from a friend”
A large share of treated patients will have no digital trail. Ask the source at registration from the same fixed list, and match phone numbers against recent enquiries before accepting “walk-in”. You will find a meaningful share of walk-ins enquired first. The attribution piece covers the limits of what you can know.
Incentives decide whether the rules survive
Rules on paper lose to targets in practice. If a unit head’s bonus rests only on their own footfall, they will not release a patient to a sister unit. If contact centre agents are paid on bookings, they will book anything, including slots the patient will not attend.
Align the incentives with the rules. Reward agents on honoured appointments, not bookings. Give units credit for released leads. Hold central marketing to treated patients and cost per treated patient across the group. Publish response times by unit and shift where every unit head can see them.
Governance and the weekly view
A group CRM needs one owner for the data model, ownership rules and source taxonomy, and a champion in each unit who owns local data quality. Changes to stages, ownership rules or sources go through the group owner; local journeys and languages can sit with units.
The weekly view should fit on one page per unit: enquiries captured, share answered within the window, leads reassigned, leads released to sister units, booked, honoured, treated, and data-quality exceptions. That is enough to run the business, and short enough that people read it.
A ninety-day sequence
- Weeks one to three: agree ownership rules, the cross-unit cases and the source taxonomy with every unit head in the room. Sign them off.
- Weeks four to six: set up tracking numbers, queues, handover acceptance and WhatsApp routing for one pilot unit and the central desk.
- Weeks seven to nine: connect appointment and billing data, start the treated-patient match and the weekly exception report.
- Weeks ten to twelve: review disputes and reassignments, fix the rules that failed, then add the next unit.
The software choice matters less than this agreement. Use the hospital CRM vendor scorecard to test vendors against your rules, not their demo.
Sources and further reading
- Google Ads: About offline conversion imports: sending booked and treated outcomes back to Google Ads.
- WhatsApp Business Messaging Policy: opt-in and messaging rules for unit and central numbers.
- DPDP Rules, 2025 (Press Information Bureau): consent and retention duties that shape the CRM record.
Questions people ask
Agree three group-level rules before go-live: who owns a lead at each stage, how the call centre routes and hands over enquiries between units, and how treated patients are credited to sources and budgets. Then pilot with one unit and the central desk before rolling out.
The central desk owns every new enquiry until first contact. Ownership moves to a unit when an appointment is booked there or a unit-specific conversation is needed. Ownership means accountability for the next action, not credit for revenue.
Merge the records on identity, usually mobile number plus name and date of birth. The earlier open record owns the lead until booking, and the attending unit owns the visit.
Most groups do best with hub and spoke: the central desk answers and books, while unit desks handle estimates, admissions and follow-up. It only works if every handover is accepted in the CRM within a set time.
Route by clinical need first, then language, then location. Use tracking numbers per unit and campaign, skills-based queues for high-value specialties, confirmed warm handovers and an after-hours queue.
Give units credit for leads they release to sister hospitals, auto-reassign leads that pass their response window, and publish response times and releases by unit every week.
Separate the two questions. The original source keeps acquisition credit; the attending unit gets the revenue. Report cost per treated patient by source and unit, linked through the patient’s registration ID.
Ask the source at registration from a fixed list and match phone numbers against recent enquiries before accepting walk-in. A meaningful share of walk-ins turn out to have enquired first.
Contact-centre telephony, every WhatsApp number in the group, website forms and chat, campaign tracking, and appointment and billing data from each unit’s hospital information system.
On honoured appointments rather than bookings, so agents do not fill slots patients will not attend. Track show rates by agent alongside response times.
For each unit: enquiries captured, share answered within the window, reassigned and released leads, booked, honoured, treated, and data-quality exceptions. One page per unit is enough.
A group growth or digital head owns the data model, ownership rules and source taxonomy. Each unit has a champion for local data quality, and IT supports integration and security.
Plan around ninety days to agree rules and prove them in one unit with the central desk. Later units move faster because they reuse the same rules, queues and reports.
Cost per treated patient by source and unit, the split between central and unit spend, and proof that released leads were treated inside the group rather than lost to competitors.
Read my takes first in Google Search
