Loading
Because it is not a smooth curve. Two weeks in September carry a quarter of the year's tickets, mostly the same twenty questions from three different audiences — students, teachers and administrators — who each need a different answer.
Staffing for that peak is unaffordable and staffing under it is a fortnight of misery every year.
The knowledge base and help centre answer the twenty questions, with article suggestions surfacing the right one on the ticket form before it is submitted. Failed-search reports say exactly which articles September proved you were missing.
Routing separates the three audiences on arrival, so a teacher's question does not sit behind three hundred student password resets.
It is not a learning platform and holds no student records. It references the account and does not become a second store of pupil data.
And it will not remove the peak. It changes what fraction of it needs a person.
Business hours and SLA clocks reflect term time rather than a uniform calendar, and reporting compares this September to last rather than to August.
The AI customer agent handles the repetitive tier within guardrails, and hands over anything about a specific pupil to a person.
Yes — students, staff and administrators to different queues on arrival.
Yes, on the form before submission, and failed searches show the gaps.
Yes, business hours are configurable rather than uniform.
Half an hour on your own numbers is usually enough to say whether Desk is the right place to start.