DLT registration for school SMS, explained for schools

What DLT is, without the jargon

Indian telecom regulation requires every organisation that sends commercial or transactional SMS to register itself, and to pre-register both the sender ID and the exact wording of each message. Operators maintain this registry, and anything that does not match a registered entry is rejected before it reaches a parent.

The intent was to stop spam and spoofing. The side effect for schools is that SMS is no longer something you can simply switch on — there is paperwork first, and it belongs to the school.

The three things you register

• ▸The entity — your school. Registered once, with your school's own documents. You receive an entity identifier that follows you across operators.
• ▸The header, or sender ID. The short code a parent sees as the sender, six characters, usually an abbreviation of the school name. Pick it carefully: parents recognise it, and it is effectively your SMS brand. A transactional header is distinct from a promotional one.
• ▸Content templates. The exact wording of every message you will send, with placeholders for the parts that change. "Dear {#var#}, your child {#var#} was marked absent on {#var#}." You register a template per message type — absence, fee due, fee received, exam schedule, holiday notice, meeting invitation.

Register more templates than you think you need, including the ones you might use next term. Adding one later is routine, but it takes days you will not want to wait during an exam week.

Why messages stop arriving

Almost every school that says "SMS has stopped working" is hitting one of these.

• ▸The wording changed. Somebody improved a sentence. The template no longer matches what was approved, and the operator drops it. The fix is to re-register the new wording — or revert.
• ▸A variable is longer than allowed. A very long student name or a note pasted into a placeholder can push the message outside the registered shape.
• ▸The wrong header. A promotional header used for a transactional message, or vice versa, is rejected or delivered under the wrong rules.
• ▸The number is on a preference list. Fully blocked promotional preferences do not stop genuine transactional service messages, but a message classified as promotional to that number will be stopped.

Who pays, and who owns it

Operators charge a one-time registration fee for the entity and header — the amounts change, so check the current figures with your SMS provider rather than trusting a number in an article. Message charges are separate and per message.

The important part is ownership. The entity and header are registered in your school's name. That means two things: parents see your school as the sender, and if you ever change software vendor, the registration stays with you. Be cautious of any arrangement where messages go out under a vendor's header — it is convenient at first, and it is their asset, not yours.

A practical order of work

• ▸Pick your SMS provider first — they walk you through the operator portal, because they do it every week.
• ▸Register the entity with your school's documents.
• ▸Register one transactional header. Keep it recognisable: parents ignore what they do not recognise.
• ▸Write every template you will need this year, including fee reminders, absence, receipts and notices, and register them together.
• ▸Send one live message per template and confirm delivery before you rely on it for a fee cycle.
• ▸Keep the approved wording somewhere your staff can see, so nobody edits a live template casually.

What this means when you choose school software

Ask three questions of any vendor. Does it send through our own registered header? Does it map our approved templates, or force its own wording? And when a message fails, can we see which one and why?

A system that hides delivery failures will quietly stop reaching parents, and you will find out when somebody complains about a fee notice they never received.