Google Sheets CRM for General Physician Clinics

It's 11 am, peak OPD hour. The receptionist is juggling three things: a walk-in asking for the doctor's timing, a WhatsApp message from someone who wants to know if fasting is required before a blood test, and a call from a patient checking whether last week's reports are ready. By the time she finishes with the walk-in, the WhatsApp enquiry is buried under four other chats, and it never gets a reply.

That one missed reply is the leak. Not a dramatic one — nobody loses a patient over a single unanswered message. But over a month, a GP clinic in a tier-2 or tier-3 Indian city typically fields 200-400 enquiries across calls, WhatsApp, Google listing messages and walk-ins, and a meaningful slice of those never get followed up simply because there's no single place tracking who asked what and who called back. The receptionist isn't lazy; she has no system, just memory and a diary that's usually left at the front desk when she's on lunch or chhutti.

This guide covers what a proper CRM setup looks like for a general physician's clinic — not a hospital-grade EMR, just a working system that captures every enquiry and tells someone, every morning, who to call. If you want to see exactly what's included, the CRM Setup & Automation for General Physicians offer page has the full scope.

What a CRM Setup actually does for a General Physician

Strip away the jargon and a CRM for a GP clinic does four things:

• Captures every enquiry in one place — whether it came in as a phone call the receptionist logged manually, a WhatsApp message, a Google Business Profile message, or a walk-in who left a number "in case a slot opens." Right now these live in four different places (call register, WhatsApp app, a notebook, someone's memory). The CRM puts them in one sheet or one Zoho pipeline.
• Tracks the token/timing questions separately from actual patient follow-ups. A GP clinic gets a huge volume of "what time is doctor available today" and "is there a queue right now" messages — these are not leads to nurture, they're operational noise. The setup tags these so they don't clutter the same view as a patient who called asking about a follow-up consultation for their father's BP medication.
• Reminds someone, daily, who needs a callback. A patient who asked "can I get an appointment for evening slot" and never got a confirmed time doesn't just disappear from view — the system flags them for a call today.
• Produces a monthly pipeline report — how many enquiries came in, how many converted to a visit, where the drop-off is (usually it's the evening rush, 6-8 pm, when the clinic is busiest and least likely to reply to anything).

This isn't about digitising patient medical records — that's a separate, more regulated problem. This is about not losing the person who wanted to become a patient but got lost in the noise.

How it works, step by step

1. First contact captured automatically. Whether the enquiry lands via WhatsApp Business number, a missed call, or a Google Business message, it's logged into the CRM sheet with timestamp, channel, and a first-cut category (token/timing query vs. appointment enquiry vs. follow-up).
2. Auto-reply handles the repetitive questions. Timing, address, whether X-ray facility is available on-site — these get an instant WhatsApp reply so the front desk isn't retyping the same answer forty times a day.
3. Anything needing a human gets flagged. If the question is specific ("can doctor see my father today, he has fever and cough for 3 days"), it's routed to the receptionist's queue, not auto-answered.
4. Receptionist responds from within WhatsApp as usual — the CRM just watches and logs, it doesn't change how she talks to patients.
5. Unclosed enquiries roll into the next day's reminder list. If nobody confirmed a slot or closed the enquiry by end of day, it appears at the top of tomorrow's call list.
6. Morning reminder goes out — typically a WhatsApp message or sheet notification listing 5-15 names to call back before the OPD rush starts.
7. Monthly report auto-generates — enquiry volume by channel, conversion rate to actual visit, and the busiest hour for missed follow-ups (in our experience, this is almost always late evening).

Customer: Is the doctor available today evening, my son has fever since yesterday Bot: Yes, evening OPD is 6 PM to 9 PM today. Would you like us to note your son's name and hold a slot around a preferred time?

Customer: Doctor available hai kya abhi, papa ko BP ki problem hai, purani reports bhi hain Bot: Ji haan, doctor available hain. Aap 15-20 minute mein aa sakte hain, ya specific time chahiye toh bata dijiye hum note kar lete hain.

A typical week, before and after

What it costs and what is included

The payback logic is simple: if this system recovers even one follow-up a month that would otherwise have been missed — a patient who came back instead of going to a competing clinic down the road — it has likely paid for the care plan. You don't need big numbers here, just fewer people falling through the cracks during the evening rush.

Setup timeline

Day 0

You have a 20-minute call with us. We ask about your current channels (WhatsApp number, Google Business listing, whether you take phone bookings), your OPD hours, and what's currently leaking — usually it's evening enquiries or follow-up patients.

Day 1

We build the CRM structure — sheet or Zoho pipeline, tagging rules for token/timing vs. genuine enquiries, and connect your WhatsApp Business number and Google Business messages into it. You review the auto-reply wording for accuracy (your OPD hours, address, facilities available).

Day 2

We go live. Real enquiries start flowing into the CRM, auto-replies start answering repetitive questions, and the first day's reminder list is generated for the receptionist. You test it by sending a few sample messages yourself before the OPD rush starts.

What you need to have ready

• Your clinic's WhatsApp Business number (or willingness to set one up)
• Current OPD timings, including any split shifts (morning/evening)
• List of facilities available on-site (X-ray, ECG, pharmacy) so auto-replies are accurate
• Access to your Google Business Profile if you use it for messages
• Someone designated to act on the daily call-back list — usually the receptionist or the owner
• A rough sense of your current enquiry volume (even a guess helps us size the setup correctly)

Doing it yourself vs done-for-you

DIY is genuinely fine if your enquiry volume is low (under maybe 50 a month) and one person reliably owns follow-ups. It stops working the moment volume grows or the person managing it takes leave.

Mistakes GP clinics make with this

• Treating every WhatsApp message as equal. Token/timing queries and genuine appointment enquiries get lumped together, and the real enquiries get lost in volume. Fix: tag and separate them from day one.
• No one owns the follow-up list. The CRM only works if someone actually calls the people on the daily list. Fix: assign it explicitly to one person, not "whoever's free."
• Auto-replies with wrong or outdated timings. If OPD hours change (say, doctor travels for a few days), the auto-reply keeps giving old information and frustrates patients. Fix: build in a quick way to update hours without re-doing the whole setup.
• Ignoring the monthly report. Owners set this up and then never look at the pipeline report, missing the pattern (usually evening drop-off) that would tell them where to focus. Fix: actually read the monthly numbers, even for five minutes.
• Trying to make it a full EMR. Cramming patient medical history into the same sheet as enquiry tracking makes it unwieldy and raises data-sensitivity concerns. Fix: keep this strictly to enquiry and follow-up tracking, not clinical records.

FAQ

Will this replace my receptionist?

No. It handles the repetitive timing/token questions automatically so she can spend her time on actual patient conversations and callbacks, not retyping the same answer all day.

Can it work with just WhatsApp, no separate app?

Yes. Most GP clinics we work with run this entirely through their existing WhatsApp Business number and a Google Sheet — no new app for the receptionist to learn.

What if I already use Google Sheets informally?

We build on what you have where possible. If your existing sheet has useful history, we can migrate the structure rather than starting from zero.

Does this handle patient medical records?

No, this is enquiry and follow-up tracking only, not a clinical EMR. Keeping the scope narrow keeps the setup simple and avoids handling sensitive medical data unnecessarily.

What happens if I stop the monthly care plan?

The CRM and all your data remain yours. There's no lock-in — you can pause the care plan and the sheet or Zoho account keeps working, though you'd lose ongoing monitoring and monthly report generation.

How is this different from a hospital's patient management software?

Hospital PMS systems are built for large multi-department workflows and billing. This is scoped specifically to the GP clinic problem — enquiries and follow-ups — and costs a fraction of what PMS software typically runs.

Next step

Send us your clinic type, city, and what's currently leaking — evening enquiries, follow-up patients, or something else — on WhatsApp.

Check the full scope on the CRM Setup & Automation for General Physicians page.

See our process end-to-end on the How We Work page.