TRAI DLT, honoured from day one. Your sender header, your templates, ready in hours.

How most Indian schools live with TRAI DLT today

In most Indian schools the SMS system was set up years ago and nobody has touched it since. The accountant remembers there is an SMS gateway login somewhere; the IT-savvy son of the principal set it up one Sunday and then left for college. The school's 6-character sender header is registered with TRAI's DLT system on the school's behalf, the four or five most-used templates are approved, and SMS goes out every fee-cycle morning the way it has for the last three years. Nobody asks how it works, and that is fine — until the day TRAI changes a rule.

May 2025 was that day for thousands of Indian schools. TRAI mandated that every SMS template now carry a suffix tagging the message type — transactional, promotional, service or government — directly in the sender header. Schools that did not update saw their SMS delivery quietly drop by 40 percent overnight. Receipts that used to arrive at 9 a.m. arrived at midnight, or did not arrive at all. The accountant did not know why. The vendor's support team was unreachable. Parents called the office asking 'kal ka receipt aaya nahi sir, kya hua?' and the office had no answer, because the office did not know SMS was a regulated business that quietly broke when TRAI tightened the screws.

We built SMS for schools to take the regulator out of the office's daily worry. The school's existing TRAI DLT registration — the Principal Entity, the sender header, the approved templates — is honoured by Inkwelly on day one. The May 2025 suffix mandate, and every TRAI rule change after it, is applied to every SMS we send for the school, automatically, with no two-week re-registration wait, no overnight delivery drop and no panicked support call to MSG91 or Fast2SMS on a Saturday morning.

How SMS in Inkwelly actually works

From the school's Communications screen the office manager opens Connect SMS and picks the vendor the school already uses — MSG91 or Fast2SMS. The two are the dominant Indian school SMS gateways, and most schools already hold a TRAI DLT registration with one of them. The accountant pastes in the school's MSG91 or Fast2SMS authentication key (the long alphanumeric string the vendor gave the school on day one), the 6-character sender header that parents recognise on their phones, and the school's Principal Entity ID from the DLT portal. Inkwelly verifies the credentials with the vendor in one round-trip and pulls back the school's approved template list — every template, with its DLT template ID, the placeholders the school filled in and the current TRAI DLT category. Setup takes about 8 minutes for a school that already has an MSG91 or Fast2SMS account.

