CRM Software for Hospitals: Running the Enquiry Desk and Call Centre

CRM software for hospitals manages the patient enquiry before registration: every call, ad form, website form and WhatsApp chat is captured, routed to the right department, called back on a fixed schedule, booked for an OPD visit and tracked until the patient arrives. It sits beside your HIS, which takes over at registration, and shows what each specialty's Meta ads cost per qualified lead.

For a wider checklist that also covers clinics and chains, read the healthcare CRM buyer's guide.

What CRM software for hospitals covers that the HIS does not

Search for "CRM for hospital management" and most results are hospital management software: registration, EMR, billing, pharmacy, lab, beds. That software starts working when a patient gets a UHID. A hospital CRM covers the stretch before that point, plus the follow-up after an OPD visit that nobody in the HIS is assigned to chase.

Use this split when you write requirements:

Some HIS vendors sell a CRM module; ask yours what it covers before buying a second system.

The gap between the two is where patients disappear. Say someone in Indore fills a knee-pain form on Instagram at 10 pm, gets a call the next afternoon, and has booked elsewhere by then. The HIS never saw that person, so nothing records the loss. If your enquiries sit in Excel or on agents' personal WhatsApp, you have this gap.

Department-wise enquiry routing with sources and teams

Some enquiries name a specialty: the knee replacement ad, the IVF lead form. Others don't: the main number, a general booking form, a WhatsApp chat that opens with "hello". Route them differently.

Specialty enquiries go straight to the department. Give each department its own lead source per channel. In atomcrm.ai each Meta lead form is mapped to its own source, starting stage and owner, each website form gets its own private webhook URL, and a source can skip the assignment rules and send its leads straight to a person, team or branch. "Ortho Meta" and "Ortho Web" both land with the orthopaedics coordinators without anyone sorting them.

General enquiries go to the central call centre. Assignment rules share the load: round robin to split evenly, or capacity to give the next lead to whoever has the fewest open ones, with a daily cap per person and a fallback person. Leads that match no rule stay unassigned and visible.

A sample routing table for a hypothetical 200-bed hospital in Nagpur:

Make payment mode a dropdown (cash, insurance through a TPA, corporate, government scheme), because it changes the first call. Conditional rules on custom fields show the orthopaedics fields only when the department is Orthopaedics.

Agree one edge case before go-live. A repeat enquiry from a form, ad or manual entry (matched on the last 10 digits of the phone, or on email) is recorded on the existing lead, not as a new one. If cardiology owns that patient and they now ask about a knee, decide who hands it across. A CSV import does not check, so clean duplicates out of the file before importing.

For a group with several units, make each unit a branch with its own desk teams, and limit its rules to that branch. Here is how lead distribution works, including branch and team rules.

Missed calls at the hospital call centre: escalation rules

The main number loses patients quietly: calls at shift change, lunch, evenings and Sundays that ring out and are never returned. Fix it in three layers.

Layer 1: move the ring to the next person

If agents take calls on Android phones with atomcrm.ai's Call Pro app, a missed incoming call can escalate to the next telecaller by rules: ring time, order, and skipping anyone offline. Write the plan down first:

Rule: Main line
Ring time before moving on: 20 seconds
Order: Agent 1 > Agent 2 > Agent 3 > Shift lead
Skip: anyone who is offline

If the main number runs on an IVR or missed-call service instead, connect it as a lead source so each caller arrives as a lead with a number to call back.

Layer 2: a date on every patient you could not reach

Create a stage called Not reachable that requires a next callback date, so no agent can park a lead there without one. A cadence that suits most hospital enquiries:

Each attempt is one Quick Update: connected or not, stage, status, a one-line comment and the next callback. A patient has only one pending callback at a time, so a new date replaces the old one.

Layer 3: someone owns the overdue list

The callback queue has tabs for Overdue, Due today, Upcoming and All pending, oldest first, with the last comment on each card. A reminder arrives 15 minutes before each callback, and callbacks not done on their day stay in Overdue. Set a first-response time limit in settings, and add an automation on the "callback missed" trigger that assigns the lead to the shift lead.

Call Pro logs every call on the lead with outcome, duration and recording, feeding a leaderboard of connect rate, talk time and follow-up adherence per agent. See how the telecalling side works.

Appointments and show-up tracking by department

A booked appointment is not a patient until they walk in, so track the gap per department.

Create a stage called OPD booked that requires an appointment. Moving a lead into it creates an appointment with a title, start time and duration, which then moves through scheduled, confirmed, attended, no-show and cancelled. Coordinators see the day in a table or calendar view.

Set the next callback for the day before the visit and confirm on that call. If the patient last messaged more than 24 hours ago, WhatsApp allows only a Meta-approved template. A confirmation template to write in the CRM and submit for approval:

Namaste {{1}}, your appointment at {{2}} is booked.
Department: {{3}}, Doctor: {{4}}
Date and time: {{5}}
Please bring earlier reports and a photo ID.
To change the time, reply to this message.

After OPD, mark each appointment attended or no-show. Move no-show patients to a No-show stage that requires a callback date, so every missed visit gets a rebooking call. Hospitals also need an Advised procedure stage with a required callback date, where a knee replacement sits while the family discusses cost. Set Admitted as the Converted stage.

Show-up rate is attended ÷ (attended + no-show). Say cardiology booked 55 OPD appointments in a month: 45 attended, 8 no-shows, 2 cancelled. That is 45 ÷ 53, about 85%. If another department sits far below that, listen to five of its booking calls before blaming the ads.

