Hospital CRM readiness checklist

Most hospital CRM projects do not fail at the software. They fail because nobody agreed what an enquiry is, patient records live in five places under three spellings, consent was never recorded, and the system that knows whether a patient actually arrived was never connected. The CRM goes live, the dashboards look empty, and the contact centre goes back to spreadsheets.

This checklist is for the months before you choose anything. It tests whether your data, enquiry capture, consent, integration with the hospital information system, ownership and reporting are ready for a CRM to be useful. If too many answers are no, the right next step is the groundwork, not the purchase.

For marketing, digital, contact-centre and IT leaders deciding whether a hospital or group is ready to implement a CRM.

A CRM vendor demo is a performance. The pipeline is clean, every enquiry has a source, every agent follows the script, the dashboards glow. Nobody in the room is lying; they are showing the product running on data and processes that look nothing like yours. The trouble starts after purchase, when the tool meets your real enquiries, your real contact centre and your real HIS.

That is why I run a readiness check before any vendor gets a demo slot. It is an internal exercise, usually done in a few weeks, that answers a blunt question: if we had the perfect CRM tomorrow, could we actually use it? Most hospitals discover they cannot yet, and that the gaps are in process, data and ownership rather than software.

Demos shape requirements more than requirements shape demos. Once a team has seen a slick product, the feature list starts to mirror what was shown, and questions such as who owns an enquiry at two in the morning, or how a booking gets written into the HIS, never come up. A readiness check reverses that order: you arrive knowing your weak points and ask the vendor to show the product in exactly those conditions. It also protects the budget. A CRM bought before the organisation is ready tends to become an expensive lead inbox, and that failure is usually blamed on the vendor rather than the preparation.

The checklist above follows the same areas, so you can score yourself as you go.

1. The enquiry journeys you actually run

Map how enquiries arrive and what happens to them today: not the SOP, the process on the floor. Sit with the contact centre, the OPD front desk, the health check desk, the international desk and whoever answers WhatsApp, and trace a handful of real enquiries to an honoured appointment or to the point where they were lost. Most hospitals find more journeys than they expected: OPD appointments, health checks, second opinions, admissions and estimates, corporate and TPA enquiries, international patients, home care, pharmacy. Not all of them belong in the first phase. The output is a short document listing the journeys, their owners and which ones the CRM must handle at launch.

In a multi-unit group, repeat the tracing in at least two units. Journeys that look identical on the group SOP often differ sharply between a flagship and a smaller unit in another city, and the smaller units are often where enquiry leakage is worst.

2. Data you have, and data you think you have

For each source (HIS records and appointments, telephony, web forms and chat, the WhatsApp business platform, marketing platforms, sometimes billing and pharmacy) ask whether the data exists, where it lives, how clean it is and whether it can be accessed. The recurring problems are predictable: duplicate patient records across units, phone numbers in different formats, doctor and department names that differ between the HIS and the website, no clean appointment export, and call outcomes recorded nowhere. I sample a small set of records from each source and check them by hand. It is tedious and revealing, and the cleaning work is usually larger than the CRM configuration itself, as I explain in the data work nobody budgets for. Budget it before a vendor quote anchors expectations.

3. Integration with the HIS, telephony and WhatsApp

A CRM that cannot see appointments and arrivals cannot tell you whether an enquiry became a patient. One not connected to the phone system depends on agents typing call notes, which they will not do consistently under pressure. For the HIS, find out what interfaces exist, who controls them, what they cost, how long the HIS vendor takes to deliver changes and whether bookings can be written back from outside. For telephony, check whether calls can be logged against a patient record and outcomes captured with one click. The IT head should own this assessment, with a named person who stays through implementation. Also decide early whether an existing WhatsApp provider stays and connects to the CRM or moves inside it; leaving that open is what causes duplicated conversations and patients hearing from two systems.

4. People, ownership and the contact centre

Software does not own enquiries; people do. Ask who will own each journey, who will manage the contact centre’s daily use, and who will own the system: configuration, users, reports and change requests. A vague mix of marketing and IT is a warning sign. Look honestly at the contact centre: agents, shifts, training, attrition, and whether they are measured on calls handled or appointments booked. Name a business owner before any demo, senior enough to settle arguments between departments and close enough to operations to understand what agents face. Without one, the vendor fills the vacuum, the trap I describe in managing vendors without becoming their project manager.

5. Consent and DPDP

Confirm what notice and consent you collect at each point of contact, where it is recorded, how opt-outs work and who can see what. Questions worth answering before a demo: can you record consent at the point of enquiry, including on calls and WhatsApp? Is there a retention policy for enquiry data that never became a patient? Which roles should see clinical information? How is data shared across units? Compliance and legal own the answers; the growth team drafts the questions. A vendor who cannot show role-based access, consent records, audit trails and deletion workflows on realistic scenarios is not ready for a hospital. The primary text is the DPDP Rules, 2025 (Press Information Bureau).

6. The few measures the CRM must produce

My shortlist starts with enquiry to honoured appointment by channel, specialty and unit; response time by channel and hour; and the reasons enquiries are lost. Write down how each is calculated and which data it needs, then check whether your journeys, data, integrations and people can produce it. This also clarifies what you do not need: many hospitals are sold lead scoring and journey builders when nobody can yet say how many enquiries became patients last month. More in enquiry to appointment: the number that matters.

End with a short readiness summary: journeys in scope, state of the data, integration position, owner and team, consent position and measures required. Score each area plainly as ready, partly ready or not ready, and share it with leadership before you invite vendors. It often changes the timeline, and occasionally the decision to buy at all. Then give every vendor the same scenarios, drawn from your real journeys, and ask them to show the product handling them live:

• A duplicate patient enquiring through a web form and a phone call on the same day.
• A WhatsApp enquiry at night that must reach a named agent by morning with its history intact.
• An appointment booked in the CRM and written into the HIS, then marked as honoured on arrival.
• A patient withdrawing consent, and the CRM suppressing every future message across teams.
• A unit head viewing enquiry to honoured appointment for their unit only.

Vendors who show these on realistic data are worth a second meeting. Those who return to their standard presentation have told you something useful. For the wider buy, build or combine decision, see how I decide on healthtech vendors.

If demos are already booked: a two-week version

In week one, trace real enquiries through two or three of your busiest journeys, sample data from the HIS and telephony, and ask IT for a written view of integration options. In week two, name the business owner, confirm the consent position with compliance, agree the three measures you need and write the demo scenarios. Score yourself on this checklist, share the scores with vendors in advance and ask them to address those gaps in the demo. Whatever you decide, keep the readiness summary: it becomes the first page of the implementation plan, set out in hospital CRM implementation: a phased rollout plan.