At Slinger, staff start at one Staff Resources page for almost everything. We followed three everyday requests from that page. About 90 seconds.
Get the full list for slinger.k12.wi.usMade by the schoolOS team from your public website. The schoolAgent scenes are a concept view, and the product screens use demo data.
Work Orders sits right in the Staff Resources menu and opens its own system. Maintenance already has a clear path.
The middle school handbook asks students to report Chromebook problems to the teacher. From there, none of the links on Staff Resources is for technology help.
The same goes for a classroom projector. Staff Resources has no technology help link for this either.
Maintenance and technology requests land in one queue, each tagged for the right team, with the room attached. Chromebook tickets attach to the device record, so the next repair starts with its full history. Your team keeps the work that needs them.
We followed three everyday requests from Staff Resources on slinger.k12.wi.us. What we found is common. Everything here comes from public pages, and we haven't posted it anywhere. The schoolAgent scenes are a concept view and the product screens use demo data.
For the Slinger technology team
We'll send you everything we found on slinger.k12.wi.us, what the site answers and where people get stuck. Nothing needed from you.
Send me the list