Service desk
Queues and SLAs
Queues decide who looks at a ticket. SLAs decide how fast it must be answered and resolved. Administrators define queues, SLAs and business hours under Admin; see Administration.
Queues
Every queue appears under Queues in the service desk side navigation with its count of open tickets. Click a queue to list its tickets, or All queues to see everything.
How a ticket lands in a queue
- When you create a ticket, choose the Queue in the New ticket form. If you click New while a queue is selected, that queue is filled in for you.
- Recurring ticket templates set the queue for the tickets they create.
- Workflow rules can move tickets automatically. See Workflow rules.
Move a ticket to another queue
- Drag the ticket row from the list onto a queue in the side navigation.
- Open the ticket, choose Move queue… from the More actions menu, pick the Queue and add an optional internal note.
- Use Escalate and set a Target queue while raising the tier.
- Select several tickets in the list and click Move queue… in the bulk bar.
Every move is recorded in the ticket's activity under System.
Saved views
Above the queues, the side navigation has four built-in views that cut across all queues:
| View | Shows |
|---|---|
| SLA at risk | Tickets whose SLA is in warning or already breached |
| Customer replied | Open tickets where the latest note is a logged customer reply |
| Unassigned | Tickets with no primary resource |
| Created today | Tickets created today, in your business time zone |
The views are fixed; you cannot create or save your own.
SLA clocks
Which SLA applies
A ticket uses its company's SLA. If the company has none, it uses the SLA marked Default SLA. Each SLA holds targets by priority. The New ticket form shows the SLA name and both due times before you create the ticket. If you change the priority later, the due times are recalculated from the ticket's creation time.
The two clocks
Each ticket shows two countdown clocks at the top:
| Clock | Stops when |
|---|---|
| First response | A team member saves the first Reply to customer note. Internal notes do not count. Resolving the ticket also meets it. |
| Resolution | The ticket moves to a closing status. |
Note: The SLA editor also has a Resolution plan target column. The ticket screen shows clocks for first response and resolution only.
Business hours
An SLA runs either during Business hours or around the clock (24×7), set per SLA under Admin → SLAs. Business-hours SLAs count only time inside your opening hours and skip closed days and holidays, so a ticket opened late on Friday with a two-hour target is due on Monday morning. Opening hours, time zone and holidays are set under Admin → Settings.
What pauses the clocks
The clocks stand still while the ticket is in a status that stops the SLA clock. With the standard statuses these are:
- Waiting customer
- Waiting materials
- Scheduled
New, In progress, Escalated and Customer responded keep the clocks running. When the ticket leaves a paused status, the time it spent waiting is added to its due times: the resolution due time always moves, and the first response due time moves if no first response has been sent yet.
Booking a service call for a ticket on the Dispatch calendar can move the ticket to Scheduled, which pauses its clocks.
Administrators choose which statuses stop the clock under Admin → Picklists, so your list may differ.
Warning, breach and met
The list shows one SLA countdown per ticket, for whichever clock is most urgent.
| State | When | How it shows |
|---|---|---|
| On track | More than a quarter of the target remains | Teal countdown |
| Warning | Less than a quarter of the target remains | Amber countdown |
| Breached | The due time has passed | Red, with a negative countdown (or "late") |
| Paused | The ticket is in a paused status | "paused" in grey |
| Met | The clock was stopped in time | "met" in the list, MET on the ticket |
On the ticket, each clock also shows its due time and a bar of how much of the target is used. Tickets in warning or breach are collected in the SLA at risk view.
Limit: A breach is shown on the board and in reports. Frontline PSA does not send breach emails by itself; notifications are queued under Admin → Notifications.
Recurring tickets
Recurring tickets create scheduled work such as monthly maintenance. Open Recurring templates at the bottom of the service desk side navigation.
The list shows each template's company, queue, priority, schedule, next run date, assignee and the tickets it has created. Click Show inactive to include inactive templates.
Create a template
Click New template.
Enter a Title and pick a Company; both are required. Add a Description, Contact, Queue, Priority, Assign to, Issue, Sub-issue and Estimated hours as needed. These are copied to each ticket.
Choose a Contract, or leave it empty to use the company's default contract.
Set the schedule:
Field Meaning Repeats Daily, Weekly, Monthly, Quarterly or Yearly Every The interval. Monthly with 2 means every two months Lead days Create the ticket this many days before the run date Next run The date of the next occurrence End on Optional last date. The template turns inactive after it Leave Active ticked and click Create template.
Click a template to edit it. Delete removes a template that has never created a ticket. A template that has created tickets is deactivated instead.
When tickets are created
A ticket is created when a template's next run date, minus its lead days, is reached. The ticket is due at 17:00 on the run date, and the template's Next run moves to the following occurrence. Missed occurrences are skipped, not created late.
Due templates are checked automatically while the service desk is in use, about once an hour. Click Run now to create every ticket that is due today straight away. Running it twice on the same day does not create duplicates; if nothing is due you see "Nothing due today".