Product
Administrators work in a browser workspace. Parents and staff take everyday actions through the school’s WhatsApp identity. One record, two surfaces.
Book a Live DemoSchool management console · illustrative
Students
Roster
On your campus
Attendance
Today
Marked classes
Fees
Ledger
This term
WhatsApp workflows
Connected to school WhatsApp conversations
| Queue | Status | Owner |
|---|---|---|
| Fee follow-up · Class 9 | Waiting on parent | Accounts |
| Admission documents | Review | Office |
| Bus 12 departure | Live trip | Transport |
Walk a fee, attendance, transport or gate journey. Demonstration copy only.
School WhatsApp
Parent experience
Demonstration conversation
School office
Office queue: fee enquiry opened.
The ledger and receipt sit on the same student record the office already manages.
Problem. Enquiries, applications and enrolled profiles live in different files.
Workflow. Capture the enquiry, complete the application, then open the student record the rest of the school will use.
Administrators. Administrators manage pipelines, documents and section assignment from the workspace.
WhatsApp. Prospective parents message or call the school number about admission. The office answers and keeps notes.
Problem. Attendance, homework, timetable and exams are tracked in separate tools.
Workflow. Teachers mark the roll and share work; the office publishes exams and results from the same class record.
Administrators. Timetable, grades and examination setup stay in the administration console.
WhatsApp. Parents see attendance and result notices in the school thread.
Problem. Fee schedules, collections and receipts do not match the student ledger.
Workflow. A parent checks the balance, pays, and receives a receipt while accounts sees the same entry.
Administrators. Fee structures, exceptions, reconciliation and audit sit with finance roles.
WhatsApp. Outstanding dues and payment confirmation happen in WhatsApp.
Problem. Staff files, leave and payslips are emailed around.
Workflow. HR keeps records; staff complete attendance and leave in their role conversation or web tools the school enables.
Administrators. Permissions decide who can view payroll and staff documents.
WhatsApp. Payslip and leave notices can be delivered on the school number where enabled.
Problem. Routes, live trips and parent alerts are run from a driver’s personal chat.
Workflow. The office defines routes; the driver runs the trip; parents get stop alerts.
Administrators. Buses, routes and trip logs remain in the transport module.
WhatsApp. Drivers and parents use transport conversations on the school number.
Problem. Gate passes and pickup authorisation are paper or personal WhatsApp.
Workflow. Security matches the pass; the office keeps the campus log.
Administrators. Visitor and pickup rules are configured centrally.
WhatsApp. Scan results appear in the security conversation.
Problem. Rooms, wardens and out-passes are tracked separately from the student file.
Workflow. Wardens manage rooms and out-passes against the boarding student record.
Administrators. Hostel occupancy and warden permissions live in the workspace.
WhatsApp. Out-pass requests and hostel notices go through the warden conversation.
Problem. Staff share personal numbers with parents, and enquiry calls are lost on someone’s phone.
Workflow. Current parents and new admission enquiries reach the message center and call center on the school number. The office answers, keeps notes and follows up.
Administrators. Only the admin can see phone numbers. Teachers, drivers, wardens and security never see a parent’s number, and parents never see theirs.
WhatsApp. Everyone talks through the school’s WhatsApp number.
Problem. Reporting, audit history and permissions are afterthoughts.
Workflow. Role permissions, reports and audit logs are part of the same platform.
Administrators. School leadership sees operations without a second system of record.
WhatsApp. WhatsApp remains the access layer—not a parallel database.
