One engine for WhatsApp, SMS, Email, and Push.
Every module — fee, attendance, homework, transport, exams — sends through the same automated engine, with consent gates, quiet hours, and a fallback channel when the first one doesn't land.
Every channel, one engine, no module sends directly.
No module calls a WhatsApp or SMS sender directly — every notification goes through the same event → rule → template → channel pipeline, so behaviour is consistent everywhere.
Template-based WhatsApp messaging for fee reminders, attendance alerts, homework, and announcements — the channel parents actually read.
SMS and email as reliable fallback channels, with the same templates and rules driving delivery as WhatsApp and push.
In-app push for parents and staff on the mobile app, with deep links straight to the relevant screen — a fee due notice opens the fee screen, not the app's home page.
Parent consent is tracked per channel; a parent who's opted out of WhatsApp for marketing still gets critical fee-due and safety alerts through an allowed channel.
Non-urgent messages are held during configured quiet hours and released afterward — no fee reminder landing on a parent's phone at 11 PM.
A failed WhatsApp delivery automatically retries and falls back to SMS, with a dead-letter queue for anything that still doesn't land, so critical alerts don't silently disappear.
Send to a whole school, one class-section, or a subject-election group — audience expansion handles students, parents, teachers, and staff scoped correctly.
Every send, delivery status, and consent decision is logged — useful the day a parent disputes whether they were notified.
Feedback forms, surveys, quick polls, and consent/acknowledgement requests — published through this same engine, with audience targeting, identified or anonymous responses, and live analytics.
What administrators ask first
Which WhatsApp provider do you use — is it the official Business API?
Yes — WhatsApp messaging runs through the official Business API via a configured provider, not an unofficial or scraping-based integration that risks a number getting banned.
What happens if a WhatsApp message fails to deliver?
It retries automatically and falls back to SMS if WhatsApp still fails, so a fee-due or safety alert doesn't silently vanish because one channel had an outage.
Can a parent opt out of promotional messages but still get safety alerts?
Yes — consent is tracked per channel and per message category, so an opt-out from general announcements doesn't block a critical attendance or safety notification.
Do we set quiet hours per school, or is it one global setting?
Quiet hours are configurable, with a sensible IST default out of the box, so a reminder queued in the evening is held and released the next morning instead of landing at night.
Do we have to configure every module's messages separately?
No — every module (fee, attendance, homework, transport, exams, and more) publishes through the same engine, so rules, templates, and consent settings apply consistently everywhere, not per module.
Do you also handle feedback forms, surveys, and polls, or is that a separate tool?
Same engine — a published feedback form, survey, or poll notifies its target audience through this pipeline, and a reminder to non-responders is scheduled the same way any other message is. Responses can be Identified, Confidential, or fully Anonymous depending on the form.