Every preschool in India runs on WhatsApp, and mostly it works. The class group is where tomorrow's holiday gets announced, where a mother asks whether the fever going around is anything to worry about, and where forty photographs of a rangoli competition arrive within ninety seconds of the competition ending.
I am not going to pretend that is a failure. WhatsApp beat every parent-communication product ever built for Indian schools by being where the parents already were. It costs nothing, needs no training, runs on the cheapest handset in the family, and gets read within minutes — a delivery rate no email newsletter will ever touch.
It is also structurally incapable of about half of what a preschool needs to say. Not because it is bad software. Because it is a group chat, and a good number of these messages were never group messages.
What the group chat is genuinely good at
Be honest about this before replacing any of it, because a lot of software gets bought to solve problems the group was already solving perfectly well.
- Same-day announcements to everybody: holiday tomorrow, gate closed for road work, wear yellow on Friday
- Informal warmth — the video of the class singing, the photo of the new slide, the things that make a parent smile at a bus stop
- Parents talking to each other: carpools, birthday plans, who else's child has the same cough
- Reach. It is already installed, already open, and read faster than anything you could send instead
If telling sixty families the same thing at once were your only communication need, you would not need anything else — and you should not buy anything else.
Broadcast versus per-child: the distinction that breaks it
The moment a message is about one child, the group is the wrong room. Your daughter did not eat lunch today. October's fee is still pending. Aarav had a fall in the play area at twenty past eleven and we put ice on it. Please update the emergency number, the old one is unreachable.
None of those can go to the group, so they go to a personal chat from the teacher's own number. That is where the real damage starts, and it is not about privacy — it is about custody of the record. The history now lives on a personal phone. The teacher resigns in April and the history walks out with her. Four months later a parent asks what you told them in July, and the answer is sitting in a handset somebody handed back.
There are three audiences in a preschool, not one: the whole centre, one classroom, and one child. Announcements need to reach all three — with attachments, and with an expiry, so last term's sports-day circular falls off the parent feed instead of sitting there confusing people. What matters is that all three are addressed from the centre, not from a staff member's SIM.
The test is not whether you can send the message. It is whether the centre still has it after the teacher who sent it has resigned.
The daily report parents actually open
The highest-value thing a preschool sends is exactly the thing a group chat cannot carry: a report on one child, at the end of one day.
What goes in it is not complicated — overall mood, the nap window, what was served at each meal and how much of it was actually eaten, the activities, diaper or potty notes for the small ones, a line of teacher's remarks, a photograph or two. Read it back as a parent and you can see why it lands. A mother who dropped a two-year-old at half past eight has been carrying a low hum of worry all day: did he sleep, did he eat, was he all right. Forty photographs of somebody else's rangoli do not answer that. Six lines about her son do.
It matters that the report is composed as a draft through the day and published at the end of it. A parent should not be watching a half-written note assemble itself in real time, and a teacher should not be writing for an audience while she is still supervising a room.
The compounding effect is on the relationship, not the software. A parent who has read something specific about their own child every evening for a term arrives at a parent-teacher meeting informed instead of anxious. That is a different conversation, and you can feel the difference across a whole centre.
Fees in a group chat: don't
Somewhere in India this evening, a preschool will post a list of names and pending amounts into a class group. It works, in the narrow sense that people pay. It is also a small public humiliation, and it is the fastest available way to lose a family that was going to pay on Friday anyway.
Money is per-child by definition. A fee message has to be private, it has to carry the actual bill rather than a number somebody typed from memory, and it has to carry a way to pay. Collecting over a group chat means payments arrive as unattributed UPI credits that someone matches by hand against names in a conversation — which is fine at twelve children and impossible at ninety. A hosted pay-link attached to the invoice puts the money against the right bill without anyone doing detective work.
And reminders should run on a schedule rather than on the head teacher's conscience. Coming-due and overdue bills chased automatically, each nudge moving from pending to sent to done, so the person running the centre is not also the collections department every last week of the month.
Photographs of other people's children
This is the uncomfortable section, and it is the one most owners have genuinely not thought through. A class group of sixty numbers is a directory of sixty families that you have handed to sixty near-strangers. Everyone in it can see everyone else's phone number, and you vetted none of them beyond the fact that they pay a fee.
Then there are the photographs. A teacher posts a nice group shot from a birthday. One parent forwards it to a family group, someone forwards it again, and a picture of eleven children is now somewhere nobody agreed to. Most of the time nothing comes of it. But there is always a family for whom it matters — a custody situation, a relative they are keeping distance from — and a group of sixty gives them no way to opt out of anything.
India's data protection law is explicit that children's personal data deserves extra care and that processing it needs verifiable consent from a parent or guardian. You do not need to become an expert in it to draw the practical conclusion, which is straightforward: a photograph of a child should reach that child's guardians, and nobody else, unless the other guardians agreed to it. A per-child daily report gets you there structurally. The photo of Aarav goes to Aarav's guardians because there is nowhere else for it to go, and no member of staff has to remember a rule at half past five.
What a preschool system must do before it is worth the money
Plenty of products will sell you a parent app that is a noticeboard with a login. That is a worse group chat. The honest bar is higher:
- Address all three audiences — whole centre, one classroom, one child — with attachments and an auto-expiry so stale notices drop off
- Treat the daily report as a first-class thing: drafted through the day, published to that child's guardians
- Hold real child and guardian records — date of birth, allergies, medical notes, relations, who is authorised to collect — so the same data drives the gate and the bill
- Bill and collect: a monthly invoice per child with a pay-link, and due-date reminders that run without a human starting them
- Publish the meal menu, because what he ate is the second question every parent asks
- Keep every one of those records at the centre, not on a phone that leaves in April
If a product cannot do the per-child half of that list, it is not replacing your group chat. It is adding a second place to check.
Teacher effort: the make-or-break constraint
This is where most preschool software actually dies, and it has nothing to do with features.
A teacher has fifteen three-year-olds and no spare hands. If publishing a daily report takes six minutes a child, it will happen enthusiastically for eight days and then stop. And a system that parents were promised and then quietly stopped receiving is worse than never having had one — you have converted a nice surprise into a broken promise.
So the report has to be mostly taps. The meal menu is already published centrally, so meals come prefilled and the teacher only marks how much was eaten. Mood is a tap. The nap window is two taps. The typed part is one line, and on a hard day it should be allowed to stay empty. Anything more ambitious than that is a design that has never met a Wednesday.
Buy the tool your least tech-confident teacher can finish a whole room on, at five o'clock, with a child pulling at her dupatta.
Test that before you sign anything. Not a demo where a salesperson fills one child's report on a laptop — sit the teacher who will actually use it in front of it, hand her a real room, and time her.
Switching mid-term without confusing parents
Do not kill the group. Nobody will thank you, half the parents will not move on day one, and you will spend a fortnight answering the same question in two places. Run them together and let the group shrink into what it was always best at.
- Get the child and guardian records in first — correct phone numbers, relations, allergies, and who may collect. Nothing downstream works until that is right.
- Run both for two or three weeks: daily reports and fee bills through the new system, the group still carrying chatter and a nudge that the reports are there
- Tell parents once, plainly, what moves and what stays — and then keep to it, because a rule you announce and abandon costs you more than never announcing it
- Move fees second, not first. A parent's first experience of the new thing should be six warm lines about their child, not a demand for money.
- Then stop posting notices to the group. When the noticeboard moves and nobody complains, the switch is finished.
What you end up with is not a group chat replaced. It is a group chat relieved of duties it was never built for — the child, the money and the record — and left to do the thing it does better than any software you could buy: sixty parents talking to each other about a birthday party.