Skip to content
All modules Communication & Family Engagement

Announcements software for Indian schools

School-wide broadcasts

Feature identity

Announcements

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

Example view

Announcements in a school workflow

School-wide broadcasts

Communication & Family Engagement
Announcements in a school workflow
Communication & Family Engagement
  1. 01
    Required context

    Eligible audience records and at least one configured delivery channel must be confirmed before rollout.

  2. 02
    Supported work

    Audience tokens including class/section targeting, deduped per family.

  3. 03
    Reviewable result

    A scheduled or immediate broadcast with an explicit audience preview, deduplication and per-channel delivery evidence.

Example record

Announcements

Authorised view
  • Audience tokens including class/section targeting, deduped per family
  • A live recipient-count preview with masked contact samples
  • Schedule for later — the worker publishes and fans out on time
  • Announcement-360: delivery rate, read rate, per-channel statistics
A scheduled or immediate broadcast with an explicit audience preview, deduplication and per-channel delivery evidence.
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

Publish an announcement to selected audiences such as parents, students, staff, teachers or one class-section, then choose from the channels configured for the school. A dry-run estimates eligible recipients and identity deduplication reduces repeated sends. Actual delivery remains asynchronous and depends on provider, consent and channel policy.

The school problem

School teams need a dependable way to handle Announcements: School-wide broadcasts. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

School-wide broadcasts.

  1. Audience tokens including class/section targeting, deduped per family
  2. A live recipient-count preview with masked contact samples
  3. Schedule for later — the worker publishes and fans out on time
  4. Announcement-360: delivery rate, read rate, per-channel statistics

Operational result

What your school gets

A scheduled or immediate broadcast with an explicit audience preview, deduplication and per-channel delivery evidence.

Access and ownership

Who typically uses it

  • Communication administrator
  • School administrator
  • Principal
  • Teacher

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

  • Eligible audience records and at least one configured delivery channel
  • Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Flagship workflow deep dive

Announcements & Multi-Channel Family Broadcasts

One circular. Every channel. Honest delivery evidence.

Compose one announcement and reach families across WhatsApp, SMS, email and the in-app portals in a single pass — with a live recipient count before sending, school-approved WhatsApp templates, recorded opt-outs, and a unified delivery log that reports only what each channel's provider actually returns.

Interactive operating model

One circular's honest journey

Each stage shows the control that gates the broadcast and the evidence the school can point to afterwards.

Illustrative workflow · no customer data

Stage 1 of 5

Composed

Authorised staff write the circular and choose audience tokens and channels.

Control point

Only staff with communication rights compose; the audience is a defined token set, not a pasted number list.

Evidence retained

The draft, its audience definition and author.

Core workflows and features

The operational work behind the promise

  1. Audience-token broadcast builderAddress parents, students, staff, teachers or one class-section with audience tokens, deduplicated so nobody is messaged twice for one circular.
  2. Live recipient previewA dry-run resolves the real recipient count before sending, so an empty class token or missing numbers surface while it is still a draft.
  3. Multi-channel fanoutOne publish fans out across the selected channels — WhatsApp, SMS, email and in-app — instead of four separate sending tools.
  4. Approved-template WhatsAppBusiness-initiated WhatsApp goes out as the school-approved template you configure. Without one, WhatsApp itself only delivers free text inside its 24-hour service window.
  5. Scheduled publishingSchedule an announcement and the worker sends it at the chosen time with the same template and audience resolution as an immediate send.
  6. Unified delivery logEmail and messaging outcomes land in one delivery view, so a circular's evidence is reviewed in one place rather than per provider.
  7. Per-channel evidence honestyReview the evidence each configured channel actually returns — recorded in-app state, WhatsApp delivery or read where available, SMS acceptance only.
  8. Opt-outs recorded and honouredInbound STOP and START messages update the recipient's preference, and opted-out numbers are skipped on the next broadcast automatically.
  9. Onboarding quiet modeA new workspace holds non-essential outbound communication until the school explicitly goes live, so setup experiments never reach families.
  10. In-app noticeboard and detail pagesAnnouncements appear in the parent and student portals with their own detail view, independent of any external channel's delivery.

Drafting help, human sending

Aira can draft the words. A person always presses send.

Where the plan includes it, Aira drafts announcement and campaign copy on request through the governed AI path. The broadcast itself — audience, channels, timing — remains a deliberate human action with the recipient count on screen.

  • Draft announcement or campaign copy on request through the governed Aira path where the plan includes it.
  • Show the honest resolved recipient count before anything can be sent.
  • Route WhatsApp through the school-approved template you configure, so a business-initiated broadcast goes out as that template.
  • Record per-channel outcomes into the unified delivery log for staff review.

Human boundary

Aira never sends a broadcast. A person composes or accepts the copy, sees the recipient count, and presses send; channel evidence differs by provider — SMS never claims read evidence, and email opens appear only when the configured provider supplies them.

Key daily uses

What the school team does here

  1. Publish a school-wide circular across WhatsApp, email and the portals in one pass.
  2. Target one class-section about tomorrow's schedule change.
  3. Schedule the exam-week notice for Monday morning.
  4. Review which channel actually accepted, delivered or recorded each message.
  5. Check that opted-out families were skipped, with the preference on record.

Used by

  • Principal
  • Vice principal
  • Front-office executive
  • Class teacher
  • Tenant administrator
  • Parents and students (recipients)

Actual access follows the school's plan, role permissions and record scope.

Measurable operating indicators

Metrics to track — not guaranteed ROI

Establish a baseline before rollout, agree the reporting period, then compare the school's own source evidence.

Reach before send

Resolved recipients in the dry-run preview ÷ intended audience size

Catches an empty class token or missing contact numbers while the circular is still a draft.

Channel acceptance

Provider-accepted sends ÷ attempted sends, per channel

Provider acceptance is not inbox delivery — treat it as the channel's own evidence, reviewed per provider.

Opt-out rate

Opt-outs recorded ÷ recipients messaged over the period

A rising rate is a content-and-cadence signal the school should act on, not a metric to suppress.

Prerequisites and availability

Confirm the operating context before rollout.

Core communication capability · WhatsApp, SMS and email run on the school's configured providers and approved templates

  • WhatsApp and SMS require provider onboarding and school-approved templates; template and registration approvals are channel-specific steps.
  • Email runs on SendGrid or the school's own SMTP configuration.
  • Guardian contact data and consent records must be current — the school owns both.
  • A new workspace holds non-essential outbound communication until the school's explicit go-live.

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.

Why does WhatsApp need an approved template?

Because the channel requires it: business-initiated WhatsApp outside the service window must use a pre-approved template, so Vidyapeeth360 refuses to send a broadcast as free text. Provider onboarding and template approval remain channel-specific steps for your school.

How do we know who actually received an announcement?

You review the evidence each configured channel actually returns. In-app can show recorded state, WhatsApp may return delivered or read, SMS carries no read evidence, and email opens appear only when the configured provider supplies them.

Does Announcements work on its own?

SMS Alerts, WhatsApp Alerts, Email Notifications, Push Notifications 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 Announcements?

Eligible audience records and at least one configured delivery channel. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Is AI used in Announcements?

No AI capability is asserted for Announcements. 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

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

See it in your school context

Run announcements the connected way.

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

You control analytics.

Necessary storage keeps sign-in and saved preferences working. Optional analytics and session replay stay off until you allow them, and our event contract excludes names, contact details and student records. Cookie Policy