Marketing return by specialty: cost per qualified lead and funnel reports

Lead generation for hospitals is usually judged on cost per lead, because that is what the ad account shows. Specialties differ too much in how many enquiries become patients for that to guide budgets. Compare cost per qualified lead and cost per attended visit instead.

A worked example for one hypothetical month with ₹4,00,000 of ad spend:

Cardiology has the costliest leads and the cheapest specialist visits. IVF has cheap leads and the most expensive visits. Before cutting IVF, find where it drops: 80 of 500 leads qualified (targeting and form questions), and 20 of 80 came in (follow-up). Fertility decisions also take longer, so judge IVF on a 60 or 90-day window, and read every cost next to the revenue each department books.

What atomcrm.ai gives you for this:

• Leads by source. With one source per department per channel, this standard report shows each department's rows side by side (add Ortho Meta and Ortho Web together for the orthopaedics total).
• Ads Intelligence syncs Meta ad spend and grades every ad by effective cost per qualified lead against a target CPL you set.
• Conversion lag and cohorts show how long leads take to convert, and the sales funnel adds revenue and CAC.
• Signals back to the ad platforms. Map a stage such as Visited to a Meta Conversions API event, and upload leads carrying a Google click ID as offline conversions at the stages you choose.
• Scheduled reports go daily, weekly or monthly to up to 20 addresses, so department heads see their numbers without asking.

Roles, number masking and audit trail for patient data

Enquiry data is sensitive: a name, a phone number and the condition someone asked about. Keep the CRM to what the call centre needs to book a visit, and leave clinical notes in the HIS.

Each role gets fine-grained permissions and a data scope of own leads, team or everything. Phone numbers can be masked to the last four digits for roles not allowed to see them. A sample setup:

Every recording play is logged. The audit trail records every change and export, login activity is kept, and login can require an OTP sent to the admin's numbers. Each workspace's data is isolated and stored in India. The security page explains data isolation, the audit trail and data residency, and the roles and permissions guide shows how to build the table above.

One limit for groups: data scope cannot be set by branch. Because teams are per unit desk (setup step 1), team scope already keeps each unit's staff to their own unit's leads. Keep "everything" for the few roles that genuinely work across units.

The Digital Personal Data Protection Act, 2023 applies to personal data you collect through forms and calls. Add a consent line to every form and check the current rules with your legal adviser.

How a hospital sets this up in atomcrm.ai

A first-fortnight plan, in the order that avoids rework:

1. Branches and teams. One branch per unit, one team per department desk in each unit (for example Nagpur Ortho desk), plus the call centre.
2. Stages. New enquiry; Not reachable (callback required); OPD booked (appointment required); Visited; No-show and Advised procedure (callback required); Admitted as Converted; Not interested and Went elsewhere as Disqualified. Use statuses such as "Insurance approval pending" for why a lead is stuck.
3. Fields. Department, payment mode, preferred doctor and the conditional fields from your routing table, with the key ones on Quick Update.
4. Sources. Log in with Facebook, map each lead form to its department source, and backfill missed leads for up to 90 days. Add Google lead form ads and one webhook per website form. Import open enquiries by CSV, up to 5,000 rows per file.
5. Assignment. Department sources straight to their teams, general sources to the call centre with a daily cap and fallback person. Set working hours for distribution.
6. Calls and WhatsApp. Install Call Pro on agents' Android phones and set escalation. Connect the WhatsApp inbox through Meta's WhatsApp Cloud API or Gupshup and submit your templates.
7. Roles and reports. Build the role table, then schedule reports to each department head.

atomcrm.ai is not an HIS: no EMR, billing, pharmacy or bed management. It has no dialler that places calls on its own and does not turn calls into text. The CRM runs in the browser, and the only app is Call Pro for Android. If you need those, it is the wrong fit. Otherwise, see how atomcrm.ai works for hospitals.

Frequently asked questions

How is hospital CRM software different from an HIS or HMS?

An HIS or HMS runs the patient's time inside the hospital: registration, EMR, billing, pharmacy, lab and beds. Hospital CRM software runs the time before and around it: capturing and assigning enquiries, scheduling callbacks, booking the first appointment and following up no-shows. Hospitals that advertise usually need both, with patients handed over at registration.

Can a hospital CRM send booked appointments to our HIS?

atomcrm.ai has a connector for PMS Ichelon that receives booked appointments. For other hospital software, your IT team or vendor can use the REST API with signed webhooks, or outbound webhooks for lead events. Until that is built, the front desk registers the patient on arrival and the coordinator marks the appointment attended in the CRM.

What is the best CRM for hospitals in India?

No single answer fits every hospital. Score each option on the same tests: routing by department source and team, missed-call escalation, callback dates enforced by stage, appointment states including no-show, cost per qualified lead by specialty, number masking by role, and where data is stored. Then run one department's real enquiries through a two-week trial before deciding.

How much does CRM software for a hospital cost in India?

atomcrm.ai is priced per workspace in rupees with users included: Starter includes 3 users, Growth 15 and Scale 100, and Enterprise is custom. Any plan starts with a ₹5 activation fee for a 14-day trial, after which the chosen plan auto-debits. Count your agents, coordinators and managers first, then compare plans on the pricing page.

Next step: start with one department

Pick the department with the biggest ad spend, give it its own sources, team and stages, and run two weeks of real enquiries through it before adding the rest. Start a 14-day trial for ₹5 with your own lead sources, or book a 20-minute demo and bring your department list and last month's enquiry count.