Reach.

A notice no one reads might as well never have been sent.

• WhatsApp templates

  Send approved WhatsApp Business templates with a header (text, image, video or PDF), a body and call-to-action or URL buttons — the format Meta requires to reach a parent's phone.

• Variable mapping

  Map each template placeholder — {{student}}, {{class}}, an amount — to a real student or parent field with a fallback value, so one template personalises across the whole audience without a mail-merge spreadsheet.

• Audience scoping

  Pick who hears it: an entire class, named sections, individual students, teachers or employees — and choose whether students are reached via the parent or the student contact.

• Channels & in-app

  When WhatsApp is not the right fit, the same audience can get an in-app notification that lands in the mobile inbox, or an email sent from the school's connected mailbox.

• Delivery receipts

  Meta's webhooks flow straight back in: every recipient moves through Sent → Delivered → Read or Failed, with timestamps and the failure reason kept against the name — not a black box after you hit send.

• History & logs

  Every campaign is kept with a full per-recipient delivery log — searchable, exportable, and resolved against the message each parent actually received.

• Phone-number management

  Register more than one WhatsApp sending number, set a default and per-branch access, give each a daily send limit with a counter — and let the platform route around a number that has hit its cap.

• Templates with analytics

  Build and version templates by category — Utility, Authentication or Marketing — in the language parents read, then watch sent, delivered, read and button-click numbers per template over time.

• 01 / 04

  Scoped by branch and session, like the rest of the platform. An audience is resolved from this year's class and section records — so a broadcast to VII-A reaches the children who are in VII-A now, never last year's roll, and a multi-campus trust keeps each campus's sends its own.

• 02 / 04

  Drawn from the one ledger every other module writes to. Recipients, parent contacts and class lists are the same records admissions, fees and attendance already maintain — so there is no separate contact book to keep in sync, and a number fixed once is fixed everywhere.

• 03 / 04

  On the same web, iOS and Android apps. A coordinator queues a broadcast from the desk; the in-app channel lands in the very mobile inbox parents already open for fees and homework. No second app for messaging.

• 04 / 04

  Within reach of Sol, the AI agent. The same assistant that works across the school sits over communications too — a quiet way to ask who didn't receive the last notice, not a fourth tool to learn.

Why it has to be this

Anyone can send a message. The hard part is knowing it arrived.