Support Departments
Administrators create the departments that receive tickets, staff each one with its own operators, and choose which user groups are allowed to write to it. Every request lands with the colleagues who can actually answer it.
Support
SCL Support is your school's own help desk, running inside the system your staff already work in. Administrators create the departments that receive requests, staff each one with members of the school's own team, and decide which user groups may write to them. Parents, teachers and students are granted access the same way, so each audience sees only the departments meant for it.

Administrators create the departments that receive tickets, staff each one with its own operators, and choose which user groups are allowed to write to it. Every request lands with the colleagues who can actually answer it.
Each department adds its own fields to the ticket form, from text, date and number to dropdowns, email and a teachers list, marked required or admin only. Requests arrive complete, so operators stop chasing people for basic details.
Tickets are filed as High, Medium or Low, and administrators can rename these levels or add their own. Operators see urgent work colour coded at the top of the list instead of hunting for it.
Tickets move through Open, Answered, Replied and Closed, and the status updates itself as each side responds. Anyone reading the list can tell what is waiting on the school and what is waiting on the requestor.
The original request and every reply sit in a single conversation in the order they were written, each message showing who sent it and when. Nobody has to reconstruct the story from forwarded emails.
Files can be attached to the opening message and to any reply, within a file count and size limit administrators set in Settings. A parent sends a document once and the operator finds it on the ticket.
SCL Today
When a ticket arrives, every active operator of its department gets a notification naming the ticket number, the department and the subject. Requests are picked up when they land, not when someone next checks the list.
From one Options panel, operators move a ticket to another department, hand it to a named colleague, change its priority or status, or rename an unclear subject. A request sent to the wrong desk reaches the right one without being raised again.
A reply from the person who raised a ticket changes its status but never claims it, so an unassigned request keeps reaching everyone in the department until an operator picks it up. A chaser never disappears into one inbox.
The ticket list opens on the requests you are responsible for, grouped by status with the most urgent first, and filters by number, subject, requestor, department, status, priority and dates. Operators find a request in seconds.
Every SCL page gives staff a Help menu, opened with the question-mark key, with that page's step-by-step guide and, where they exist, a short video, a guided tour and a What changed here tour after an update. Staff answer their own how-to questions before raising a ticket.
Where the school has SCL Connect switched on, staff can ask how to do something and get numbered steps drawn only from SCL's help guides, with the guide and its video linked. Parents and students do not see it.
Every ticket can carry one assignee chosen from that department's operators, and an unassigned ticket is claimed automatically by whoever replies to it first. There is always a name attached to the work.
Operators can mark any message Private, which keeps it between colleagues and hides it from the person who raised the ticket. Staff compare notes on the ticket itself rather than in a separate chat.
Operators can bring other members of staff into a ticket when it needs a second opinion, and a participant can be limited to private replies only. The right people join without the ticket being handed off.
When somebody replies, SCL sends an in-app notification to the people on that ticket, and every user can switch it off from their own notification settings. Nobody keeps refreshing to see whether an answer arrived.
A counter on the Support menu shows the open and replied tickets in your departments that are unassigned or assigned to you. Operators notice a queue building without opening the module.
Requestors see only the tickets they raised, operators see everything in the departments they staff, and access for parents, teachers and students is granted from Users & Groups. Nothing is exposed by accident.
Connected modules
These modules share the same student record, so what happens in one shows in the others.
Private messages, class discussions, newsletters to any audience and classroom moments, for staff, parents and students, with read receipts and recall.
One app for grades, attendance, fees, messages, behaviour and medical details, across every child a family has at your school. Web and mobile.
Every student gets their assignments, gradebook, timetable, report card and virtual classrooms in one login, on the web and on their phone.
Every screen and every action governed by permissions you grant per role, down to whether a user may access, create, edit or delete. Not a fixed set of roles.
Training at your school and online, a Help menu on every page with the page's guide, guided tours and videos on many pages, Ask the Help Center, phone support and Priority Support where your license includes it.