All modules Communication & Family Engagement

SMS Alerts software for Indian schools

Configured transactional SMS

Feature identity
SMS Alerts
An illustration, not a screenshot. The interactive example below shows what this capability actually does.

SMS Alerts in a school workflow

Example provider evidence

Evidence layer 01MSG91 SMS with a DLT-registered sender and per-type template IDs
Evidence layer 02Exponential-backoff retries plus an operator “retry failed” sweep
Evidence layer 03STOP/START opt-outs honoured at the single send funnel

The configured provider's returned state remains distinct from the school record.

MSG91 SMS with a DLT-registered sender and per-type template IDs
Exponential-backoff retries plus an operator “retry failed” sweep
STOP/START opt-outs honoured at the single send funnel

Code-native illustrative example · not live product UI · no customer dataExample labels and outcomes come from this capability's reviewed catalogue record.

Product scope

What it does

Transactional SMS through India's DLT regime done right: MSG91 Flow-based sends with a registered sender ID and a per-message-type DLT template ID — one template is never reused for every body, which is exactly what gets schools blocked. Delivery statuses flow back into one unified log with retry and dead-letter handling.

The school problem

School teams need a dependable way to handle SMS Alerts: Configured transactional SMS. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Configured transactional SMS.

MSG91 SMS with a DLT-registered sender and per-type template IDs
Exponential-backoff retries plus an operator “retry failed” sweep
STOP/START opt-outs honoured at the single send funnel
A per-message delivery-event timeline in the log

Operational result

What your school gets

DLT-aligned transactional SMS attempts with per-type templates, retry handling and provider-returned delivery evidence.

Access and ownership

Who typically uses it

Communication administrator
School administrator
Template approver
Message recipient

What each person can actually see depends on the role you give them and which classes or records you assign.

Availability and setup

What to confirm before rollout

Communication & Family Engagement catalogue capability

MSG91 credentials, registered sender ID, DLT template IDs, consent and applicable policy
Requires configured provider credentials, approved templates, consent and applicable DLT rules.

Connected operating context

Available workflows

These are the documented neighbouring capabilities that school teams may review with this module. A related page does not imply that every hand-off is automatic or enabled in every plan.

Explore all modules

Buyer questions

Frequently asked questions

The questions school owners ask before they subscribe: what it does, who can see it, and what to set up first.

Does SMS Alerts work on its own?

Announcements, Circular Management, Emergency Alerts, Attendance Alerts are the documented neighbouring capabilities. They help a school evaluate the surrounding hand-offs, but a related page does not mean every integration is automatic or included in every plan.

What should our school prepare before enabling SMS Alerts?

MSG91 credentials, registered sender ID, DLT template IDs, consent and applicable policy. Requires configured provider credentials, approved templates, consent and applicable DLT rules.

Is AI used in SMS Alerts?

No AI capability is asserted for SMS Alerts. Its documented work remains controlled by school records, roles and permissions.

How do we confirm the plan and implementation scope?

Plan inclusion and rollout scope depend on the live plan matrix, readiness state and your school's written proposal. The demo team will confirm the applicable boundary before rollout.

Related evaluation guides

Assignment & Notices

See the Communication & Family Engagement workspace Compare plans and commercial costs

See it in your school context

Run sms alerts the connected way.

See how this workflow fits your school's current records, roles, plan and rollout requirements.