Skip to main content
Schylva
Login helpRequest a demo

School communication software for Indian schools

School updates that keep the audience and action together.

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.

Book a communication workflow demo Get a custom quote

This is the current Schylva web workflow. Native in-app and push notifications are coming at launch. WhatsApp, email and non-login SMS are not product channels.

Administrator circular formStatic preview

Visible evidencePre-submit circular and audience controls

Identity-free crop of Schylva administrator circular controls showing title, message, supported audiences and optional attachment before submission
Existing Schylva sample-school interface · identity-free physically cropped derivative.Review pre-submit circular controls.

Shows empty title and message fields, audience choices and the optional attachment area before submission.

Static preview · expanded detail unavailable
  1. School preparesAudience-specific circular
  2. Recipient opensThe underlying update record
  3. Action stays linkedExplicit acknowledgement

One accountable communication path

Keep every update tied to its audience and action.

Keep the school source, audience and available action in one record—not scattered across personal messages.

  1. School source

    Prepare the circular at school.

    An authorised administrator creates the update for the appropriate audience.

  2. Audience and record

    Keep audience and record together.

    The selected audience and optional attachment remain with the circular.

  3. Role-specific action

    Use the available role action.

    Teachers view relevant circulars; linked Parents and signed-in Students can acknowledge them. Only a Parent acknowledges a Teacher remark when required.

Communication-routing loop

Trace one update from preparation to acknowledgement.

Each stage names the responsible role and available action without implying delivery tracking or private messaging.

School communication stages

Choose a stage to review its web action and boundary.

5 stages · Swipe or scroll to explore

Authorised administrator

Create the circular record.

Current action
Add the title and message, plus an attachment when needed.
Connected outcome
The update begins as a school record, not a personal chat.
Audience context

Choose the circular audience.

Current action
Choose an audience available to the administrator.
Connected outcome
The intended audience remains explicit before publication.
Current web workflow

Publish through the intended role path.

Current action
Check the message, audience and optional attachment, then publish.
Connected outcome
The circular becomes available in the intended web role experience.
Teacher, Parent or Student

Open the underlying record.

Current action
Teachers open relevant circulars. A linked Parent or signed-in Student can acknowledge the circular from its record.
Connected outcome
The available action stays with the school update, not a reply thread.
Parent or Student

Acknowledge the circular where supported.

Current action
A linked Parent or signed-in Student can acknowledge a circular. Only a Parent acknowledges a Teacher remark when required.
Connected outcome
The action remains with the record; it is not a universal read or delivery receipt.

Role-specific responsibility

Keep communication responsibilities distinct.

Each role receives only its relevant controls.

Teachers

View circulars and add remarks.

Teachers view relevant circulars and can create a student remark in their assigned context. They do not create every circular type.

Explore Schylva for teachers
Parents

Open and acknowledge linked-child updates.

Parents open and acknowledge relevant circulars for a linked child. They can also acknowledge a Teacher remark when required.

Explore Schylva for parents
Students

Open circulars and remarks.

Students open and acknowledge circulars for their account. They can read, but not acknowledge, a Parent-required remark.

Explore Schylva for students

Identity-free interface evidence

Read each image only for its visible state.

These derivatives show pre-submit controls and administrator and Parent list states—not delivery, detail, acknowledgement actions or mobile notifications.

Primary screen shown aboveReview pre-submit circular controls.Return to the administrator circular form in the hero.
Administrator circular listStatic preview

Visible evidenceAdministrator circular list and audience labels

Identity-free crop of Schylva administrator All Circulars list showing sample audience labels and month navigation
Existing Schylva sample-school interface · identity-free physically cropped derivative.Administrator circular list

Review the administrator list state.

Shows an All Circulars list with sample test titles, audience labels and month navigation—not detail, delivery or acknowledgement.

Static preview · expanded detail unavailable
Parent circular listOpen detail

Visible evidenceParent circular row and acknowledgement-required state

Focused Schylva Parent circular row showing an acknowledgement-required school update using sample school dataOpen privacy-safe detail
Existing Schylva sample-school interface · identity-free physically cropped derivative.Parent circular list

Review the Parent list state.

Shows one supported circular row, its acknowledgement-required state and the available action—not circular detail, a completed acknowledgement or message delivery.

Privacy-safe focused crop · surrounding controls intentionally excluded

Current communication scope

Separate web actions from mobile launch scope.

Confirm audience and policy within this scope.

Supported today on web

  • Administrator circulars for supported school audiences
  • Circular attachments and role-specific views
  • Explicit Parent or Student circular acknowledgement
  • Teacher circular views and student remarks in the assigned context
  • Parent acknowledgement of a required Teacher remark; Students can read it but cannot acknowledge it

Confirm for your school

  • The audience policy for each circular type
  • How Parents and Students should use circular acknowledgement
  • Attachment type, size and count requirements
  • Teacher remark contexts and circular ownership responsibilities
  • Native notification rollout after provider, privacy, permission and deep-link verification

Current and launch boundaries

  • No WhatsApp or private chat, email delivery or tracking, or non-login SMS; login verification SMS delivery is not currently available
  • No universal read receipt, guaranteed delivery or acknowledgement for every update
  • Teachers do not create every circular type
  • Native in-app and push availability requires release verification
  • No custom notification categories at launch; device controls remain separate

Prepare a communication walkthrough

Bring one fictional circular.

Trace its audience, record, acknowledgement and channel boundary.

Confirm in the walkthrough

Who should receive the circular?

Identify the audience without sharing production account data.

Confirm in the walkthrough

How should acknowledgement be used?

Separate acknowledgement from a universal read or delivery receipt.

Confirm in the walkthrough

Which channels does the school expect?

Confirm the web scope and excluded channels.

School communication questions

Questions to settle before the workflow demonstration.

Confirm the audience, action and channel requirement.

Can schools target a circular to a particular audience?

Yes. Authorised administrators can target supported audiences. Confirm the school's audience policy during evaluation.

Can Parents and Students acknowledge a circular?

Yes. A linked Parent or signed-in Student can acknowledge the circular. This is not a universal read or delivery receipt.

How do Teacher remarks work?

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.

Does Schylva support WhatsApp, email or SMS school updates?

No. WhatsApp messaging, email notifications and non-login SMS updates are not product channels. Login verification SMS delivery is not currently available.

Are in-app and push notifications available now?

No. Native in-app and push notifications are launch requirements. Availability wording follows provider, permission, payload-privacy, deep-link and four-role verification.

Can users customise notification categories, and is push delivery guaranteed?

No. Custom in-app categories are outside launch scope; users retain device controls. Push delivery is not guaranteed.

Communication-focused next step

Trace one circular from school source to explicit acknowledgement.

Bring one fictional circular, its audience and acknowledgement expectation. We will map the web workflow and mobile-launch boundary.

Book a communication workflow demo Get a custom quote

Share approximate student count and priorities—never production names, messages, files or screenshots. We respond within two working days.