Tasks & tickets
The requests a school runs on — a broken fan, a parent's complaint, a form the principal wants filled — used to live in WhatsApp groups and memory. In Ilmora each one is a task or a ticket with an owner, a priority and a response time, and silence escalates itself.
- Assign a task to a staff member by name with a priority — Urgent, High, Normal — and a response time in minutes, pre-filled from your policy and changeable per task
- Acknowledge, start, complete, with notes and files; unanswered tasks escalate to management level by level
- Recurring and role-based tasks that appear on the right desk without anyone re-creating them
- Complaints, maintenance requests, feedback and admission enquiries all arrive as tickets through one engine
- Intake from the Parent and Student apps, the web, the front desk — or a printed QR code that opens the right form
- Confidential complaints: the reporter's name is stored but shown only to the officer with the right permission
The clock starts at the request, not at the reply
A response-time SLA is judged against each task's own promise — ten minutes for the urgent one, a day for the routine one — and a task nobody acknowledged is escalated on schedule whether or not anyone remembered it. Reports show who answered late, by priority and by department.
Every module writes into the Report Center, and Ask Ilmora can reach these in plain language — under your own permissions.
See Ilmora on your own data
A 30-minute demo with someone who knows the product. We will set up your institute properly afterwards — nobody self-serves their way into a broken configuration.