School communication software for Indian schools
Create a circular for a supported school audience and keep recipient action linked to the school record. A linked Parent or signed-in Student can acknowledge the circular.
Current web workflow · Native in-app and push notifications remain subject to launch verification.
One school record
Keep the school source, audience and available action in one record—not scattered across personal messages.
From school desk to recipient
Each stage names the responsible role and available action without implying delivery tracking or private messaging. Open each stage to see what happens and who is responsible.
Start with the message and the people it is for.
Add the title and message, plus an attachment when needed.
The update begins as a school record, not a personal chat.
Choose an audience available to the administrator.
The intended audience remains explicit before publication.
Check the message, audience and optional attachment, then publish.
The circular becomes available in the intended web role experience.
Teachers open relevant circulars. A linked Parent or signed-in Student can acknowledge the circular from its record.
The available action stays with the school update, not a reply thread.
A linked Parent or signed-in Student can acknowledge a circular. Only a Parent acknowledges a Teacher remark when required.
The action remains with the record; it is not a universal read or delivery receipt.
This is a workflow guide—not a working circular composer. No message is created or sent here.
The response matters
Acknowledgement is an explicit action on a record—not proof that every message was delivered or read.
School circular
A linked Parent or signed-in Student can acknowledge a supported circular. Teachers view relevant circulars.
There is no circular-level acknowledgement switch for administrators to configure.
Teacher remark
A Teacher creates a student remark in their assigned context. A Parent can acknowledge it when required.
A Student can read the remark, but cannot complete a Parent-required acknowledgement.
Four roles, distinct responsibilities
Each role receives only its relevant controls. Account and school context determine the available actions.
Authorised administrators create and target circulars to supported audiences.
Explore Schylva for school administratorsTeachers view relevant circulars and can create a student remark in their assigned context. They do not create every circular type.
Explore Schylva for teachersParents open and acknowledge relevant circulars for a linked child. They can also acknowledge a Teacher remark when required.
Explore Schylva for parentsStudents open and acknowledge circulars for their account. They can read, but not acknowledge, a Parent-required remark.
Explore Schylva for studentsThe interface, not a promise of delivery
These are separate sample-school states, not a matched end-to-end transaction. The preparation form is shown above.
Administrator · List state
Shows an All Circulars list with sample test titles, audience labels and month navigation—not detail, delivery or acknowledgement.
Parent · Action available
Shows one supported circular row, its acknowledgement-required state and the available action—not circular detail, a completed acknowledgement or message delivery.
Existing Schylva sample-school interface · identity-free physically cropped derivative.
Know the channel before rollout
Set expectations before asking families to change how they receive school updates.
Prepare a useful walkthrough
Trace its audience, record, acknowledgement and channel boundary. No production account details or school records are needed.
Identify the audience without sharing production account data.
Separate acknowledgement from a universal read or delivery receipt.
Confirm the web scope and excluded channels.
Before your demonstration
Yes. Authorised administrators can target supported audiences. Confirm the school's audience policy during evaluation.
Yes. A linked Parent or signed-in Student can acknowledge the circular. This is not a universal read or delivery receipt.
Teachers create student remarks in their assigned context. A Parent can acknowledge a required remark; a Student can read it but cannot complete that acknowledgement.
No. WhatsApp messaging, email notifications and non-login SMS updates are not product channels. Login verification SMS delivery is not currently available.
No. Native in-app and push notifications are launch requirements. Availability wording follows provider, permission, payload-privacy, deep-link and four-role verification.
No. Custom in-app categories are outside launch scope; users retain device controls. Push delivery is not guaranteed.
Your school’s communication path
Bring one fictional circular, its audience and acknowledgement expectation. We will map the web workflow and mobile-launch boundary.
Share approximate student count and priorities—never production names, messages, files or screenshots. We respond within two working days.