Service levels
Settings, Service level targets (/admin/sla). Needs module.sla and
workflow.manage.
Set response and resolution targets per priority, and per record type where a type needs its own. Plugboard marks late work Overdue and raises an alert when a target is missed.
Service levels under Service desk (/sla) is where the desk works from: how
much is overdue, split between tickets and repairs, then Late to resolve,
No first reply and Due soon. Targets and calendar on that page opens
the settings, and Open service levels on the settings comes back.
Setting targets
Section titled “Setting targets”The Targets section has one row per priority:
| First response within | How long until somebody should have replied |
| Resolved within | How long until it should be done |
| Measured | Whether this priority is tracked at all |
Type each target as a number of minutes, hours or days. Under it the page says what the target comes to in other words, such as “120 hours”. Nothing is saved until you choose Save targets.
A starting set that suits most school desks:
| Priority | Respond | Resolve |
|---|---|---|
| Urgent | 1 hour | 4 hours |
| High | 4 hours | 1 day |
| Normal | 1 day | 3 days |
| Low | 2 days | 10 days |
Set these to what you intend to achieve. A target you miss every time leaves the queue permanently red, which tells you as little as having no targets.
A target for one record type
Section titled “A target for one record type”A priority’s own row applies to every type of ticket. To give one type its own target, choose the priority and the type (Incident, Service request, Problem or Change) in the last row and choose Add a target for this type. The type’s row sits under its priority, with its own button to remove it.
An urgent incident might need a fix within 4 hours while an urgent service request can take a day. A ticket uses its type’s target where there is one, and its priority’s own row otherwise. Changing a ticket’s type re-dates it, the same as changing its priority or its service. Repairs use the priority’s own row.
A service’s own targets
Section titled “A service’s own targets”A service can set its own targets for each
priority and record type, and its own support hours. Compass might promise a
fix within two hours during the school day, while the desk’s normal target is a
day. Set them under Service levels on the service’s page, which needs
service.manage; what a service leaves empty is the desk’s, from this page.
A ticket filed under a service looks for its target in this order, first response and resolve each on their own: the service’s target for its priority and type, the service’s target for its priority, then the desk’s two rows as above. It is measured in the service’s support hours where the service has them, and in the desk’s working calendar otherwise.
Define priorities first
Section titled “Define priorities first”Targets are per priority, so the priorities have to exist before you can set them. Add them under Settings, Statuses & fields; see statuses & fields.
The working calendar
Section titled “The working calendar”Targets count decides what a day is:
- Around the clock: every hour counts, and a day is 24 hours.
- Staffed hours: only the desk’s hours count. Set the Timezone, the Desk hours and the Open days. A day in a target is then one working day, and the page says “working days” and “staffed hours”.
A ticket filed under a service with support hours of its own is measured in those hours instead.
The clock
Section titled “The clock”The clock runs from creation. It stops when the work is settled: resolved or closed, so the desk is not the one being waited on.
Which statuses count as settled is derived from their meaning (resolved and closed) rather than from their names, so renaming a status does not change the clock’s behaviour.
Pausing. Work waiting on somebody outside the desk can pause, so time spent blocked does not count against you. A ticket pauses while it is Waiting on requester (a reply from the person who raised it) or Waiting on supplier (a vendor, a carrier or a warranty provider has the next move), whatever your school calls those statuses. Moving a ticket from one to the other keeps the one pause running, and every earlier pause stays counted. A ticket shows when it paused, and that the clock restarts when it leaves the status it is in.
Who is owed a reply. A first response answers the person who asked. A ticket with no requester, raised by a monitor, a flow or a technician for themselves, has no response target, so the desk is never late for a reply nobody is waiting on. It keeps its resolve target. Setting a requester starts the response target, measured from when the ticket was raised, as a priority change is; removing the last requester drops it. An email from an address that matches nobody on file keeps both targets, because its sender is waiting for the answer.
School holidays
Section titled “School holidays”Closed in the school holidays, in the working calendar, makes the gaps between consecutive term dates count as closed. It is off until a school turns it on.
- The clocks on a desk that counts staffed hours stop over the break, so a ticket raised on the last afternoon of term falls due on the first morning back. When targets count around the clock, the holidays do not stop them.
- Loan reminders are held during the break, whichever way the clock counts. On the first day of term the held reminders go out, and holiday days do not use up the fortnight in which an overdue reminder is sent.
Where a piece of work stands
Section titled “Where a piece of work stands”| It reads | Meaning |
|---|---|
| On track | Inside its targets |
| Due soon | Close to a target |
| Overdue | Past its response or resolution target |
| Clock paused | Waiting on the requester or a supplier |
| Met | Resolved inside its target |
Once a ticket is resolved, the due column in the queue is empty. A ticket whose reply or fix is overdue says so at the top of the column beside its conversation: Reply overdue or Fix overdue, and how long ago it was due.
When work is overdue
Section titled “When work is overdue”Three things happen:
- The ticket or repair reads Overdue, in the queue and on the Service levels page.
- An alert is raised once, to the people who can see the work. For the highest-ranked priority on your list (Urgent, unless you add a higher one) the alert stays on screen until somebody dismisses it.
- The Overdue figure on Home goes up.
The alert fires once. A breach that stays breached does not raise another alert every minute, because people mute an alert that repeats.
Overdue is one number. Home, the Tickets tab and the Service levels page count the same thing: open work past its response or resolution target, each piece once. A repair and the ticket raised for it count once, as the repair. Somebody who sees tickets but not repairs gets the Tickets tab’s count.
Working the overdue list
Section titled “Working the overdue list”Open the Overdue tab on Tickets, or the Service levels page, first thing each day, before Unassigned.
Most overdue items at a school desk are waiting on somebody, with no status set to say so. Setting the right status, Waiting on requester or Waiting on supplier, is accurate and stops the clock.
Reporting
Section titled “Reporting”The SLA attainment report counts the tickets resolved in a period that met or missed their target, by priority and by record type, or by service. The Service review shows the targets each service’s tickets met beside its downtime, changes and problems. The Repair turnaround report shows how long repairs took, by month. Compare both against your targets. First contact resolution and Reopen rate show how often the desk fixed something the first time.
If the average is climbing, either volume is up or something is stuck. The overdue list tells you which.
Applies to tickets and repairs
Section titled “Applies to tickets and repairs”Tickets use the target for their service, priority and type. Repairs use the target for their priority.
Turning it off
Section titled “Turning it off”If your desk does not work to targets, leave module.sla off. Everything else
works, Service levels and its settings page leave the menu, and the queue is
not coloured by lateness. That suits a two-person desk with a queue short
enough to see in one screen.