Tickets
/tickets, and /tickets/<id> for one. Needs module.tickets.
The service desk queue for everything that is not a device repair: faults, requests and questions.
Optional Facilities, Administration and other desks add department filters, service questions, locations and explicit transfers to this workflow. See working across departments and the administrator guide.
To log a ticket from the desk, press New ticket on Tickets, or New in the menu. The composer fills itself in from what you type, can resolve a ticket you dealt with on the spot, and links people, devices and records you @-mention. See raising tickets and repairs.
Problems, major incidents and changes
Section titled “Problems, major incidents and changes”Three kinds of work start from tickets:
- Problems: the cause behind repeated incidents, with a root cause, a workaround and a known-error mark. Select incidents and choose Raise a problem; the Problems tab lists the open ones.
- Major incidents: an outage many people report, with one notice to the school. Declare major incident is in a ticket’s More actions menu.
- Changes: scheduled work with its own approval. A ticket of type Change offers Create change record.
A major incident, or an incident about a monitored service that went down, lists Changed in the last 72 hours under the ticket’s title: the changes made near the outage. See changes near an outage.
The queue
Section titled “The queue”The tabs across the top are Mine, Unassigned, My queue, Overdue, All open and Problems, each with its count. The queue comes back to the tab you were on when you return to it. Status and Priority narrow the list, and Filter holds the rest: the department, the support tier when the school has more than one, frustrated requesters, resolved and closed tickets, and Major incidents. Where the school’s AI is on, Describe a filter is first in the Filter menu; see filtering the page. Display, at the end of the row after the count, sets the sort, the columns and cards or a table. Save view keeps the current filters as a view of your own.
Overdue lists open tickets past a response or resolution target, leaving out paused ones. A ticket whose repair is late is overdue too. See service levels.
Select tickets to change their status, priority or assignee together. The same bar offers Raise a problem and Add to major incident, and Suggest fields while the school’s AI is on.
Tone is an optional column. Only a staff member’s ticket has a tone; see sentiment and staff experience.
Working on a ticket
Section titled “Working on a ticket”The header names the ticket and says where it came from: “Raised 24 Oct 2026, 5:38 am · Walk-in”, with the department first when the ticket sits in one. Beside the title are the favourite star, Print label, and More actions: the school’s own actions, View history, Email delivery records, Transfer department, Merge tickets, Declare major incident, Share a secret and the keyboard shortcuts. Each appears only where it applies and you hold the permission. Assign me, or Take over from the current assignee, sits with them while the ticket is open, and Reopen once it is settled.
Under the title, the status is a row of steps. Choose a step to move the ticket there.
The ticket has three tabs:
| Tab | What you will find |
|---|---|
| Activity | The summary, the original report, the conversation and the reply composer |
| Work | The checklist, assigned subtasks, evidence, dependencies, templates, approvals, security approvals and time tracking; on a problem, its cause and workaround |
| Files | Attachments from messages you can access, with internal files labelled |
A tab with nothing in it shows no count. Pending approvals and required work or child tickets that block completion appear above the tabs. Switching tabs keeps unsaved inputs. Arrow keys move between tabs; following a link to a tool opens the tab that holds it.
Above the tabs, a strip shows Time logged, against the estimate when there is one, your timer, Watchers and Work done out of the total when the ticket has a checklist or subtasks. Time and Work open their sections. Watchers opens People kept informed: who gets replies by email, with Remove beside each and a box to add someone by name or address. The eye beside it watches the ticket, or stops watching it.
The column beside the conversation
Section titled “The column beside the conversation”Everything the desk knows around the ticket stays in view beside it, in one compact column:
- The clock, when a promise has run out: Reply overdue or Fix overdue, how long ago it was due and, for a late reply, when it must be resolved by.
- The requester: who asked and how to reach them, and where the requester is set or changed. With nobody set it reads No requester. The name links to their person page. Choosing No requester in the requester picker takes the requester off the ticket, with Undo in the message that follows.
- Their devices: each device with what its device management last said
about it (the operating system, a compliance state other than compliant,
when it last checked in, when its warranty ends), the loan devices they hold with the date each is due back,
and their recent repairs. Loans show for people with
loan.viewwhile the Loans module is on. Link puts a device on the ticket. - Ticket details: a ruled list of the ticket’s facts. Each value is its own control and reads as plain text until you point at it: status, assignee, queue, support tier with Escalate and De-escalate, priority, the service level and when the reply and the fix are due, type, category, the service, location and labels. More holds impact, urgency, the estimate and the dates.
- Related: everything else that bears on the ticket, in one section.
Related starts with what is linked, a row each: the device, with what its device management last said; a repair; the article or documentation that answered it; the ticket it carries on from or was raised again as; tickets merged into it; the ticket it is part of, the tickets under it, and related tickets with how they relate. Link offers what is not linked: a device, a repair, an article, documentation, a parent, a child or a related ticket.
Under the linked rows, each part separated by a rule:
- The problem’s Workaround, on an incident caused by a problem.
- Other tickets: Also open for the requester, On the same device and Reads like this one, with the words that matched.
- About the requester: how many other tickets they raised this term, the school’s own documentation and help articles for the ticket, links into their other systems, and Manage their account, which resets a password, locks the account or changes licences, each action recorded on the ticket. See account recovery.
- Suggested: one-click actions, below.
- What this mentions: the monitored services and printers the ticket names, or Down in this room.
- Device actions on the linked device, through its device management.
- Changes linked to the ticket.
- Supplier, when the ticket is with one or is waiting on one. See waiting on a supplier.
- Connected systems, Work status and the ticket’s flows.
When the ticket’s workspace is 1,600 pixels wide or more, it uses three columns: Work on the left, the conversation in the middle and this column on the right, with status, priority, assignee, queue and service level as controls in a strip under the title, and Ticket details folded at the top of the column. Below 1024px, Ticket details opens the requester, the details and Related as a sheet over the conversation.
With the Time tracking module on, you can run a timer on a ticket, log time with a reply or note, set an estimate and see every entry on the Work tab. The timer can start by itself when you begin writing. Resolving a ticket you have logged no time on can ask you to add some first. See time tracking for all of it.
ThreatLocker requests
Section titled “ThreatLocker requests”When a ThreatLocker request on the ticket is
waiting, it appears at the top of the ticket at every screen width, naming who
asked, on which computer and for which file. People with device.manage can
Approve or Deny it there, the same permission as on the
Security page. Anybody else sees that it is waiting on
somebody who can manage devices. After a decision, the strip stays as a
confirmation so you can see what you just did.
Connected systems
Section titled “Connected systems”Connected systems lists what each connected system knows about this ticket: the ThreatLocker request, the device’s management state and last check-in, the requester’s directory account, monitoring for any services the ticket mentions, and links to the requester’s other systems. Choose a row to jump to its detail. A system with nothing to say about this ticket is left out.
Moving your desk across from Zendesk or Web Help Desk? See moving in for carrying the open tickets over.
A ticket carries
Section titled “A ticket carries”| Number | Sequential, and what people quote |
| Subject and body | What was asked |
| Requester | Who asked, whether or not they have an account |
| Type | Incident, Service request, Problem or Change |
| Category | What it is about |
| Service | The service it is filed under, when there is one |
| Queue | Which team owns it |
| Assignee | Which person owns it |
| Support tier | First line, Second line, Third line or the school’s own names |
| Status | Configured under statuses & fields |
| Priority | With the type, sets its service level targets |
| Supplier | The supplier it is with, when there is one |
| Conversation | Replies and internal notes |
The ticket’s service
Section titled “The ticket’s service”The Service row in Ticket details names the service
the ticket is about, such as Wi-Fi or Compass, with its status. When the
ticket was filed under it because it named it, the row reads Matched on
and the words, such as Matched on “Wi-Fi”. When the ticket named several
services, each is listed under Suggested with Use, and Choose
another opens the school’s services. People with ticket.update choose one
with Change and take it off with Clear, and a person’s choice is never
overwritten. See a ticket’s service.
A ticket filed under a service shows the service’s runbooks in its documentation, and Reports can count tickets by service.
Support tiers and escalation
Section titled “Support tiers and escalation”A ticket sits on a support tier, starting at the first. The school names its tiers, up to five, and can give each a queue and a person in ticket settings. Without that, they are First line, Second line and Third line.
Support tier, under Ticket details, names the ticket’s tier with Escalate and De-escalate beside it. Both are in More actions too, with the tier they lead to. Each moves the ticket one tier.
The dialog says what will happen, from the tier’s settings, such as From Second line to Third line. It is assigned to Sam Okafor.:
| The tier has | The ticket |
|---|---|
| A queue and a person | Goes to that queue, assigned to that person |
| A person only | Is assigned to that person |
| A queue only | Waits unassigned in that queue for whoever works it |
| Neither | Keeps its queue and assignee; only the tier changes |
Escalating asks Why it needs the next tier: what has been tried, and what the next tier needs to do. De-escalating asks why too, but leaves it to you. The reason is kept in the ticket’s history with your name.
- The person is assigned only where the ticket’s department and campus rules allow it. Otherwise the ticket waits unassigned in the tier’s queue, and the confirmation says why it was not assigned.
- The person it is handed to is told, in their own notifications.
- A resolved or closed ticket has to be reopened before it moves between tiers, and a merged ticket moves with the ticket it was merged into.
- Every move is in the audit log, with the tiers, the queue and assignee it changed and the reason. Flows never escalate a ticket: a flow moves one by setting its queue and assignee.
Support tier in the Filter menu lists the tickets on one tier, as a chip you can remove. Reports can count tickets by Support tier too; see report boards.
Moving between tiers needs ticket.update.
Waiting on a supplier
Section titled “Waiting on a supplier”Waiting on supplier is a ticket status for when the desk has done its part and a vendor, carrier or warranty provider has the next move. Like Waiting on requester, it stops the service level clock, so a part spending three days in the post does not make the desk late. Moving between the two keeps one pause running. The portal shows the requester Waiting on a supplier.
While a ticket is waiting on a supplier, Supplier in the column beside the conversation offers the school’s suppliers to choose from. Once one is chosen, the card shows up to three of their contacts with a link to ring or email each, their support hours, the response and resolve times they promise, and the school’s account number with them. Change picks another or removes it. The supplier’s record lists the ticket under Waiting on them.
Choosing a supplier needs ticket.update.
Security incidents
Section titled “Security incidents”Security incident is a built-in category for a phishing email, an account that has been taken over, ransomware, or a stolen laptop with student reports on it. Triage chooses it from words such as “phishing”, “scam email”, “suspicious sign-in”, “hacked”, “compromised”, “data breach”, “ransomware”, “malware” or “stolen laptop”, ahead of the password and email rules, so “I gave my password to a phishing email” is a security incident.
Once the school has a Security department, set in Ticket settings, security incidents go there, and only its members and administrators see them. An administrator sees every security incident, member or not.
Handed to Security
Section titled “Handed to Security”Who raises the ticket, or sets its category, decides what happens:
| Who | What happens |
|---|---|
| A requester, through the portal, email or Microsoft Teams | It goes straight to Security, and the requester keeps seeing their own ticket |
| A member of Security, or an administrator | It goes into Security, and they keep seeing it |
Anyone else with ticket.update, raising it with New ticket | It is handed to Security as soon as it is raised. They are told Handed to Security. You will not see this ticket again unless you are added to Security. and go back to the queue |
Anyone else with ticket.update, changing a ticket’s category to Security incident or accepting it as a suggestion | They are asked first, then it is handed over and they are told the same |
| A flow, a ticket button, the AI triage or re-triage | The same hand-off, as the flow or the person pressing the button |
Somebody with only ticket.create, such as a student helper | It stays on the ICT desk |
The question before a hand-off is Hand this ticket to Security?: Only the people in Security will see it. You will not see this ticket again unless you are added to Security. Under it: Anything already sent about this ticket stays where it went. Hand to Security hands it over, and Cancel leaves the ticket as it was.
That last line matters. A hand-off moves the ticket, not what has already happened on the ICT desk: a toast, a notification email, a flow run, an AI summary or a Teams thread stays where it went. Ask staff to report security problems through the portal, which never touches the ICT desk.
The hand-off moves the ticket into Security’s default queue and clears its
assignee. It needs ticket.update and no other key, because it chooses no
destination. Nothing moves a security incident back to the ICT desk except a
member of Security or an administrator using Transfer department with a
reason. A ticket kept in step with another ticketing system stays with that
system’s desk.
Each hand-off is in the audit log as Ticket handed to Security, with the ticket number, the departments it went from and to, and whether it was raised, recategorised or handed over by an automation. The subject and the details are never recorded there.
The Security desk
Section titled “The Security desk”On Tickets filtered to the Security department, or for somebody whose only desk is Security, the count beside the filters adds how many tickets were handed to Security in the last 30 days, such as 9 tickets · 9 handed to Security in 30 days. It is not shown at zero, or anywhere else.
Where security incidents stay on the ICT desk
Section titled “Where security incidents stay on the ICT desk”Security incidents stay on the ICT desk, seen by everyone who works it, while:
- no Security department is set in Ticket settings;
- the department set is paused; or
- the server has no restricted database role, which private departments need. This applies to a self-hosted server set up without it, and Ticket settings says so: Security incident stays an ordinary ICT category.
Replies and internal notes
Section titled “Replies and internal notes”The composer has two tabs, Reply and Internal note (R and N from anywhere on the page). The line beside them says who it reaches: the requester’s name, Portal only, not emailed, or Staff only.
A reply appears in the requester’s thread on the portal. With Email requester ticked, it is emailed to them too, and to the people kept informed on the ticket; CC and BCC add more recipients. The button reads Send.
An internal note is for the desk. It never sends, and it needs the separate
ticket.internal permission. The composer changes colour while it is on, and
the button reads Add internal note.
The arrow beside the button chooses the status the ticket moves to when it goes, such as Send and set Resolved. Log time opens the time field with it; see logging time with a reply or note. Ctrl Enter (Cmd Enter on a Mac) sends from the box. The filter beside Conversation shows All messages, Replies or Internal notes.
An internal note is where somebody writes “third time this term, escalate” or “her mother rang, do not put this in writing”. Separating the permission means a school can hand a casual or a student helper the queue without handing them that.
A failed send keeps your draft. If the message was saved but an attachment failed, use Retry attachments to send the remaining files without creating a duplicate message.
Suggested actions
Section titled “Suggested actions”A card headed Suggested offers things you can do in one click, each with the fact behind it. Reply that the printer fault is known, because monitoring is reporting it. Issue a laptop bag, because there are eleven. Open the directory panel for an access request, carrying the ticket with it.
These come from rules and live lookups rather than a model, so they are instant. Nothing happens until you choose one.
What the AI does here
Section titled “What the AI does here”With an AI connector that answers, the AI does four things on a ticket. Each says in words what it did.
Triage. Each ticket is classified, as it arrives, into a type, a category, an impact and an urgency. Your own rules run first and always; the model is asked to improve on them. Its answer is accepted only where it picks from lists you already use, so it cannot invent a category that turns up as a heading in your reports. What it proposes appears as Suggested under Type, Category, Priority or Assignee, with the reason on hover and buttons to accept or dismiss it. A value the desk set by itself reads Set automatically, with Undo.
The summary. A plain paragraph at the top of Activity says what is wrong and where it stands, with “Summary · From 3 messages” under it. Refresh asks for another read. Show the suggestions unfolds the likely cause, the next steps and similar solved tickets. A ticket with no summary yet, such as one imported or raised by a connector, offers Prepare a summary in its place, which asks the model there and then and reads Preparing… while it works. With no model connected, nothing is offered.
A suggested reply. It waits in the composer as “Suggested reply · Tab to use”, with Use draft and Dismiss. It is never sent for you.
Draft and Improve. Draft in the composer writes a reply when you ask. Improve rewrites what you have typed in a reply.
Anything the AI decides can be overwritten, and the moment somebody edits one of those fields the ticket is marked as theirs and is never re-classified.
While no model can answer, Refresh, Prepare a summary, Draft and Improve are not shown. Your triage rules and the suggested actions above keep working.
Canned responses
Section titled “Canned responses”Saved replies for the answers you send repeatedly, configured under ticket
settings. Type / at the start of an empty line in
the composer, or choose Canned responses, to drop one in for editing.
When you send the same canned response often, put the answer on the public help centre.
Reopening
Section titled “Reopening”A closed ticket can be reopened within a window you configure. Past that, Reopen raises another ticket that references the old one, and says so.
Too short a window turns one unresolved problem into several tickets. Too long and something from last term comes back to life on somebody who has forgotten it.
A ticket that comes back inside the window counts towards the Reopen rate, and is not counted as fixed at first contact. See reports.
Merging
Section titled “Merging”Duplicate tickets can be merged with Merge tickets, which happens most often when somebody emails and then walks up to the desk. The merged ticket keeps the conversation from both. A merged ticket says where it went, and Separate them again undoes the merge.
Service levels
Section titled “Service levels”Tickets are covered by service level targets per priority, and per type where your school sets a type its own target. A ticket with a target reads On track, Due soon, Overdue, Clock paused or, once resolved inside its target, Met. The queue’s due column is empty for a resolved ticket.
The clock reads which statuses mean the desk is not the one being waited on, so a ticket waiting on the requester or on a supplier stops accruing.
A first response is owed to somebody who asked. A ticket with no requester, such as one raised by a monitor, a flow or a technician for themselves, has no response target and is never late for a reply; it keeps its resolve target. Setting a requester starts the response target, measured from when the ticket was raised. An email from an address that matches nobody on file keeps its response target, because its sender is waiting.
Raising a repair from a ticket
Section titled “Raising a repair from a ticket”Work that starts as a question and turns out to be a device problem should become a repair, because that is where the device, the repair type, the coverage and the cost live.
Directory actions work the other way: an account change in the Directory accounts view of People can be attached to an existing ticket or raise one, so “please give Sarah access to Tom’s mailbox” becomes an auditable record.
Permissions
Section titled “Permissions”| Permission | Allows |
|---|---|
ticket.view | See tickets |
ticket.create | Raise one |
ticket.update | Change status, queue, assignment; escalate and de-escalate between support tiers; choose the supplier a ticket is with |
ticket.comment | Write replies |
ticket.internal | Read and write internal notes |
ticket.close | Close one |
ticket.transfer | Transfer one to another department |
Raising a problem, declaring a major incident and adding tickets to one need
ticket.create and ticket.update. Time tracking uses these too, with
workflow.manage for changing somebody else’s time entries. See time
tracking.
Configuration
Section titled “Configuration”Categories, queues, support tiers, canned responses, the reopen window and time tracking are under Settings, Ticket settings; see ticket settings. Statuses and priorities are under Settings, Statuses & fields, alongside the repair ones; see statuses & fields.