Home / Use cases / Education
Education & EdTech

WhatsApp for schools, colleges and EdTech.

Admission funnels, fee reminders, attendance and exam updates, and parent communication that does not live in a group nobody can mute.

The group-chat problem

Most institutions already run on WhatsApp, just badly. Announcements go into parent groups where forty people reply "noted", important messages scroll away in an afternoon, and a teacher's personal number becomes the school helpline at 10pm.

The fix is not to leave WhatsApp, which parents will not do. It is to move from groups to one-to-one messaging from an institutional number, so announcements reach individuals, replies come to a shared inbox several staff can work, and nobody's personal phone is the support channel.

Admissions

Admission enquiry volume is seasonal and unforgiving: the same week brings hundreds of enquiries, and the ones that go unanswered for two days enrol elsewhere.

  • Instant acknowledgement on every enquiry, with the two or three qualifying questions that route it correctly.
  • Stage tracking so enquired, visited, applied and enrolled are visible rather than remembered.
  • Deadline reminders for incomplete applications, which recover more admissions than any amount of new lead spend.
  • Document collection in the thread, so parents are not asked to email a scan they will not email.

Fees

Fee reminders are the flow institutions most often run manually and most obviously should not. A schedule ahead of the due date, a payment link in the message, an automatic receipt on payment, and a separate escalation path for genuinely overdue accounts. The receipt matters more than it looks: it removes the "did it go through" call entirely.

Day-to-day communication

Attendance alerts, exam schedules, result notifications, holiday and closure announcements, transport delays. All Utility-shaped, all better as an individual message than a group post. Segment by class, section or batch so a parent receives what concerns their child rather than everything.

For EdTech specifically

Course platforms have a different problem: enrolment is easy and completion is not. Class reminders before a live session, nudges when a learner goes quiet for a week, and renewal messages timed to the actual course end rather than the billing date. Watch reply rate against opt-out rate closely here, because learner lists are easy to over-message and expensive to rebuild.

A note on messaging minors

Communicate with parents or guardians rather than students where the student is a minor, and keep consent records against the guardian. India's DPDP Act sets specific expectations around children's data, and the practical implication for most schools is straightforward: the number on file should be the guardian's, and marketing to minors is not something to experiment with.

FAQ

Common questions from institutions

Messages reach individuals rather than scrolling away in a group, replies come to a shared inbox several staff can work rather than one teacher's personal phone, you can segment by class or section, and you have a record of what was sent to whom.
Yes. A payment event from your fee system can trigger a receipt through a webhook, which removes most of the calls asking whether a payment went through.
Yes. Routing rules can send admissions, fees and academic queries to different people or teams, and role-based access controls who can see what.
Where students are minors, communicate with parents or guardians and keep consent against the guardian. The DPDP Act sets specific expectations around children's data.
Yes. Sends are paced to your account's messaging limit rather than exceeding it and failing, and the shared inbox is built around showing who is waiting rather than an even distribution of work.

Related

Start with the admission funnel.

Instant acknowledgement, stage tracking and deadline reminders, before next season's enquiries arrive.