Built & live

Communications

A school constantly needs to tell people things — a holiday notice, a fee reminder, an exam date, a note to one parent. This module brings all of that into one place and sends it through whichever channel fits: an in-app notice, a phone notification, an SMS, or an email.

What it does

Communications gives the school four ways to reach a person — an in-app notice, a phone push notification, an SMS, and an email — so the right message reaches parents and staff whether or not they have the app open.

Every SMS and email is logged, and each school plugs in its own SMS, email and push accounts — so messages come from the school's own identity, and the school stays in control of its messaging costs and data.

Inside the module

Announcements

The school notice board, targeted to exactly who should see it — the whole school, a specific class or section, teachers only, or parents only. Notices carry a title, body and optional attachment, can be pinned to the top, and can be scheduled to appear later and expire automatically.

Notifications

The short "bell" alerts inside the app and as pop-ups on the phone. Often generated automatically by other modules — a fee reminder, a result published, a leave approved — and each is tracked as read or unread per person.

Direct messages

A private, one-to-one or small-group conversation — for example a parent messaging their child's class teacher, or the office messaging a parent. Messages live in a thread, can carry an attachment, and show who has read them.

SMS & Email

Reach parents on their phone and inbox — the channels that work even when the app isn't open. These power fee reminders, important alerts and login details, with support for DLT compliance: a school registers its TRAI-approved sender IDs and templates, and only those can be sent.

Delivery logs

Every SMS and email is logged — who it went to, the content, the status (queued, sent, delivered or failed) and even the cost for SMS. So the office can prove a message was sent and spot delivery problems.

Provider setup

Each school plugs in its own SMS provider, email (SMTP) account and push credentials. Secrets are stored encrypted, can be tested before going live, and start in a safe test mode until the school switches them on.

How a message goes out

The school posts a message

An announcement, an automatic alert from another module, or a direct message to one person.

It picks the right channel

An in-app notice, a phone push notification, an SMS, or an email — whichever fits the message.

It sends from the school's own account

SMS and email go out through the school's own provider accounts, so messages carry the school's identity and approved templates.

Every send is logged

Each SMS and email is recorded with its recipient, content, status and cost — so the office can see exactly what was delivered.

Why it matters

Because every SMS and email is logged, the office can see exactly which parents got the fee reminder, and which numbers failed — a real, practical reassurance. And because each school brings its own accounts, messages come from the school's own identity, keeping the school independent and in control of its messaging costs and data.

Honest note on status: SMS and email are wired up; push notifications are delivered today via Expo's push service, with Firebase (FCM) configuration scaffolded for the near future.

On the roadmap: WhatsApp messaging — alerts, fee reminders and payment receipts delivered straight to a parent's WhatsApp. Planned, not built yet.

See Communications on your own data.

A 30-minute walkthrough tailored to your institution. Bring your current admissions process; leave with a clear migration plan.