By Rohit Gupta, Co-Founder, Business & Growth (/about/rohit-gupta) Reviewed by Abhash Kumar, Co-Founder, Strategy (/about/abhash-kumar)
Neither the author nor the reviewer is a clinician; this is a strategy and compliance review, not a clinical sign-off. Last verified 2026-07-26.
This is a buyer's guide to the kinds of healthcare CRM that clinics and hospitals in India actually evaluate in 2026, including AtomCRM, which ICG builds and sells. Rather than scoring individual vendors, it groups the market into five categories, explains where each one fits, and gives you the ABDM, DPDP Act 2023, WhatsApp, multi-location and migration questions to put to any vendor on your shortlist. ICG sells one of the options discussed here. Read the next section before you read the rest.
Before you read on: what ICG's stake in this is
One of the options on this page, AtomCRM, is built and sold by ICG, the company publishing this page. ICG has a commercial interest in AtomCRM's success. You should weigh everything we say about it with that fact sitting next to it, not instead of it.
We assess every category on six axes, stated here so you can apply them yourself: pricing transparency, ABDM-native support, WhatsApp handling (native versus bolted-on), DPDP Act 2023 posture, implementation and migration burden, and whether the product was built for Indian healthcare specifically or adapted from a generic CRM. AtomCRM was designed against those same six axes — that's not neutral evidence, it's a design choice we're disclosing. Comparative claims are also the kind of claim the ASCI Healthcare Guidelines govern, so we're naming that framework here rather than letting it sit unstated: anything on this page should be checkable against the criteria above, not taken on our word.
The same disclosure applies to Hawk, ICG's CRM-intelligence layer, wherever it comes up later in this piece. Hawk is also our product. Flag that to yourself now so you don't have to remember it twice.
Jump to a section
Clinic-built CRMs · Enterprise CRM suites · General-purpose sales CRMs · Listing-platform CRMs · ICG's AtomCRM · DPDP as a buying criterion · Listing platforms: competitor or integration? · Migration cost · ABDM, WhatsApp, multi-location · FAQ
How we built this guide
We defined the six axes above before describing any category, so the limitations below don't read as reverse-engineered from AtomCRM's feature list. That's a real risk on a page like this — a company describing its own market can easily make every alternative's weakness line up suspiciously well with its own strengths. Where a category has a genuine, structural weakness, we name it: a pricing model, a missing ABDM connector, a WhatsApp add-on that costs extra, an implementation timeline. Individual products inside each category vary, so treat these as the questions to ask, not a verdict on any one vendor.
The five kinds of healthcare CRM in India
1. Clinic-software products with a CRM module
Several Indian clinic-software products grew out of EMR, queue-management or practice-management tools and added a CRM layer later. Clinical charting, scheduling and queue management tend to be strong; the lead-funnel view usually sits secondary, and revenue-intelligence questions (cost per lead, drop-off by source) are often thin because the product wasn't designed around them. Some are spa- and wellness-leaning, some are built around a single practitioner's day, and some newer entrants have a small support bench outside the metros they started in. Best for: clinics and hospital groups that want charting and CRM in one system. Ask: is ABDM linkage built and tested, is DPDP consent logged per record, how does it handle a second or tenth location, and what does local support turnaround look like in your city?
2. Enterprise CRM suites and global EHR-linked platforms
Enterprise CRM suites with a health-cloud edition, and practice-management products built for the US market first, are designed for large organisations with an in-house admin team. A hospital group with dozens of seats will get more out of them than a three-doctor clinic ever will. Pricing is usually quote-based and sits well above clinic budgets once implementation-partner cost is included, and ABDM and India-specific WhatsApp handling typically need third-party connectors or real customisation work rather than a settings toggle. Best for: large hospital groups with enterprise procurement and IT capacity. Ask: total cost including the implementation partner, and who builds and maintains the ABDM connector.
3. General-purpose sales and marketing CRMs
This is the widest category: general-purpose sales CRMs sold across real estate, education and other industries, SMB marketing-automation suites, telecalling-first CRMs built for outbound phone teams, and project-management tools with CRM features added. Many offer healthcare templates, some are inexpensive and multi-branch friendly, and funnel or campaign tooling can be strong. The tradeoff is consistent: the "healthcare" positioning usually lives in templates and messaging rather than the architecture, WhatsApp often needs a paid add-on, ABDM isn't a native concept, and DPDP consent-flow configuration falls to the clinic's own IT resource. Watch per-location pricing models too — they can make the tenth clinic cost as much per seat as the first. Best for: cost-conscious clinics with in-house IT capacity willing to build the healthcare-specific parts. Ask: what the WhatsApp and ABDM layers cost on top of the headline price, and whether reporting can answer "which specialty and source drove revenue", not just "how many calls converted".
4. CRMs tied to a doctor-listing and booking platform
A national doctor-listing and booking platform may offer its own clinic CRM. It's worth separating the CRM from the listing itself (more on that below). These CRMs tend to tie a clinic further into the platform's own booking and commission ecosystem rather than sitting neutrally on top of it. If a clinic already depends on that platform for patient acquisition, that consolidation might be exactly what it wants. If it doesn't, it can make a platform-agnostic funnel harder to run later. Best for: clinics whose acquisition already runs mainly through one listing platform. Ask: can you export your full lead and patient history if you leave?
5. ICG's AtomCRM
As disclosed above, this is ICG's own product, so read this section with that in mind. AtomCRM is built specifically for Indian clinics and hospitals, with WhatsApp handled natively rather than through a third-party workaround, specialty-configured funnel stages, and a DPDP Act 2023-aligned data architecture with consent logged at the record level rather than a bolted-on consent form. Pricing is published: ₹50,000/- one-time setup + ₹799/- per telecaller per month. The pricing, WhatsApp and DPDP points are the same axes we used to structure this guide — so treat the argument as circular by design, and check it against your own priorities rather than ours. It's built around IVF, dental, dermatology and hospital use cases rather than adapted from a generic sales CRM; it is not a clinical charting or EMR system. Best for: clinics and chains that want a lead-to-booking CRM built for Indian healthcare. Ask us: the same questions you'd ask anyone else — including where AtomCRM isn't the right fit.
What ICG's own clients actually save on cost per qualified lead
Before the headline number: this is a CPQL benchmark, not a promise. It measures cost per qualified lead across ICG's own client book, not an independent industry-wide study, and it says nothing about a CRM's own contribution to that number versus the marketing work sitting on top of it. Across 46 active healthcare client engagements, in a rolling 12-month window from July 2025 to July 2026, across Delhi NCR, Mumbai, Bangalore, Chennai, Hyderabad, and Kolkata, last verified 2026-07-26, ICG clients saw a 38-58% reduction in cost per qualified lead in their first 90 days. The full specialty-by-specialty breakdown is on the CPQL benchmarks page.
DPDP Act 2023: the buying criterion every clinic should apply, to any CRM
Under the DPDP Act 2023, a clinic becomes a data fiduciary the moment a patient's phone number lands in a CRM form — not when the patient signs a consent document, the obligation starts at data capture. That means four questions belong in every CRM procurement conversation, regardless of which vendor is on the table: where is the data hosted, and does the vendor's contract specify it; how is consent logged against each record, not just collected once at intake; what happens on a breach, and who notifies whom, on what timeline; and can a patient actually exercise the access and erasure rights the Act gives them, or does that require an engineering ticket. Ask a vendor these four questions directly rather than reading them off a feature list — a "DPDP compliant" bullet point on a pricing page is a marketing claim, not a contract term. AtomCRM's architecture is built around consent logging at the record level, which is disclosed here for the same reason everything else about AtomCRM is disclosed on this page: because it's also one of the axes we used to structure this guide.
Doctor-listing platforms: competing product, or the thing your CRM has to work with?
Many clinics already have a listing and booking flow running on a national doctor-listing platform before they ever open a CRM comparison page. That's the ordinary starting point for most Indian clinics, not the exception, and it changes the actual question a buyer should be asking. It isn't "is this CRM better than the listing platform" — the platform's own CRM aside, most CRMs aren't competing with the listing, they're deciding whether to sit on top of it or replace it. A clinic that wants to keep its existing listing-platform booking flow needs a CRM that pulls leads and appointment status from it without requiring the clinic to abandon it, and that integration depth varies a lot more across the market than most pricing pages admit. Ask specifically whether the listing-platform sync is native, middleware-based, or manual CSV export — the answer changes the actual weekly workload for front-desk staff.
Migration: the part every buying guide skips
Most CRM buying guides skip the week where nothing works — the actual migration. Moving from a spreadsheet, a WhatsApp-group workflow, or an incumbent CRM means historical patient records, appointment history, and lead-source data all have to move somewhere, and that somewhere is rarely a clean CSV import. Expect data cleanup before migration (duplicate patient records are the norm, not the exception), a parallel-run period where staff use both systems, and a retraining cost that has nothing to do with the CRM's monthly price. A vendor that can't describe its migration process in specific steps — what gets exported, what gets manually re-entered, how long the parallel-run period runs — probably hasn't done many of these migrations. Ask for a reference clinic that migrated in the last six months, not a case study from three years ago.
ABDM, WhatsApp, and multi-location: how the mechanics actually work
ABDM linkage works through a health-ID API call at the point of registration, not a checkbox in settings — a CRM either has that API integration built and tested, or it doesn't, and "ABDM-ready" without a named integration partner usually means the second one. A WhatsApp CRM integration that's genuinely native means the CRM talks to the WhatsApp Business API (BAPI) directly, with message templates and delivery status inside the CRM itself; a bolted-on WhatsApp integration usually means a third-party connector, an extra monthly fee, and message history that lives outside the CRM's own reporting. Multi-location support is the one that's easiest to misjudge on a demo call, because a single-location demo looks identical whether the underlying data model separates locations properly or just tags every record with a location field after the fact — ask specifically whether reporting, staff permissions, and patient records are scoped per location, or whether that's a workaround built on request.
Frameworks behind how we built this comparison
ICG's Device ID framework is directly relevant here: it reconciles the same patient across phone, desktop, WhatsApp, and an in-clinic visit into a single record, which is exactly the identity-resolution problem a CRM without cross-device tracking runs into. A patient who researches on a phone, books on a desktop, and messages on WhatsApp shows up as three different leads to many CRMs unless that stitching happens somewhere. Full detail on this and ICG's other five frameworks lives on the frameworks hub.
Healthcare CRM or clinic management system?
A healthcare CRM handles lead capture, follow-up, and patient-acquisition funnel tracking — the question of how someone becomes a patient. A clinic management system handles what happens once they are one: scheduling, clinical records, billing, day-to-day operations. Some products blur the line (several clinic-software products lean toward the CMS side while still selling as CRMs), which is exactly why this comparison exists separately from our clinic management system guide rather than merging the two.
Hawk: a lead-intelligence layer that sits on top of any CRM
Hawk is also ICG's own product, disclosed here for the same reason AtomCRM is disclosed above. It's not a CRM — it sits on top of whichever CRM a clinic already runs and surfaces lead leakage and funnel drop-off that the CRM's own reporting usually misses. It powers ICG's AI hot lead management service.
What happens when a hospital had no CRM at all
One ICG client, a 200-bed tier-2 cardiac hospital, was tracking leads in WhatsApp groups with no CRM in place before this engagement started. The full case study covers what changed in the revenue operations built around that gap, without a name attached, per ICG's anonymisation policy for enterprise case studies.
FAQ
Is this guide neutral, given ICG sells AtomCRM? No — ICG built the assessment criteria and built AtomCRM against those same criteria. That's the disclosure made above, not a dodge of it. Read the criteria in the disclosure section and apply them against your own priorities if ours don't match yours.
What's the real difference between a healthcare CRM and a clinic management system? A CRM tracks how a lead becomes a patient. A CMS tracks what happens after they're a patient: scheduling, records, billing. Several clinic-software products do both to varying degrees.
Does DPDP Act 2023 apply to a CRM that only stores phone numbers and appointment status? Yes. A phone number tied to a healthcare appointment is personal data under the Act, and the fiduciary obligation starts at capture, not at diagnosis or treatment.
Can a clinic keep its existing doctor-listing platform profile while switching CRMs? Usually, yes, provided the new CRM has a native or middleware-based sync with that platform rather than requiring manual export. Ask the vendor to show that integration specifically, not describe it.
How painful is migrating patient data from an old CRM or spreadsheet system? Plan for data cleanup, a parallel-run period, and staff retraining time — not just the CRM's monthly fee. A vendor who can walk you through a recent migration in specific steps has actually done it before.
Is ABDM integration mandatory for a private clinic CRM in 2026? Not legally mandatory for every private clinic yet, but it's becoming a practical expectation for hospitals and multi-location chains, and it's worth building toward even if it isn't required on day one.
What does WhatsApp-native actually mean versus a bolted-on integration? Native means the CRM talks to the WhatsApp Business API directly, with templates and delivery status inside the CRM's own reporting. Bolted-on usually means a third-party connector and an extra fee, with message history sitting outside the CRM.
If you're comparing CRMs and want a second opinion on the shortlist
If you've narrowed your shortlist to two or three products, book a call and we'll walk through the DPDP and ABDM questions above against your specific setup — including where AtomCRM genuinely isn't the right fit. If you want the broader picture of what a CRM sits inside, our free audit covers the marketing and lead-ops layer around it.
Category descriptions above are general and individual products vary; confirm pricing, ABDM and DPDP posture directly with each vendor before signing. CPQL figures carry their own methodology line, stated in full above. ICG's ownership of AtomCRM and Hawk is disclosed at the top of this page and applies to this guide throughout — this isn't a one-time disclaimer, it's the operating assumption for reading the rest of the article.
