Modules · 1 of 16

Technology

Every ticket, every device and every dollar of damage recovery in one queue — with the device history attached to the ticket that mentions it.

Most districts run a helpdesk in one system, an asset register in a spreadsheet, and damage fees in a third place that nobody reconciles. The Chromebook a ticket is about and the Chromebook a fee is against are the same device, and nothing joins them up.

IT Helpdesk & Assets

Ticket lifecycle, SLA, device register, audits, damage fees and account provisioning.

Anything broken, missing or needed from Technology starts as a ticket that records who asked, when, what was done and how long it took. Every district-owned device carries its own record — where it is, who has it, and what has happened to it — so quoting an asset tag on a ticket links it to that device history.

module key: it_helpdesk · independently toggled per district

What it does

  • Ticket queue with categories, SLA policies, routing rules and auto-assignment
  • File on behalf of a colleague, so updates reach the person who actually asked
  • Walk-up kiosk, so counter traffic lands in the same queue as everything else
  • Email inboxes via IMAP polling, snippets, saved views and ticket dependencies
  • Knowledgebase articles and CSAT surveys on resolution
  • Device check-in/out, bulk checkout, and assignment to a person or to a room
  • Asset audits by building or room, reporting what is missing and what turned up elsewhere
  • Code 39 barcode label printing and an asset model catalogue
  • Damage and loss fees issued against a device, paid by Stripe checkout
  • Third-party data access requests and work account provisioning with approval

Walk through Technology on your own data

We load a copy of your buildings and roles, turn on the modules you asked about, and show you the queues your staff would actually see.