General Physician Lead Tracking Sheet: Setup Guide
Build a general physician lead tracking sheet that captures every enquiry and reminds staff who to call. Setup, cost, and timeline explained.

It's 11:40 AM at a general physician's clinic. The receptionist is juggling a walk-in patient asking for a token, a phone call about a fever consultation, and a WhatsApp message from someone asking "Doctor available today evening?" She answers the call, forgets to note the WhatsApp enquiry, and by 6 PM that patient has already booked at a clinic down the road. Nobody in the clinic even knows the enquiry existed.
This happens every week in almost every GP clinic we've set up for — not because the receptionist is careless, but because there's no single place where an enquiry becomes a tracked lead. A phone call is remembered until the next call interrupts it. A WhatsApp message sits unread between patient records. A walk-in's contact number is written on a prescription pad that gets thrown away. The clinic doesn't lose patients because of bad medicine — it loses them because nobody followed up on "I'll come tomorrow" or "let me check with my husband."
This guide walks through what a general physician lead tracking sheet actually does, how it's built, what it costs, and what to keep ready before you set one up. If you want to see the exact setup we sell, it's on the offer page.
What a CRM Setup actually does for a General Physician
For a GP clinic, "CRM" doesn't mean a sales pipeline with deal stages — it means one sheet or system where every person who has ever asked "is doctor available" ends up, with what they asked and what happened next. Concretely, it does four things:
- Captures enquiries from every channel — phone calls (via missed call or call log), WhatsApp messages, walk-ins the receptionist logs manually, and Google/Justdial enquiries if you run ads. Right now these live in four different places (or nowhere).
- Tags each enquiry with what it actually is — new patient asking about timings, existing patient asking about a follow-up visit, someone asking if the doctor treats a specific condition, or a report/prescription request. This matters because a "timing question" needs a different response than a "follow-up due" reminder.
- Reminds staff who to call today — if a patient said "I'll come for review after 3 days" and didn't show up, the sheet surfaces that name on day 3, instead of relying on the receptionist's memory or a diary entry nobody reopens.
- Gives the owner-doctor a weekly view — how many enquiries came in, how many converted to a visit, and where the drop-off is (usually between "asked about timing" and "actually walked in").
The point isn't automation for its own sake — a GP clinic doesn't need lead scoring. It needs the token-and-timing chaos to stop losing patients.
How it works, step by step
- Enquiry comes in on any channel — WhatsApp, missed call, walk-in, or ad click.
- It's logged automatically where possible (WhatsApp and missed-call number go into the sheet/CRM without manual typing) or by the receptionist with one line for walk-ins.
- A simple auto-reply handles the repetitive questions — clinic timings, today's doctor availability, whether appointment is needed — so staff aren't answering "what time do you open" fifteen times a day.
- Anything that isn't a repetitive question gets flagged for the receptionist or doctor to reply to personally — especially medical questions, which the bot should never attempt to answer.
- Each enquiry gets a status — new, contacted, visited, follow-up due, closed — updated either automatically (if booked via the sheet) or manually in two clicks.
- Follow-up reminders fire daily — a WhatsApp or sheet notification listing who was due for review, who enquired but never confirmed, and who hasn't been contacted in 48 hours.
- A weekly pipeline report goes to the owner-doctor — enquiries received, converted, and pending, so you know if last week's dip was a one-off or a pattern (often it's a local holiday or a nearby camp pulling patients away).
Here's what the automated part of step 3 typically sounds like in English:
Customer: What time is the clinic open today? Bot: We're open 10 AM–1 PM and 5 PM–8 PM today. Would you like to book a token for evening or come as a walk-in?
And in Hinglish, which is how most actual enquiries arrive:
Customer: Doctor available hai kya abhi, thoda bukhar hai Bot: Ji haan, doctor evening 5 baje se available hain. Aap seedha aa sakte hain ya main aapka token number abhi bhej doon?
Notice the bot never diagnoses or advises on the fever — it only handles logistics and hands anything medical to staff.
A typical week, before and after
| Situation | Before | After |
|---|---|---|
| Patient WhatsApps at 9 PM asking about tomorrow's timing | Message sits unread till morning rush, sometimes missed entirely | Auto-reply answers instantly; enquiry logged for staff to see first thing |
| Patient says "I'll come after 3 days for review" | Nobody notes it down; patient forgets too | Follow-up reminder pings staff on day 3 to call the patient |
| Receptionist on chhutti for a day | Walk-in enquiries and calls go untracked | Any staff member can open the sheet and log enquiries — nothing depends on one person's memory |
| Doctor wants to know if last week's dip in patients is normal | No way to check except gut feeling | Weekly report shows enquiry count vs visits, flags the actual drop-off point |
| Two patients call about the same fever season rush (dengue/viral season) | Phone lines jam, some calls just go unanswered | Missed calls auto-logged as enquiries with number captured for callback |
| New patient asks if GP treats a specific condition (e.g., thyroid follow-up) | Answered inconsistently depending on who picks up | Standard answer stored so every staff member responds the same way |
What it costs and what is included
| Item | Price | Notes |
|---|---|---|
| CRM setup (one-time) | ₹15,000 | Google Sheets or Zoho, whichever fits your team's comfort |
| Care plan (monthly) | ₹2,500/month | Covers reminder automation upkeep, monthly pipeline report, and fixes if a channel breaks |
| Platform charges | Billed separately | Meta (WhatsApp API), Google Ads, or telecom charges for missed-call numbers are paid directly by you to those platforms |
| Lock-in | None | You can stop the care plan anytime; the sheet/CRM data stays yours |
The payback logic is simple: if the tracking sheet helps you recover even one patient a month who would otherwise have been forgotten mid-follow-up, the ₹2,500 care plan has already paid for itself. You don't need to trust a projected ROI number — just estimate what one recovered follow-up visit is worth to your clinic and compare it to the monthly cost.
Setup timeline
Setups go live within 48 hours of a 20-minute call — no long onboarding process.
Day 0
You have a 20-minute call where we ask about your channels (WhatsApp, phone, walk-ins), busy hours, and what questions your receptionist answers most often. You share access to your WhatsApp Business number and any existing patient list you want imported.
Day 1
We build the sheet or Zoho structure, set up the auto-replies for timing/availability questions, and configure the missed-call or WhatsApp capture. You review the draft auto-reply wording and tell us if anything sounds off for your patients.
Day 2
We connect the follow-up reminder logic and the weekly report, do a live test with your staff (a few real enquiries sent through), and hand over a short walkthrough video. The system is live from this point.
What you need to have ready
- Your clinic's WhatsApp Business number (or willingness to set one up)
- Current clinic timings, including any day-wise variation (e.g., doctor off on Wednesdays)
- A list of the 5-6 questions patients ask most often (timing, fees, whether appointment needed, specific conditions treated)
- Staff member(s) who will check the sheet daily — even if it's the same receptionist
- Any existing patient contact list, even if it's just a notebook or old Excel file
- Decision on Google Sheets vs Zoho (if unsure, we recommend based on your team's tech comfort during the call)
Doing it yourself vs done-for-you
| Approach | Time cost | Common failure point | Our setup |
|---|---|---|---|
| Manual notebook/register | Low setup time, but ongoing daily effort | Illegible handwriting, no follow-up trigger, lost when notebook is misplaced | Digital sheet, always accessible, backed up automatically |
| Generic spreadsheet template | A few hours to adapt | No automation — still relies on someone remembering to check follow-ups | Reminders fire without anyone needing to remember |
| Free chatbot/auto-reply tools | A day or two to configure | Often can't distinguish medical questions from logistics ones, risking incorrect auto-replies | Bot strictly limited to logistics; medical questions always routed to staff |
| Full CRM software (unconfigured) | Weeks, needs someone tech-comfortable | Over-built for a single clinic; unused features add confusion | Scoped exactly to GP clinic needs, nothing extra to maintain |
DIY is genuinely fine if you're a small single-doctor practice with low enquiry volume and a receptionist who's diligent about a paper register. The done-for-you setup earns its cost once you have multiple channels (WhatsApp + calls + walk-ins) or multiple staff who need to see the same information.
Mistakes GP clinics make with this
- Treating WhatsApp and phone enquiries as separate systems. Fix: route both into the same sheet so no channel is a blind spot.
- Letting the auto-reply attempt medical advice. Fix: hard-limit the bot to logistics (timing, tokens, fees) and route anything clinical to a human immediately.
- Only the receptionist knows how to use the sheet. Fix: train at least one backup staff member during setup so a chhutti day doesn't break the system.
- No one reviews the weekly report. Fix: block 10 minutes every Monday to glance at enquiry-to-visit conversion — patterns show up fast.
- Importing years of old, messy contact data on day one. Fix: start clean with new enquiries; import old data only after the new system is running smoothly.
FAQ
Will this replace my receptionist?
No. It removes the manual tracking burden — logging, remembering follow-ups, answering repetitive timing questions — so your receptionist can focus on patients physically in front of them.
Can the bot answer medical questions from patients?
No, and it shouldn't. The auto-reply is scoped strictly to logistics like timings and availability; any medical query is flagged for staff or the doctor to answer directly.
What if I already use a Google Sheet informally?
That's a good starting point. We typically restructure it to add automated capture and reminders rather than starting from scratch, so your team doesn't need to relearn a new interface.
Do I need a fancy WhatsApp Business API for this?
Not necessarily — for smaller clinics, a well-organized Google Sheet with manual-but-quick logging works fine. WhatsApp API automation is added when enquiry volume justifies it.
What happens if I want to cancel the care plan later?
You can stop anytime — there's no lock-in. The sheet or CRM and all your data remain yours to keep using independently.
How is this different from a hospital-scale CRM?
Hospital CRMs are built for multi-department, multi-doctor scale with complex billing integration. This setup is scoped specifically for a single GP clinic's enquiry-to-follow-up flow — simpler, faster to set up, and easier for a small team to actually use daily.
Next step
Send us on WhatsApp: your clinic type (solo GP or multi-doctor), your city, and where enquiries are currently leaking (WhatsApp, calls, or walk-ins). Message us at WhatsApp, check the offer page for full scope, or see how we work before the call.
CRM Setup & Automation for GP clinics
Platform charges billed to you directly. No lock-in. Live within 48 hours once your platform access and Meta verification are complete (Meta verification typically takes 3 to 10 business days). Global systems: 2 to 14 days.