WhatsApp CRM for coaching institutes

A parent messages a coaching institute at 9:40 pm: “Is there a seat in the evening JEE batch?” The fluorescent lights in the classroom are off. The counsellor is on a bus. That thread *is* the admission. If it lives in a personal WhatsApp, the seat belongs to whoever replies first — and whoever forgets, loses it to the centre down the road that answered in twelve minutes.

A WhatsApp CRM for coaching institutes is not a school ERP and not a blast tool. It is a desk where the enquiry, the demo class, the fee conversation and the batch-start reminder sit on the same student — on WhatsApp, and on SMS or email when the parent is not on WhatsApp.

This article is the operating picture: what counselling teams actually do all week, where spreadsheets and personal chats break, how a conversation OS plus an education pack is supposed to look, and what to refuse when a vendor demo is only a chatbot.

A week in admissions, not a feature list

Monday: fifty enquiries from a Facebook form, a Google Form, a walk-in, and three forwarded WhatsApp screenshots. They all say “JEE” or “NEET” and a city. None of them name a batch.

Tuesday: two counsellors are in demo class. The remaining one is answering “fees?” with a PDF that is six months old. The owner cannot see which threads are ageing.

Wednesday: a parent who attended Monday’s demo has gone quiet. Nobody owns the follow-up. The batch starts Saturday.

Thursday: the accountant wants a list of “likely to pay.” That list is a counsellor’s memory plus a sheet titled FINAL_v7.

Friday night: another 9:40 pm message. If the CRM cannot show *course, batch, demo attendance, fee stage, owner* next to that chat, you do not have a WhatsApp CRM. You have a chat app with extra login screens.

What counselling teams actually need

Most “education CRMs” store a lead and ask the counsellor to copy-paste a WhatsApp. That is why institutes still run admissions in chat backups. The work is the conversation, and the conversation has fields:

• Which course and batch window (weekday evening vs weekend) did they ask about?
• Which centre — many brands run three addresses and still share one WhatsApp number.
• Did they attend the demo, no-show, or reschedule?
• Who owns the thread if that counsellor is taking a class?
• Has fee / scholarship / sibling discount been discussed, and in which currency of promise (not a legal contract — a stage)?
• When does the batch start, and has the welcome / kit / first-class reminder gone out on the same thread?

VartaDesk’s education pack installs courses, batches and enrolments on top of a shared inbox. The conversation OS does not fork: one thread list across WhatsApp, SMS, RCS and Email. The pack does not pretend to be an attendance ERP.

Shared inbox: the owner must see every counsellor

The failure mode of “everyone uses WhatsApp Business on their phone” is not rudeness. It is invisible inventory. A parent messages the printed number on the flex. That number is logged into one device. When that counsellor is sick, the thread is gone.

A shared inbox means:

1. The number is connected once (your BSP — AiSensy, Twilio, Fast2SMS, etc.).
2. Every counsellor sees the same queue, with assignment.
3. Internal notes stay off the parent’s phone.
4. When a conversation flips to human, journeys stop. A late-night bot must not argue with a parent who already said “I’ll come Saturday.”

If you are comparing WhatsApp inboxes rather than ERPs, read Wati vs VartaDesk. Wati is a strong WhatsApp Business platform. VartaDesk is the desk plus the records a coaching centre already names out loud.

Demo class, then a person — not another bot loop

Institutes that auto-reply “Thank you for your enquiry, our team will connect shortly” and then go silent convert like a missed call. The parent already used WhatsApp because they wanted an answer *tonight*, not a ticket ID.

A pattern that survives contact with a real counselling floor:

1. Confirm the course and the batch window on the same thread. “Evening JEE, 6:30, starting 12 Sep — 4 seats.” Not “we offer many courses.”
2. Send the demo slot as an approved template, with the centre address and a map link, not a new essay every time.
3. Mark attendance as a CRM fact. A demo that happened only in someone’s head will not trigger the fee conversation.
4. If they reply with a fee objection, a timing clash, or “my child is in another institute,” hand off to a human. Automation that talks over a counsellor is worse than no automation.

VartaDesk journeys pause when a conversation flips to a person. That is table stakes. If a vendor cannot show you that pause in a demo, you are buying a chatbot with a CRM skin.

Why “WhatsApp only” breaks at Indian scale

The parent who enquired on WhatsApp may need an SMS at 7:05 am for the demo reminder (notifications muted, phone in a school bag), or an email with the fee breakdown that the other parent wants to print. A WhatsApp-only inbox makes the counsellor the integration.

India also has DLT rules for SMS. Fee and reminder templates need Entity ID, Template ID, Header and category matching the TRAI portal. Incomplete DLT must not silently “send anyway.” We wrote the ruleset here: India DLT SMS and WhatsApp CRM.

RCS is optional. Email is not glamorous. Both still beat “we only do WhatsApp” when the family is split across devices.

How this is different from a school ERP

An ERP keeps attendance, marks, fee ledgers and ID cards as the system of record. A conversation OS keeps the thread. Do not dump the marksheet into the inbox. Do not ask the counselling CRM to generate transfer certificates.

The pipeline that belongs on the desk is counselling-shaped: enquiry → demo booked → demo done → fee discussion → enrolled → batch started. Academics stay in the ERP. If a vendor shows you “homework WhatsApp” as the hero, you are looking at the wrong product for admissions.

A realistic first 14 days on VartaDesk

• Day 1–2: Connect the WhatsApp number through the provider you already pay for. Invite counsellors. Do not run dual inboxes “for a while.” Dual inboxes is how threads get lost.
• Day 3: Install the education pack so course, batch and enrolment exist as records — not as tags named `JEE_EVE`.
• Day 4–5: Move the five templates you actually send (welcome, demo confirm, demo reminder, fee follow-up, batch start) through WhatsApp approval. Paste DLT IDs on the SMS versions.
• Day 6: Build one journey: demo reminder → wait → if no reply, SMS → if they reply “can’t come,” assign a human.
• Day 7–14: Run *only* new enquiries on the desk. Do not boil the ocean with three years of chat export. Prove that Saturday’s batch-start list is generated from the CRM, not from a counsellor’s notes app.

Opt-out is not a legal footnote. STOP on SMS or WhatsApp must stop campaigns and journeys. A coaching brand that keeps nudging after “please don’t message” will not keep the number.

Questions to ask any WhatsApp CRM vendor

• Can two counsellors work the same WABA without sharing a phone?
• Does human takeover stop the journey, or only hide it?
• Are course and batch first-class records, or tags on a generic lead?
• Can I send the 7 am reminder as DLT SMS from the same student record?
• Will you invent my DLT Header in a pack so onboarding looks fast? (If yes, walk away.)
• Where do globally opted-out people get excluded — at send time, or “we’ll add that”?

What “good” looks like on a Saturday morning

The owner opens the desk. The evening batch that starts Monday has a list: enrolled, fee discussed, demo done, still-open. Each row opens the same WhatsApp thread the parent started in. Nobody is hunting a screenshot in a family group.

That is the product. See the education walkthrough or start a trial. The first week of value is not a dashboard. It is the enquiry that still has an owner the next morning.