What should a coaching institute send on WhatsApp after a demo class?
Within 15 minutes of the demo ending, send one WhatsApp message that names what the student saw, states the next step (fee link or parent call), and proposes a single deadline. Then run a fixed 72-hour rhythm: same evening recap, next-morning parent nudge, and a day-three close-or-pause message. Post-demo WhatsApp follow-up coaching teams treat this as ops, not inspiration.
Post-demo WhatsApp follow-up for coaching admissions is the structured thread between a student leaving your centre (or logging off Zoom) and the fee receipt. Most institutes nail the demo pitch and then go quiet for two days while parents compare three fee PDFs on the dining table. Swayam builds admissions and revenue ops for Indian coaching teams (swayamapp.com), not the government SWAYAM MOOC portal.
Why do warm demos still die after day one?
The student liked the faculty. The parent asked sensible questions. Then everyone returned to board homework and office calls. Your counsellor meant to send the fee breakup that night but got pulled into walk-ins. By Thursday the family has a competing quote and your thread is buried under school group forwards.
Industry write-ups on Indian admissions often cite long gaps between demo and fee as a top leak point, though exact percentages vary by city and course ticket size. What we see in the field is simpler: the institute that keeps the thread alive with short, specific WhatsApp notes wins more often than the one that sends a generic brochure on day five.
- Counsellors confuse "polite" with "vague" and never ask for a decision date.
- Fee messages go out without referencing what happened in the demo room.
- No owner is tagged when the parent says "we will discuss at home."
What does the first 72 hours look like on the clock?
Run the same clock for every demo attendee, whether the source was Meta, walk-in, or referral. The counsellor who ran the demo owns the thread unless you explicitly hand off to a closer. Ops should see four timestamps in the CRM: demo end, recap sent, parent touch, and fee status.
| Time after demo | Who acts | WhatsApp job | Success signal |
|---|---|---|---|
| 0–15 minutes | Demo counsellor | Recap plus one next step (fee link or 10-minute parent call slot) | Parent or student replies or taps the link |
| Same day, 7–9 PM | Same counsellor | Short note on batch start date and one objection you already heard | Read receipt with no reply still counts; log it |
| Next morning, 10–11 AM | Senior counsellor or team lead | Parent-facing message if the student attended alone | Parent asks a fee or transport question |
| Hour 48–72 | Owner of the lead | Binary ask: seat hold by date or move to nurture list | Fee initiated, visit booked, or lost reason captured |
Admissions teams that document this table on a wall or inside their CRM stop debating whether "we already followed up." Either the timestamps exist or the lead is still open work.
What should each message actually say?
Keep copy pasteable but never identical across leads. Swap in the batch name, the faculty member who taught, and the exact concern raised ("commute from Noida Sector 62," "doubt on organic chemistry pacing"). Counsellors who attended the demo should not outsource the first recap to a broadcast template; parents notice instantly.
Same-evening recap example shape: thank them for attending, name one thing the student did well in class, attach fee options (lump sum and instalment if you offer both), and ask which slot works for a five-minute parent call tomorrow. Avoid open loops like "let us know if you have questions" with no calendar offer.
Parent nudge the next morning matters when the student is in Class 11 or 12 and the cheque writer was not in the room. One calm paragraph on safety, results context for your city, and how fee adjustment or scholarship review works beats three voice notes from different staff.
By hour 72 you are choosing between enrollment and honest closure. If they are comparing institutes, ask which two names are on the table and what would make your centre the pick. If they go silent, mark lost reason as "post-demo nurture" and drop them into a slower weekly thread rather than daily pings that train parents to mute you.
How do managers spot post-demo leakage early?
Track three counts every morning during admission season: demos held yesterday, recaps sent within 15 minutes, and fee links opened within 72 hours. When recap compliance slips below ninety percent for two days, pause new walk-in assignments until the backlog clears. Counsellors carrying more than twenty active post-demo threads at once will skip the evening message; that is a capacity signal, not a attitude problem.
Pair WhatsApp discipline with call backup. If the parent has not read the recap by the next afternoon, one short call from the same counsellor often unlocks the fee conversation faster than a fourth text. Log the call outcome in the same timeline as the chats so the next shift does not restart from zero.
How is this different from pre-demo nurture?
Pre-demo sequences sell the visit: reminders, directions, faculty intro. Post-demo work assumes intent already rose once. The tone shifts from marketing to decision support. Mixing the two (sending another "why choose us" deck after they sat in your classroom) feels tone-deaf and lengthens the thread without moving fee status.
If you run separate numbers for marketing blast and counsellor desk, keep post-demo on the counsellor line parents already trust from booking. Jumping them to a new business account mid-decision adds friction you do not need.
What is a realistic post-demo WhatsApp follow-up coaching target?
Targets vary by ticket size, but operators we work with aim for at least sixty percent of demo attendees to receive the 15-minute recap, forty percent parent or student reply within 72 hours, and twenty-five to thirty-five percent fee initiation within seven days for competitive exam batches. Treat those as internal benchmarks you validate against your own CRM export, not guarantees.
Should you use WhatsApp templates after the demo?
Inside the 24-hour customer care window, free-form messages are fine on the Business app many centres already use. Outside that window, or when you scale to multiple branches, approved utility templates for fee reminders and demo feedback protect your number quality rating. Document opt-in on the enquiry form and keep a plain-language stop path. Meta's business policy pages spell out template categories; your BSP can help map fee nudges to the right label.
Who owns the thread when the demo counsellor is on leave?
Assign a named backup before the demo starts, not when the recap is already late. The backup reads the demo notes field (three bullets minimum: course, concern, promised next step) and sends from the same visible name if possible. Parents should not have to explain the demo twice because of internal roster shuffles.
When should you stop WhatsApp and mark the lead lost?
After the hour-72 binary message, either move to fee collection, schedule a parent visit, or shift to a weekly nurture with exam tips and batch dates. More than six unprompted pings in ten days without a reply usually means mute risk. Capture lost reason while the demo memory is fresh: fee, distance, competitor name, or timing. That data belongs in the same system as your Meta lead reports.
Where to tighten the rest of your admissions loop
Post-demo follow-up sits between fast first response and long-cycle nurture. If your team is still fixing upstream leaks, read the walk-in enquiry 90-minute playbook, the WhatsApp follow-up sequence for coaching admissions, and the admissions CRM 48-hour playbook for India. When you want one timeline for enquiry, demo, and fee, skim Swayam pricing to see if a single admissions CRM fits how your counsellors already work on WhatsApp.
