schoolAutomate
Part of the schoolSupport Suite
Coming soon

The Work Behind Every Request, Done Automatically

Describe a workflow in plain language and agentic AI builds it and runs it across the tools your district already owns. Nobody coordinates, nobody retypes data, nobody chases a ticket.

Become a design partner
Workflow builder
Staff onboarding
Published
When a new staff member is added, create their accounts, assign access by role, and schedule orientation
Describe a workflow
Trigger
New staff in HR
HR system
Action
Create accounts
Directory · Google
Approval
You sign off
Before access goes live
Action
Schedule orientation
Calendar · SIS record
Typed in plain language, drawn as a workflow across your systems.
Live · runs on every new hire
The problem

Routine Work Shouldn't Need a Ticket

Most of what lands in a district queue isn't a mystery. The steps are known and the outcome is the same every time. Yet a person still reads the request, retypes the data into three tools, and closes the ticket. Nobody decided anything.

The fix isn't a faster queue. It's work that runs itself the moment the trigger fires.

One address change, by hand
FO
Front office opens the ticket, reads the form
FO
Retypes the address into the SIS
TR
Forwards to transportation for the bus route
FO
Emails the family and closes the ticket two days later
Four handoffs. One field changed.
Connected systems
Your existing stack
Directory groups
AD or Google
SIS
Student records
Google Workspace
Email, Drive, devices
Web filter
Policies by class
Device management
Lock, wipe, locate
HR system
Staff changes as triggers
No consolidation required. Nothing replaced underneath.
Agnostic first

Runs Across the Tools You Already Own

schoolAutomate connects the systems your district already runs and automates workflows across them. No code, nothing ripped out. Your directory groups, SIS, Google, web filter, and device management keep doing their jobs. schoolAutomate does the work that used to happen between them.

Autonomy you control

Human Approved or Fully Automated. Your Choice.

Full automation where you want it. A parent submits an address change. The workflow verifies it, updates the SIS, and confirms with the family.

Human approved
Nothing happens until a person you pick says yes
or
Fully automated
Runs on its own, with a record you can check anytime
You pick one for each workflow. Start with approvals everywhere, automate more as trust builds.
Run log · Parent address change
Completed
Trigger · Address change submitted · 3:12 PM
Dana R. (parent), through the family portal
Verified · 3:12 PM
Checked against district records
SIS updated · 3:12 PM
The system of record, written directly
Family confirmed · 3:13 PM
"We updated your address for both students."
Zero people involved after the trigger
Workflow · Temporary whitelist
Restores in 2:58:14
Ms. Chen, via schoolAgent · 9:38 AMCan my classes use vimeo.com for the film unit this morning?
Approved by you
9:41 AM
Filter policy updated for Ms. Chen's classes
9:41 AM
Block restores automatically, teacher notified
12:41 PM
Temporary by design. The block restores itself.
Governance built in

Waits for Approval, Fires the Moment It Lands

When a request needs approval, the workflow waits. The moment approval lands, it fires. A teacher asks to whitelist a site for one lesson. You approve. The filter policy changes for her classes, then restores itself three hours later. No cleanup, no follow-up ticket.

Every workflow lives in one registry. An owner, permissions, and a full audit trail, so you always know what runs where.

One process, every school

The Same Work, the Same Way, in Every School

Define onboarding once and it runs the same at every campus. Same steps, same access rules, same records. When the process changes, you change the workflow and every school is current the same day.

Consistency without policing.

Workflow · Staff onboarding
One definition
Lincoln Elementary
14 runs this year
Roosevelt Middle
9 runs this year
Washington High
21 runs this year
District office
6 runs this year
Same trigger, same steps, every campus
How districts adopt

Two Ways In. One Automation Engine.

Orchestrate over the tools you own today, or consolidate onto the schoolOS IT stack. schoolAutomate does the work in both.

Start today
Keep your stack

Orchestrate

schoolAgent + schoolAutomate, on top of the tools you already run

schoolAgent answers at the front door. schoolAutomate runs workflows across your existing systems. You start deleting tickets on day one.

Works with your directory, SIS, Google, filter, and MDM
Nothing replaced underneath
Onboarding, filter, and SIS workflows run here today
When you're ready
One schoolOS stack

Consolidate

schoolSupport + schoolAssets, with orchestration built in

Replace the point tools with the schoolOS IT stack. schoolAgent and schoolAutomate are built in, and automations now run against one system of record. They do more.

One system of record for support and assets
Requests reach IT, HR, facilities, and the front office
Same automations, richer data, higher ceiling
The compounding proof
Mark a device lost and the workflow locks it, wipes it, and sends its last location. schoolAssets updates the record itself.
Where automation sits

Every Request Ends in Answer, Route, or Automate

One front door. schoolAgent answers common questions, routes work that needs a human, and triggers schoolAutomate when a request matches a workflow.

Intake
schoolAgent
The front door. Answers instantly, routes what needs a human, triggers workflows.
Coordination
schoolHelpdesk
Carries routed requests to resolution with the right team and full context.
Automation · You are here
schoolAutomate
The work behind requests, done automatically.

Answer shrinks the queue. Route speeds the queue. Automate deletes the queue.

Security

Built to Be Trusted With Your Systems

schoolAutomate holds credentials to your most sensitive systems. We built for that responsibility.

Read the security overview →

Least privilege access

Each connection gets only the access its workflows need. Revoke it anytime.

Everything on the record

Every action is logged and exportable, so you can always see what touched what.

See schoolAutomate in Action

Bring one workflow your team still runs by hand. Leave with it running.

Become a design partner