Help Desk Software for Schools: SSO, Three Audiences and September

School help desks are unusual, and most comparison articles treat them as small businesses. They are not. Your ticket volume is wildly seasonal, your users cannot be trained the way employees can, and a meaningful share of them are children. Here is what that means for the purchase.

Three audiences, not one queue

This is the requirement most schools discover after they have bought something. A school help desk serves at least three groups and they need different treatment.

The Asyntai column is ours. It is strongest on the parent row, which is high volume, out of hours and almost entirely answerable from your school website. Anything safeguarding-related routes straight to a named member of staff, which is the behaviour a school needs and one you configure rather than hope for.

Notice the last row. Parent questions arrive in the evening and at weekends, when your IT and office staff are not working. A help desk that only operates in school hours leaves that queue to pile up overnight, and most of those questions have published answers on your own website.

The September problem

School IT volume is not flat. It collapses in the holidays and spikes hard at the start of the year, when every new device, account and login problem arrives in the same fortnight.

This is the strongest practical argument in a school for something other than straight per-agent pricing. Three ways to handle it:

• Day passes. Freshdesk sells temporary agent access at $2 to $12 per person per day. Bringing in extra hands for the September fortnight costs a fraction of carrying seats all year.
• Free tiers with light roles. Zoho Desk has a free edition with three user licences and light agent seats on higher tiers. Jira Service Management is free up to 3 agents, which suits a small internal IT desk.
• Deflect the spike. Most September tickets are the same handful of questions: how do I log in, how do I connect to the network, where is my timetable. Those have written answers, and answering them automatically flattens the peak rather than staffing it.

What the software costs

We make Asyntai, so read that row as a disclosure. It sits in front of your ticketing system and answers the questions that would otherwise open a ticket. Sector-specific education platforms exist, including asset-led products aimed at K-12 districts, and most of them price by quote rather than publishing a figure.

Helpdesk or help desk? Both, and it matters for your search

You will see this written as helpdesk, help desk and service desk, and vendors use all three inconsistently. There is no real difference in what they sell, but there is one distinction worth knowing when you compare products:

• A helpdesk is usually described as reactive. Somebody has a problem, a ticket is raised, it gets fixed. Most school IT desks are this.
• A service desk is the broader term, adding change management, asset registers, service catalogues and approvals. Schools reach for this when IT also runs procurement, device rollouts and access requests.

If your team handles the annual device refresh, tracks which pupil has which Chromebook, and approves software requests, you want service desk capabilities even if you search for helpdesk software. That distinction moves you toward asset-aware platforms and away from simple ticket inboxes, and it is worth settling before the shortlist.

K-12 and universities are different purchases

If you are a single school, be careful about advice written for universities. A platform sized for twelve departments and thirty agents will cost you money and configuration time you do not have, and the free tiers listed earlier will serve you better for at least a year.

The self-service question

Self-service is the standard recommendation for school helpdesks, and it half works. Worth being precise about why.

A knowledge base helps staff, who will search it, and helps almost nobody else. Students do not read documentation, and parents do not know your site structure well enough to find the page about absence reporting. Publishing the article is necessary and it is not sufficient.

What changes the numbers is not the article existing, it is the answer arriving when the question is asked, in the words the person used. "My kid is off sick, who do I tell" needs to reach the absence procedure without the parent knowing that page is called Attendance Policy.

That is the gap between a knowledge base and an answering system, and in a school it is the difference between a page nobody reads and an evening queue that never forms.

Education discounts, honestly

They are real and they are modest. Published education and non-profit discounts in this market sit around 10% to 15%, sometimes with an extended trial for qualifying institutions. Freshworks runs an education programme with a notably long free trial period, which is worth asking about directly.

The practical advice: choose the right tool on requirements, then ask for the education rate at the end. Do not let a 15% discount pull you toward a platform that does not do single sign-on with your identity provider, because that decision costs you every day for years.

A 15% discount on the wrong platform is not a saving.

The requirement that outranks price

Single sign-on. Schools run identity through a small number of systems, and if your help desk does not connect to yours, every student ticket starts with a password problem, which is the thing you were trying to reduce.

Ask specifically, and get the answer in writing:

• Which identity providers are supported? Name yours. Google Workspace for Education and Microsoft Entra are the common ones, with ClassLink and similar in some districts.
• Which tier includes single sign-on? This is frequently a higher-tier feature, which changes your real price more than any discount.
• Does it sync groups? Being able to route a ticket by year group, department or site saves an enormous amount of manual triage.
• What happens to accounts at the end of the year? Students leave in cohorts. Ask how deprovisioning works before your first July.

Safeguarding and data protection

This is where a school purchase differs most from a business one, and it deserves care rather than a checklist.

If students can raise tickets or chat, the system will occasionally receive a message that is not an IT problem. Any tool you choose needs a clear, fast route to a human, and your staff need to know what that route is. Automated systems in particular must be configured to hand over rather than attempt to help, and this should be tested before launch, not assumed.

On data, ask three questions and get written answers: where is the data stored, how long is it retained, and is any of it used to train the vendor's models. Your data protection officer will need all three, and asking early is much easier than asking during a procurement review.

We are not lawyers and this is not legal advice. It is the list of questions that tends to come up, so that it comes up early.

Rolling it out without losing the staff

The technical setup is the easy part. Getting teachers to raise a ticket instead of stopping you in the corridor is the actual project, and it fails more often than the software does.

Four things that decide whether it sticks:

• Make raising a ticket faster than finding you. A form with eleven required fields loses to a corridor conversation every time. Three fields and a submit button competes.
• Accept email as an entry point. Staff will email the address they have always emailed. Point it at the helpdesk so those become tickets automatically, rather than trying to retrain sixty people.
• Close the loop visibly. The single biggest complaint about school IT desks is silence. An automatic acknowledgement and a note when it is fixed does more for perception than a faster fix time.
• Do not launch in September. Launch in the summer term or the January term, when volume is normal and you have room to fix what breaks. Launching into the busiest fortnight of the year is a common and avoidable mistake.

What to measure in the first term

Three numbers, reviewed once at half term, are enough:

That third figure is the one worth watching over years. In most schools it is high, because the same login, network and access questions repeat every term with every new cohort. Each one you answer automatically is a ticket that never reaches a two-person IT team in the first week of September.

Five questions to ask a vendor

1. Which tier includes single sign-on with our identity provider? Name it. This changes the price more than the discount does.
2. How do we handle the September surge? Ask specifically about temporary seats, light agents or day passes rather than annual licences.
3. Can students, staff and parents have different request forms and routing? One queue for three audiences becomes unmanageable quickly.
4. What is the education or non-profit rate, and what qualifies? Ask at the end, once the shortlist is decided on requirements.
5. Where is data held, how long, and is it used for model training? Get all three in writing for your data protection records.

What to do next

• Sample last year's tickets. Mark each: staff, student or parent, and whether the answer is already published somewhere. Those two splits decide your whole shortlist.
• Start on a free tier. Zoho Desk's free edition, Jira Service Management free for three agents, or Help Scout's free tier will run a small internal desk while you learn what you need.
• Solve the parent queue separately. It is out of hours, high volume and almost entirely documented. Staffing it is the expensive answer.
• Plan for September in June. Whatever you choose, know before the summer how you will handle the first fortnight, and price that specific fortnight rather than the average month.