Up to
85%
less time on repairs
The full repair process.
- Before Plugboard
- 30 minutes
- After Plugboard
- 1 minute
Handle intake, loan devices, updates and collection in one connected repair workflow.
Every ticket opens with the person’s year and tutor group, the device they were issued and any loan or repair. One desk for school IT, in place of the one you run today.
Everything else the desk does is below.
A ticket opens with the requester’s year and tutor group, the device they were issued, its warranty and any loan or repair, so the first reply can be the answer.
Year, tutor group and student ID from your student system, and the device from your device management.
Set response and resolution targets for your team; breaches show on the dashboard.
Describe the problem and the person, device, category and priority fill in, and a walk-in fix is raised resolved on the spot.
The device page holds the owner, room, warranty, every repair and loan, and what your device management last reported.
Find the owner, location, warranty and service history from a device serial.
Issue a loaner and link it to the device and repair record.
For schools that own their students’ devicesA cracked screen goes from a card tap at the kiosk to collection on one repair, with coverage set at intake and a loaner on the same record.
Devices guideStudents and staff sync from your student system, with your identity account state beside each person.
Your student information system keeps students and staff current.
See the identity account state next to the person record.
Start a guarded MFA reset from the person record.
A card tap at the kiosk opens the job, and parents see the repair status and any approved charge, once the school links them.
A student taps their card at the library kiosk and picks repair, loan or request.
Students and staff submit requests and follow their progress from the portal.
Repair progress, current loans and approved charges in one place, once the school links each parent.
Flows carries the routine work across the desk. AI drafts the flows and acts on its own only where your people have agreed with it.
Describe the work in plain words. The draft is grounded in your own tickets, repairs and settings.
AI answers start as suggestions and act on their own only after your people have agreed with enough of them.
Accounts, devices and admin roles wait for a go-ahead with step-up, and nothing is deleted.
Student systems, device fleets, identity, security and backup monitoring.
Explore connectorsAlso connected: Cisco Meraki, Chrome Enterprise, Xero, ThreatLocker, UniFi and TeamViewer.
Not listed? We scope and quote custom connectors up front. Ask about yours.
Product names and logos belong to their owners.
Projects, rooms and equipment, bookings, maintenance and team workload.
Printer, network and AV health, security alerts and backup status in one place.
Every campus in the same tenant, with roles and queues scoped by site.
Charges, budget codes, purchasing and invoices with Xero or MYOB.
Reports and CSV export, insights, a knowledge base and a document library.
Raise and follow requests from the mobile app or a team-chat bot, with no tracking in the app.
Up to
85%
less time on repairs
Handle intake, loan devices, updates and collection in one connected repair workflow.
Plugboard is priced per licensed student, a year, from your census count. Every module, every staff account and every device are covered, and hosted AI comes with a monthly allowance. A 30-day trial on your own data follows the demo. Onboarding and your data import are a one-off line on the quote.
Each school runs on its own server in Sydney with its own database, and signs in through its own identity provider with MFA it can enforce. We hold no SOC 2 or ISO 27001 certification and no ST4S assessment, and the Security page says where each one stands.
Not here? Email hello@plugboard.app.
Yes. Plugboard is the whole service desk: tickets, devices, loans and repairs on the same records. When you switch, your people and devices come in from your student system and device management, and the desk connectors (Freshservice, Jira Service Management, Halo, ServiceNow, Zendesk and Web Help Desk) bring your tickets across. The connector catalogue shows each one’s scope and status.
Yes. Students and staff sync from Synergetic, Sentral, Compass, TASS or Schoolbox, and Entra or Google show the account state beside each person.
With AI enabled, Plugboard prepares triage, briefs and reply drafts in the background, and drafts flows when you ask. Triage, duplicate handling and the decisions inside flows run automatically only after people have agreed with them often enough. Reply drafts still need a person to send them, and accounts, devices and admin roles need a person’s go-ahead.
Managed hosting is a server per school in Sydney, with encrypted backups and an offsite copy in Oceania, best effort. Or run the same software on your own server, at the same price. Hosted AI is the exception: Cloudflare runs embeddings and decisions, and chat uses Anthropic’s Claude, processed by Anthropic in the United States. Names, emails and IDs are pseudonymised first, and a school can switch AI off. Security has the detail.
Yes. After a 15-minute demo we set up a 30-day trial on your own school’s data, before the first invoice.
Fifteen minutes on your devices, your student system and the workflow you want fixed, with a 30-day trial on your own data to follow.
We reply within one working day.