How to send an absent SMS to parents, automatically

What has to be true before any message can go out

Automatic messaging sounds like a software problem. Most of the time it is a data problem, and the schools that get it working fix these four things first.

• ▸One mobile number per student, and the right one. Schools usually hold the father's number, the mother's, and whatever number was written on the admission form three years ago. Decide which number is the messaging number and clean that column before you start — a wrong number is worse than no message, because the parent who needed it never learns anything was wrong.
• ▸Attendance recorded digitally, at a fixed time. A message can only be sent from a register that exists in a system by, say, 9:30 a.m. If the register reaches the office at lunch on paper, no software can send a morning message.
• ▸A decision about who counts as absent. Late arrivals, half-days, approved leave and sick notes should not all trigger the same message. Schools that skip this send an absence SMS to a parent who dropped their child at the gate at 8:50, and the credibility of every later message drops.
• ▸A sender ID your school is registered to use. In India you cannot send business SMS from a random number. This is the DLT requirement, and it is the step that catches most schools out.

Send on exception, not on attendance

The first instinct is to message every parent every day: "Your child is present." It is a bad instinct, for three reasons.

It costs money — a 1,000-student school sends 220,000 messages a year instead of about 15,000. It trains parents to ignore you, because a message that always says the same thing stops being read by the second week. And it hides the one message that mattered, on the morning a child did not reach school.

Message on exception: absent, or long unexplained absence. Keep the daily record inside the app for parents who want to check it.

What it costs

Two separate costs, and schools often conflate them.

• ▸The software that marks attendance and decides who to message. This is your ERP or attendance system.
• ▸The messages themselves, billed by an SMS provider per message, through your own registered sender ID. Transactional SMS in India is cheap per message, but it is a real running cost that scales with how many you send — another reason exception-only matters.

Ask any vendor plainly whether SMS charges are included or billed separately. Both models exist, and the difference shows up on your second invoice, not your first.

The DLT step, in one paragraph

Indian telecom regulation requires commercial SMS to go out under a registered entity, a registered sender ID (the six-character header parents see), and pre-approved message templates. Your school registers as the entity; the templates are the exact wording, with placeholders for the child's name and date. A message that does not match an approved template is rejected by the operator, which is why schools sometimes see messages silently fail after a wording change.

This registration belongs to your school, not to your software vendor — it is your name on the header parents see. Any ERP worth using will send through your sender ID rather than its own.

What usually breaks

• ▸Marking after the cut-off. If a teacher marks the register at 2 p.m., the "morning" message arrives in the afternoon and the parent has already collected the child. Set a cut-off and show teachers who has not marked.
• ▸Duplicate students. Two records for one child, from an admission and a re-admission, means two messages and an angry parent.
• ▸Template drift. Someone improves the wording, the template no longer matches the registered one, and delivery stops without an error anyone notices. Check a live delivery report after any wording change.
• ▸Siblings. Three children, one parent number, three messages on the same morning. Decide whether that is what you want before a parent tells you it is not.
• ▸Nobody watching failures. A number that has stopped working fails silently every single day. Someone should see a bounce list monthly.

Doing it without an ERP

It is possible, and for a small school it can be enough: keep attendance in a shared sheet, filter the absentees, and paste that column into a bulk SMS panel that already has your registered templates. Budget 15 to 20 minutes a day, and accept that it stops the week the person who does it is on leave.

The reason schools eventually automate is not the 20 minutes. It is that the manual version silently stops on exactly the days that matter — exam week, festival week, the week everyone is busy.