// The situation

The simple CRM Sunatman needs essentially functions as a central management system for all incoming prospective patient data from various sources such as Meta Ads, Instagram, Google, referrals or word of mouth, events, and manual input from the admin. This system doesn't need to be directly connected to complex WhatsApp automation, but it should be able to help the Customer Care team neatly record each lead, knowing who has been contacted, who needs to be followed up, when the next follow-up should be, and the level of interest of each prospective patient. With this system, each incoming lead becomes more than just a list of WhatsApp numbers, but rather a record with a clear history, status, priority, and follow-up actions. Each lead should include basic information such as the customer's name or ID, WhatsApp number, lead source, the prospective patient's age, the patient category, infant, child, or adolescent, the branch of interest, the date of first contact, the date of last communication, the customer's main needs or questions, and notes on important conversations. For Sunatman, patient age is quite important because it directly relates to the relevant service category and pricing. The branch of interest should also be recorded so that when the prospective patient becomes more serious, the admin doesn't have to go back and search for information from old conversations. A CRM should serve as a summary of the customer journey so that different administrators can understand the customer's past context. One of the main functions of a CRM is to organize the follow-up process. Each lead should have columns for the next follow-up date, the last follow-up date, the number of follow-ups completed, the results of the last follow-up, and the status of whether the follow-up is still safe, due, or overdue. This way, administrators don't have to rely on personal memory or reopen entire WhatsApp conversations every day. A CRM can provide markers such as "Follow-Up Today," "Overdue," "Not Needing Follow-Up Yet," or "No Further Follow-Up Needed." This system is crucial because many potential patients may not immediately make a decision when they first inquire. They could be comparing prices, discussing with their partner, waiting for the right time, waiting for a child to be ready, or still having concerns about the circumcision process. These leads need to be nurtured without being overly pursued. To help the team prioritize work, the CRM should also categorize leads into Hot, Warm, and Cold. A Hot Lead is a potential patient with strong signs of a purchase or booking, such as inquiring about a specific schedule, selecting a branch, stating a desired date, asking about availability, or stating they wish to register. A Warm Lead is a potential patient who has shown interest but has not yet made a booking decision, such as inquiring about pricing, methods, facilities, recovery processes, doctors, locations, or stating they are still considering. A Cold Lead is a lead who has only asked general questions, has not shown strong interest, is difficult to contact, or has been followed up with several times but has not responded. However, for Sunatman, the Hot, Warm, and Cold qualifiers should only be used in a sales context. Leads related to medical conditions, patient complaints, current patients, or emergencies should not be considered Hot Leads because they require treatment based on service needs, not sales potential. In addition to the Hot, Warm, and Cold qualifiers, CRMs should have more specific journey statuses. Simple statuses can range from New Lead, Contacted, Information or Consultation, Interested, Intent to Book, Schedule Submitted, Booking Form Sent, Appointment Confirmed, Converted, Not Interested, and Inactive. These statuses allow the team to understand each potential patient's status along the journey to treatment. For example, a customer who has just inquired about pricing can be in the "Information" or "Consultation" sta

The verdict · Sep 30, 2026

Yes.

You need a simple CRM — and you've already designed it.

What's really going on

You have leads landing from Meta, Instagram, Google, referrals, and events, and a Customer Care team already juggling them in WhatsApp. The pain is real: no shared memory, no follow-up queue, admins reopening old chats to find a child's age or branch. But your spec — Hot/Warm/Cold, eleven journey statuses, medical-vs-sales carve-outs — is a mature CRM for a clinic that hasn't run a basic pipeline yet. Build the Ferrari now and your admins will quietly go back to WhatsApp.

What to do instead

  1. Zoho Bigin (free for 1 user, low per-user after — India-priced, works in ID) — one pipeline, custom fields for age, patient category, branch, source, next follow-up date. Start with 4 stages: New, Contacted, Interested, Booked. Add the other seven later only if a stage earns its keep.
  2. Google Sheets (free) — for the first two weeks, before Bigin. One row per lead, columns exactly as you listed. If the team won't fill a sheet, they won't fill a CRM either — find that out cheaply.
  3. Today, in 30 minutes: open Bigin, create the pipeline, add fields for Age, Patient Category (Infant/Child/Adolescent), Branch, and Next Follow-Up Date. Import the last 30 days of WhatsApp inquiries by hand. That import is the test.

What you're being oversold

Skip Respond.io, n8n, and anything that promises WhatsApp automation until the manual pipeline runs for a month — you'll automate chaos otherwise. Skip the eleven-status journey; four stages plus a Hot/Warm/Cold tag covers 90% of what you described. The cost of doing nothing isn't a number I'll invent for you — it's the warm lead who asked about a Saturday slot, got no follow-up on Thursday, and booked at the clinic down the road. You already know that lead exists.

When to revisit this

When your admins are filling Bigin daily without being reminded, and you can name three leads that booked because of a scheduled follow-up — then add WhatsApp API, journey statuses, and automation.

The part worth getting right

The one call that decides everything: are your admins going to actually log leads outside WhatsApp, or not? If yes, Bigin works and your spec unfolds over six months. If no — if the team will keep living in WhatsApp threads — then a CRM is the wrong first move and you need WhatsApp itself to become the record (shared inbox, tags, assignments). Same clinic, same leads, two completely different tools. Get this wrong and you'll pay for a CRM nobody opens, or you'll wire up WhatsApp automation on top of a process that still lives in one admin's head. Which one is Sunatman today?

Honest opinion · No affiliate links · public Get your own →

Did this actually help?

A binary signal so we know which verdicts are landing — and which ones aren't.