Why Your School’s SMS to Parents Is Failing Silently — and How DLT Registration Fixes It

Here is a problem that costs Indian schools more goodwill than almost anything else in their software, and that most of them do not know they have: the SMS you send to parents may not be arriving, and your software is probably telling you it did.

Not "some messages are delayed". Dropped entirely, at the operator, with no error returned to the sender. The school sees a healthy sent count, the parents receive nothing, and the first anyone learns of it is when a father says he was never told his daughter was absent.

This guide explains why that happens, how to check whether it is happening to you in about five minutes, and what to do about it. It applies whichever school software you use — this is a telecom regulation, not a product feature.

What DLT is, briefly

DLT stands for Distributed Ledger Technology. Under TRAI’s Telecom Commercial Communications Customer Preference Regulations, every organisation sending commercial or transactional SMS in India has to register on a DLT platform operated by the telecom providers. Three things get registered:

• The entity — your school, verified against its PAN and GST details.
• The header, also called the sender ID — the six-character alphabetic string parents see instead of a phone number, such as STECHY or an abbreviation of your school’s name.
• The template — the exact wording of each message type you intend to send, with variables marked.

The regulation exists for a good reason: it is what made unsolicited spam SMS traceable to a real registered entity. The side effect for legitimate senders is that anything not registered is discarded.

Why the failure is silent, and why that matters

This is the part that catches schools out. When an operator rejects a message for a DLT mismatch, it does not, in the general case, return a useful error to the sending application. From the software’s point of view the message was accepted by the gateway and handed on. So it is logged as sent.

The result is a class of bug that is invisible from inside the system. Every dashboard is green. The campaign screen shows 847 messages sent. The parents received none of them.

Compare that to email, where a bounce comes back and lands in a bounce report, and the failure is at least visible. With SMS you have to go and look for the absence of a delivery, which almost nobody does unless they already suspect a problem.

How to check, in five minutes

Open the delivery report for a recent campaign — not the send log. The distinction is the whole point:

• A send log records that your software handed a message to the gateway.
• A delivery report (DLR) records that the operator delivered it to a handset.

Compare the two counts. Rough expectations for transactional SMS in India:

If you cannot find a delivery report at all, ask your vendor for one specifically. It is the number that tells you the truth, and any messaging module worth having exposes it.

The three things that break a registered template

Registration is not one-and-done. Three mismatches account for most ongoing failures.

1. The text no longer matches

The message your software sends must match the registered template exactly, apart from the variables. Somebody edits the wording to be friendlier — adds an exclamation mark, changes "Dear Parent" to "Dear Parents" — and the message stops matching. The operator drops it. No error.

This is the most common cause of a campaign that worked last term and does not work this term.

2. Variables in the wrong shape

Templates mark variables with placeholders, and operators enforce rules about them: how many are allowed, minimum length of the surrounding fixed text, and whether a variable may sit at the very start of the message. A template that puts a student’s name as the first characters is frequently rejected, because that pattern is what spam looks like.

3. Header not linked to the template

Headers and templates are registered separately and then associated. A newly approved template sent under a header it is not linked to fails in exactly the same silent way.

What a school actually needs to register

Most schools need somewhere between six and twelve templates. Registering them in one batch is far less painful than discovering each gap the week you need it.

How to register: the sequence

1. Choose your operator’s DLT portal. Jio, Airtel, Vodafone Idea and BSNL each run one; registering on any one propagates to the others. Most schools use whichever their SMS provider recommends.
2. Register the entity. PAN, GST certificate, a letter of authorisation on school letterhead, and an authorised signatory. Expect a few working days.
3. Register the header. Six alphabetic characters, tied to your entity, and classified as transactional or promotional. A day or two.
4. Register each template. Submit the exact text with variables marked. Typically same-day to two days each.
5. Link headers to templates, and give the template IDs to your software.
6. Send one test to a real handset and check the delivery report, not the send log.

Two weeks end to end is a realistic plan for a first registration. Do it before your session starts, not during admission season.

Why we make templates mandatory in the software

This is a deliberate design decision and it is worth explaining, because it will occasionally be inconvenient.

Our communication module will not send a campaign without an approved template. You cannot type a free-form message and blast it to parents over SMS. That is more restrictive than some products, and schools occasionally push back on it.

The reason is that the alternative is worse. Software that lets you send anything will happily report "1,240 sent" for messages the operator discarded, and the school will believe that number. We would rather be inconvenient once, at setup, than show you a comforting figure that means nothing. The delivery report sits on the same screen as the campaign for the same reason.

The alternative most schools are moving to

WhatsApp has quietly become the primary channel for a lot of Indian schools, and for good reasons: messages are read, delivery and read receipts come back, and the message can carry a payment link that actually works. It has its own template approval through Meta, which is generally faster than DLT, and it is charged per conversation rather than per message.

A sensible arrangement for most schools:

• WhatsApp for anything that must be read — absence alerts, fee reminders, results.
• SMS as the fallback for parents without WhatsApp, and for OTPs.
• E-mail for anything long or formal: circulars, receipts, report cards as attachments.
• The parent app for anything that benefits from a notification and a tap-through.

Our guide to parent communication goes into the channel mix in more depth, and the integrations page lists what connects.

The short version

If your school sends SMS in India and you have never looked at a delivery report, look at one today. Unregistered or mismatched DLT templates fail silently, and a healthy sent count proves nothing. Register your entity, header and every template you need in one batch before the session starts; keep the wording frozen once approved; and judge every campaign on delivered, never on sent.

Primary sources

The rules described above come from the regulators and portals themselves. Where this guide and an official source disagree, the official source is right.

• Telecom Regulatory Authority of India — The regulator behind the DLT regime and the TCCCPR rules that make registration mandatory.