KIDUART school ERP
Messaging and notificationsLive

MSG91 with KIDUART

MSG91 is the practical choice for Indian schools: domestic transactional pricing, a sender ID parents recognise, and DLT template registration handled on your own account. KIDUART sends absence alerts, fee reminders and OTPs through it and records the delivery report against each message.

Transactional SMSDLT sender IDDelivery reports

What you get

  • Domestic transactional pricing suited to daily school volume
  • A registered sender ID so parents recognise the school
  • DLT-registered templates mapped to school events
  • Delivery reports written back to the communication log

The connection, hop by hop

How MSG91 actually works here

No hand-waving about being 'seamlessly integrated'. This is the path a single event takes, end to end.

  1. DLT templates registered

    Your absence, fee and OTP templates are registered on DLT under your own entity, as Indian regulation requires.

  2. Event fills the template

    KIDUART fills the approved template with values from the student, fee or login record.

  3. MSG91 sends it

    The message goes out on your sender ID to the guardian numbers on record.

  4. Delivery report stored

    MSG91's report updates the message record, so failed numbers surface for correction.

Keys, data and the bill

Who holds the credentials

Your MSG91 auth key and sender ID, stored against your school's messaging configuration.

Where the data sits

KIDUART keeps the template used, recipient and delivery status.

Who gets billed

SMS credits are purchased and billed on your own MSG91 account.

Where it lands in the product

The modules this integration writes into

An integration is only useful if it writes into the module your staff already work in. These are the exact modules involved.

Communication

Messaging

Linked workflows in the product

Open Messaging

Security & Access

Security Alerts

Linked workflows in the product

Open Security Alerts

Setup, step by step

Connecting MSG91

  1. Create an MSG91 account in the school's name

  2. Register your entity, sender ID and templates on DLT

  3. Share the auth key and sender ID with us

  4. Map each DLT template to the KIDUART event that uses it

  5. Test on a staff number, then enable for parents

What you need on your side

  • An MSG91 account with a DLT-registered sender ID
  • DLT-approved templates for each transactional message
  • Guardian mobile numbers on student records
Scope this on a call

Questions schools ask

MSG91, answered plainly

Who registers the DLT templates?

The school does, on its own entity, because the sender ID belongs to you. We tell you exactly which templates to register and map them once approved.

What happens if a template is rejected on DLT?

That event simply does not send until an approved template exists. Nothing else stops, and the message stays queued as failed rather than silently dropped.

Live demo

See MSG91 in a live demo

We will run the connection on screen with your own scenario your fee book, your parent groups, your school accounts.

  • 30-minute walkthrough

    Booked around your school hours

  • Run on your own data

    Your fee heads, classes and staff roles

  • No card, no lock-in

    Nothing is charged to see the product