Your help desk was built for a company. You run a district.

Students find the librarian. Parents call the front office. Teachers guess which queue a broken window goes in. The tool works because your people make it work, and none of that shows up in a report.

Five questions. Nothing to fill in. Nobody sees your answers but you.

A teacher with a coffee mug explains a problem to a district help desk technician at her laptop while a staff member waits with a broken projector
Monday 7:42 AM
This morning's requests···
How do I get into my Chromebook?AnsweredAI
Broken window in Room 4RoutedFacilities
Projector in Room 12 is deadOpenIT
Only the projector reached your queue.
Our design partners
Olympia School District logoOlympia School District
Lower Moreland Township School District logoLower Moreland Township SD
Ladue School District logoLadue School District
Massac Unit School District #1 logoMassac Unit SD #1
Olympia School District
Lower Moreland Township SD
Ladue School District
Massac Unit SD #1
1 in 3
edtech leaders say their district is understaffed for tech support.
CoSN State of EdTech, 2026
Silos
between departments are the second biggest barrier to getting things done. Only budget ranks higher.
CoSN State of EdTech, 2026
6
technology staff lost over six years. The schools still expect the same service.
Olympia School District, WA
The pattern

Business help desks assume everyone has a login.

Half the people who ask your district for help never will. So their questions find a person instead, and that work never becomes a ticket.

Asked at the library desk0 tickets···
JSMy Chromebook won't let me log in
AMWhere do I print my essay?
KLCan you reset my password?
RDThe wifi isn't working again
01

The librarian is your help desk

Students don't file tickets. They find the nearest adult who knows. That work is real, and it never shows up in a report.

Broken window in Room 43 days lost
TS
Filed by a teacher in ITMon 8:12 AM
JM
Still waiting in ITWed 1:30 PM
AK
Reassigned to FacilitiesThu 9:05 AM
02

The wrong queue

People guess which team owns a request. The window got fixed. The guessing didn't, and your team inherits the cleanup.

Back to school callsnot IT's···
When does my first paycheck post?Payroll
Where do I update my W4?HR
I can't see my class rosterSIS
Projector won't turn onIT
03

Calls that aren't yours

At Olympia School District, 20 to 25 percent of back to school calls belonged to payroll, HR, or the student information system.

What changes

Answer the routine. Route the rest.

A front door built for a district answers people who will never log in and sends real issues to the right team the first time.

Answer

Questions get answered first

Students, families, and staff get answers from your own district content, at any hour, without a login.

Route

The right team, first time

Requests reach IT, Facilities, HR, or the front office with context. Nobody has to guess the queue.

Keep

Your help desk stays

schoolAgent works in front of the help desk you already run. Nothing gets replaced and nobody retrains.

From a peer

Fewer staff, the same expectations

Marc Elliott's technology team at Olympia School District lost six people in six years. His schools still expect the same service. Here he talks about where he looked first.

Read Marc's post

schoolOS is the first platform I've seen that actually addresses how operations work in practice.

ME
Marc ElliottCIO, Olympia School District, WA
Read his story
Olympia School District
18,385
tickets reviewed
42%
could be handled by knowledge or automation

"schoolOS is the first platform I've seen that actually addresses how operations work in practice."

MEMarc Elliott
CIO, Olympia School District, WA
Why it is different

Built for the people who ask a district for help.

A business help desk organizes the queue. Your district needs fewer things in it.

The question
A business help desk
schoolOS
Who is it built for?
Employees with an account and a portal.
Students, families, and staff, logged in or not.
Where do parent questions go?
To a phone, an inbox, or the front office.
Answered at the front door from your district content.
Who routes the request?
The requester guesses a queue. Someone reassigns it.
It reaches the right team the first time, with context.
Who writes the knowledge base?
Your team writes and maintains articles.
It builds itself from district content. Your team reviews.
How do you get a number out of it?
Run a report, export it, build the pivot table.
Ask otto in plain English and get the answer.
Rip and replace?
Migrate everything first.
Start in front of what you run today. Consolidate later if you choose. Never mid year.
Five minute self check

Ask the people answering your phones.

Marc's advice to other IT leaders is simple. Before you change anything, look closely at the work that keeps coming back. Five questions and a few minutes with your team.

01

Who answers what never becomes a ticket?

Name the three or four people nobody assigned. The librarian, the front office, the tech everyone texts.

02

What do you hear ten times a week?

Ask your help desk staff for their top five. Write them down the way people actually ask them.

03

How much of it belongs to someone else?

Ask your techs for an honest guess at the share of calls meant for HR, payroll, or Facilities.

04

Where do people go when they don't know?

Follow one request from the first question to the fix. Count the handoffs along the way.

05

What would your team do with the time back?

Pick the project that keeps slipping. That is what this work costs you today.

Want a number to go with your answers? The Hidden Work Calculator turns them into hours.

Open the calculator

Common questions

Why do business help desks struggle in K12?

They assume every requester has an account and knows which team owns the problem. In a district, students, families, and many staff never log in, and requests cross IT, Facilities, HR, and transportation.

Can we see it before we commit?

Yes. We can build a working version of schoolAgent from your public website so you can watch it answer real questions. It runs alongside your current help desk, and your team does not have to set anything up.

What does the AI touch?

Assets, tickets, and operational workflows. It never touches academic records, behavioral records, or anything that decides a student's outcome. It is trained without PII, and a person stays in command of consequential actions.

Does it cover phone calls?

No. schoolOS runs on web, chat, email, and portal. Districts see call volume drop because the front door becomes the fastest way to get an answer.

Do we have to replace our help desk?

No. Most districts start with schoolAgent in front of the help desk they already run. Moving ticketing and assets onto schoolOS is a later choice, not a day one requirement.

For district IT teams

See what your website already answers

We read your public site the way a parent would and show you which common questions it answers and where people get stuck. Nothing needed from your team.

Get a free site review
schoolHelpdesk ticket queue