From that moment every SMS the school sends — the fee receipt, the attendance absent alert, the exam-result line, the parent-teacher meeting reminder — goes through Inkwelly to the vendor and out to the parent's phone with the school's sender header on it. Parents see SUNRSI (the school's 6-letter ID) at the top of the SMS, not a generic shortcode and not Inkwelly's name. The TRAI DLT template ID is attached on the wire, the message type suffix (transactional, promotional, service or government) is applied to the header in real time, and TRAI's reporting backend sees a perfectly compliant SMS from the school.

When TRAI changes a rule — and they do change rules, every six to twelve months — Inkwelly's job is to absorb the change before the school's next fee cycle. May 2025's header-suffix mandate was applied to every Inkwelly school's SMS within 48 hours of TRAI publishing the notice. The principal did not have to do anything. The vendor's support line stayed quiet. The next morning's fee receipts went out at 9 a.m. with the right suffix on the header and the parents on the receiving end saw the same SMS they always do.

When a parent replies STOP to a promotional SMS, the unsubscribe is logged permanently inside Inkwelly and that parent stops receiving promotional SMS forever. Transactional fee receipts and attendance alerts still reach her — that is how TRAI's rules work — but the school cannot send her open-day invites or summer-camp marketing again, even by mistake. The audit trail is preserved for the full retention period TRAI requires.

See the SMS setup flow

“Pehle May ke baad hamare SMS delivery achanak 40 percent gir gaye the, kuch samajh nahi aaya tha kya hua hai. Inkwelly aane ke baad hum kuch nahi karte SMS ke baare me — TRAI ka koi naya rule aata hai, woh log handle kar lete hain, fee receipt waise hi parents ko 9 baje pahunchti hai. Headache khatam.”

Five real school days, one SMS setup

1. The 1st of the month, every month — fee receipts. The accountant runs the fee cycle in the Fees module at 9 a.m. 380 fee receipts go out as SMS over the next 10 minutes — each with the school's 6-character sender header, the transactional suffix, the receipt number, the parent's child's name and the amount paid. By 9:30 a.m. the office screen shows 374 delivered, 5 failed (the 5 failed numbers are flagged for the office to call the parents and update the phone number on the Student Information profile).

2. The day TRAI changes a rule. TRAI publishes a notice on a Thursday evening tightening the header-suffix rule. By Saturday morning Inkwelly has rolled out the change across every school's SMS pipeline. The principal of a Tier-2 CBSE school in Bahraich never sees the notice, never reads the rule, never calls anyone. Monday's fee receipts go out at 9 a.m. with the right suffix on the header. Parents see the same SMS they always see.

3. Result day morning. Class 10 board results are out. The exam controller sends the result line as SMS to all 240 Class 10 parents — each parent receives one line 'Your child's overall percentage is X. Detailed marksheet on WhatsApp.' SMS arrives in under a minute (SMS is the fastest channel India has). For parents who do not use WhatsApp — about 8 percent of the school's families on average — SMS is the primary result-day channel, and they appreciate not being left out.

4. Promotional admission campaign — January. The school runs a Class 1 admission campaign for the next academic year. The promotional SMS goes to a pre-approved audience of about 2,400 prospective families collected at open days during the year. The promotional suffix is on the header, the STOP keyword is included in every message body (as TRAI requires for promotional SMS), and 38 parents reply STOP. Those 38 are removed from the school's promotional list permanently — but they continue to receive transactional admission-status SMS if they end up applying, because TRAI allows that distinction.

5. The Saturday night SMS panic call. The vendor's web console goes down on a Saturday evening at 9 p.m. — a real thing that happens periodically with MSG91 and Fast2SMS during their maintenance windows. Inkwelly's dashboard shows the office that SMS sending is paused on the vendor side. The office knows immediately without anyone calling. The Sunday morning's pending fee reminder is queued, picks back up automatically when the vendor recovers at 2 a.m. that night, and the office reads about it on Monday morning rather than at 11 p.m. on Saturday.

See SMS on your school's existing TRAI DLT registration

30-minute walkthrough on the Inkwelly demo school. Bring your school's MSG91 or Fast2SMS login, your TRAI DLT Principal Entity ID and your last month's SMS volume. We will show how the same sender header, same templates and same vendor account can send every school SMS — fee receipts, attendance, results — through Inkwelly's office surface, with TRAI rule changes absorbed automatically.

Limits, safety and the small print

TRAI is the regulator, not Inkwelly. Sender headers, template approvals, message-type categorisation and the STOP-keyword rule are all TRAI's. Inkwelly is the office's working surface — it pulls TRAI's rules and the vendor's responses into one place, translates them into plain language, and lets the office act on them without opening the DLT portal or the vendor's console. If TRAI flags a school's sender header for repeated abuse (sending promotional SMS to STOP-listed parents, sending without category match, ignoring re-registration deadlines), Inkwelly cannot override that — the school will need to fix the underlying behaviour and ask the vendor to re-register the header with TRAI. We coach every school on day-one setup so this almost never happens.

Per-SMS pricing is set by the vendor, not Inkwelly. MSG91 and Fast2SMS publish their own per-SMS rates — typically ₹0.18 to ₹0.25 per transactional SMS in India in 2026, slightly higher (₹0.25 to ₹0.40) for promotional SMS because TRAI charges more for promotional, and the OTP service category sits between the two. Inkwelly does not add a per-SMS margin on top. A typical Indian CBSE school with 400 students sends about 4,000 to 8,000 transactional SMS per month, which works out to ₹750 to ₹2,000 per month in vendor charges. Inkwelly's monthly subscription is separate and disclosed on the pricing page.

Templates are approved, not authored, by Inkwelly. Every SMS template a school sends must be on the school's TRAI DLT template list, and only the school's Principal Entity admin can submit a template for approval. Inkwelly makes the submission painless — you copy the exact body Inkwelly shows you, paste it into the DLT portal, click submit, and approval typically comes back in 4 to 24 hours. We cannot bypass the DLT portal. No vendor can. That is the regulator's rule and it exists for the right reasons.

Promotional SMS needs explicit, recorded consent. Transactional SMS (fee receipts, attendance, results, admit cards) can go to every enrolled parent without explicit consent because the parent is a customer of the school. Promotional SMS (open-day invites to non-enrolled families, summer-camp marketing, alumni messages) requires explicit consent recorded against each parent, with a working STOP path. Inkwelly enforces this distinction at the audience level — promotional templates can only be sent to audiences marked as consented, and parents who reply STOP are moved out permanently.

If the school leaves Inkwelly, the DLT registration stays with the school. The TRAI DLT Principal Entity, the sender header and the approved templates are registered in the school's name — not Inkwelly's. If the school moves to another ERP, the registration, the header and the templates all stay with the school, exactly where they are. Inkwelly cannot lock a school into its SMS identity and we have built the setup specifically so it cannot.