Skip to content
All modules Communication & Family EngagementDedicated Aira capability

Parent Aira governed AI for Indian schools

Answers a parent about their own child — from live data, never another family's.

Feature identity

Parent Aira

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

Example view

Parent Aira in a school workflow

Answers a parent about their own child — from live data, never another family's.

Communication & Family Engagement
Dedicated Aira capability

Parent Aira

Answers a parent about their own child — from live data, never another family's.

ScopeOnly supported, permission-checked school context
  1. Required contextA plan that includes Aira, plus linked parent-child identity and a school-enabled channel/credit budget must be confirmed before rollout.
  2. Supported workFees, attendance, published marks & the bus — from live data.
  3. Reviewable resultOwn-child-only answers for a guardian across supported fees, attendance, published marks and transport data.
Governed resultOwn-child-only answers for a guardian across supported fees, attendance, published marks and transport data.
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

Answers are scoped to the authenticated parent's own children — Aira's tools can only look up student IDs linked to that account. The default router pattern-redacts common identifiers, and known names can be tokenized when the calling flow supplies them. Supported channels include the web portal, the early-access app and an opt-in WhatsApp auto-reply when configured.

The school problem

School teams need a dependable way to handle Parent Aira: Answers a parent about their own child — from live data, never another family's. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Answers a parent about their own child — from live data, never another family's.

  1. Fees, attendance, published marks & the bus — from live data
  2. Web portal + early-access mobile app + configured WhatsApp
  3. Role-scoped tools plus configured identifier safeguards
  4. School-controlled: on/off toggle + a protected credit budget

Operational result

What your school gets

Own-child-only answers for a guardian across supported fees, attendance, published marks and transport data.

Access and ownership

Who typically uses it

  • Parent or guardian
  • School administrator

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

Included from Premium

Permission-scoped Aira questions and supported actions that require human confirmation.

  • A plan that includes Aira, plus linked parent-child identity and a school-enabled channel/credit budget
  • Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Flagship workflow deep dive

Parent Communications & Own-Child Aira

The right message. The right family. The right scope.

Plan school communication through configured WhatsApp, SMS, email, in-app and early-access push channels. Parent Aira is a separate read-only experience that answers supported questions about the authenticated family's own children through enabled web, early-access mobile, voice and opt-in WhatsApp paths.

Interactive operating model

The family-scope communication path

Switch stages to see the difference between an outbound school message and a read-only parent question.

Illustrative workflow · no customer data

Stage 1 of 6

Audience preview

Authorised staff select the school audience and inspect eligible recipient evidence.

Control point

Masked samples, deduplication, consent and role scope are visible before publish.

Evidence retained

Selected audience, recipient count and exclusion reasons.

Core workflows and features

The operational work behind the promise

  1. Scoped audience selectionChoose an authorised stakeholder, class or section audience and preview the eligible recipient count before publish.
  2. Masked recipient previewReview representative masked contact evidence without exposing a full family contact list in the composer.
  3. Overlapping-audience deduplicationResolve overlapping audience tokens to one recipient identity per student or staff record so the same selected identity is not fanned out twice.
  4. Configured channel templatesUse Meta-approved WhatsApp and DLT-registered SMS templates with the school's provider credentials.
  5. Email and in-app deliveryRoute email through the configured sender and publish supported notices to the signed-in portal experience.
  6. Early-access pushUse supported push notifications and deep links only inside the enabled early-access app programme.
  7. Schedule and expiryChoose a future publication time and an expiry while keeping the authored message available for staff review.
  8. Consent and quiet-mode controlsApply channel consent, opt-out, provider and onboarding quiet-mode checks before an eligible send.
  9. Provider-reported evidenceReview attempted, sent, delivered, read or failed states only where the configured provider returns them.
  10. Own-child AiraAnswer supported questions about the signed-in guardian's linked children across fees, attendance, published marks and transport data.

Aira with a family boundary

Draft for staff. Read for parents. Never widen the child scope.

Aira can prepare communication copy for an authorised staff member to review. Parent Aira separately uses read-only, permission-checked tools that resolve only student IDs linked to the authenticated guardian.

  • Draft a school notice or reminder for staff editing before the communication publish path.
  • Answer supported own-child fee, attendance, published-mark and transport questions from authorised current records.
  • Use the same child linkage on web, early-access mobile, configured voice and opt-in WhatsApp access paths.
  • Check that the plan includes the Aira AI assistant, then apply the governance precheck, configured identifier safeguards and credit budget before an AI request.
  • Refuse child-data answers for an unknown WhatsApp sender until the required identity and opt-in relationship is established.

Human boundary

Parent Aira is read-only and cannot update a school record, send a school broadcast or access another family's child. Staff review generated outbound copy; provider acceptance does not prove delivery or reading.

Key daily uses

What the school team does here

  1. Preview and schedule a class or whole-school circular.
  2. Draft a multilingual notice for authorised staff review.
  3. Review failed or ambiguous provider evidence before choosing whether to retry.
  4. Let a verified guardian ask about their own child's fees, attendance or published result.
  5. Review reachability, opt-outs and quiet-mode skips before a campaign.

Used by

  • Communications operator
  • Principal
  • Vice principal
  • Admission manager
  • Tenant administrator
  • Teacher in an authorised communication scope
  • Parent or guardian

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.

Reachability

Eligible recipients with a valid, consented configured channel

Separates audience size from the families a provider can actually attempt to reach.

Provider-reported delivery

Attempted, sent, delivered, read and failed states by channel

Uses each provider's returned evidence and avoids treating acceptance as guaranteed reading.

Governance disposition

Opted-out, quiet-mode-skipped, failed and manual-review message states

Makes policy and delivery exceptions visible instead of hiding them inside a single delivery percentage.

Prerequisites and availability

Confirm the operating context before rollout.

Aira AI assistant on a plan that includes it · configured channels · native apps in early access

  • Parent access requires an authenticated guardian account linked only to that family's student records.
  • WhatsApp and SMS require school-owned provider credentials, approved templates, consent and applicable Meta or DLT rules.
  • Email requires configured delivery; provider acceptance does not guarantee inbox placement.
  • Native mobile and push remain early access ahead of public app-store release.
  • Voice and opt-in WhatsApp Aira require their configured providers, identity path, assistant credits and channel enablement.

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.

Can a parent ask about another family's child?

No. Every parent tool resolves a child strictly within the children linked to that authenticated parent account. There is no path from the parent surface to another family's records, and no school-wide question a parent can ask.

Will parents get AI replies on WhatsApp automatically?

Only if the school switches it on — it is off by default. When enabled, replies go only to a registered, opted-in parent account, and business-initiated messages still follow the channel's approved-template rules.

Does Parent Aira work on its own?

Parent App, Voice Aira, Attendance Alerts, Online Payment 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 Parent Aira?

A plan that includes Aira, plus linked parent-child identity and a school-enabled channel/credit budget. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Is AI used in Parent Aira?

Dedicated Aira capability. Aira supports only the reviewed actions listed on this page, and authorised people remain responsible for confirming material actions.

How do we confirm the plan and implementation scope?

Parent Aira is included from Premium in the current public plan matrix. Final rollout scope, services and external dependencies are confirmed in your written proposal.

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

See it in your school context

Run parent aira 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