SMS notifications with KIDUART
Not every parent has a smartphone, checks email, or installs an app, but almost every parent receives SMS. KIDUART sends transactional SMS through a supported gateway Twilio, MSG91 or Amazon SNS using templates you manage in-product, so an absence alert or a fee reminder reaches the guardian on the same day rather than in a diary note the child forgets to show.
What you get
- Same-day absence alerts to the guardian on record
- Fee due and receipt confirmations by SMS
- Login OTP and password reset codes on the same gateway
- Targeted sends by class, section or staff group
- Delivery callbacks recorded against the communication log
The connection, hop by hop
How SMS notifications actually works here
No hand-waving about being 'seamlessly integrated'. This is the path a single event takes, end to end.
Event triggers a message
Absence, fee due, notice, OTP you decide which events are allowed to send SMS at all.
Template resolved
The approved template for that event is filled from the student or fee record, keeping wording consistent and DLT-compliant.
Gateway sends it
The configured provider Twilio, MSG91 or Amazon SNS delivers to the guardian number on the student record.
Status written back
Provider delivery callbacks update the record, so a failed number is visible instead of silently lost.
Keys, data and the bill
Who holds the credentials
Your gateway account credentials and sender ID, held against your school configuration.
Where the data sits
KIDUART records which template was sent to which number and the delivery status returned.
Who gets billed
SMS credits are billed by your provider on your own account, so you control pricing and volume.
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.
Setup, step by step
Connecting SMS notifications
Pick your gateway Twilio, MSG91 or Amazon SNS
Share the credentials and approved sender ID
Map which events send SMS: absence, fee due, notice, OTP
Approve the message templates for each event
Send a test to a staff number before enabling for parents
What you need on your side
- An SMS provider account with a registered sender ID
- DLT template registration where Indian regulations require it
- Guardian mobile numbers present on student records
Questions schools ask
SMS notifications, answered plainly
Who pays for the SMS credits?
SMS is billed by your provider on your own account, so you keep control of credits and pricing. KIDUART sends through it and records what was sent.
Will parents get flooded with messages?
No. You decide which events trigger an SMS. Most schools keep SMS for absence, fee dues and urgent notices, and use WhatsApp, app notifications or email for everything else.
Can we change gateway later?
Yes. The gateway sits behind one interface, so moving from one provider to another is a credential change, not a rebuild of your templates.
Also in messaging and notifications
Related integrations
WhatsApp Business
Reach parents on the channel they actually read, using approved WhatsApp Business templates from the school's own number.
Twilio
Use Twilio as your SMS gateway, including messaging services and delivery status callbacks.
MSG91
Use MSG91 as your Indian SMS gateway with DLT-registered templates and a school sender ID.
See SMS notifications 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