What SLAs track
Every SLA policy measures two things:- Response time — How long until a technician sends the first reply after a ticket is created.
- Resolution time — How long until the ticket reaches Resolved status.
Creating an SLA policy
Set priority targets
Define response and resolution times for each priority level (Critical, High, Medium, Low). For example: Critical = 15 min response, 4 hour resolution.
Set timezone
Select the timezone used for business hours calculation. This determines when the SLA clock starts and stops each day.
SLA statuses
| Status | Meaning |
|---|---|
| On Track | Within the target time window |
| At Risk | Approaching the target deadline (configurable threshold) |
| Breached | Target time has been exceeded |
| Met | Ticket was resolved within the SLA target |
SLA pausing
The SLA resolution timer pauses when a ticket enters the Waiting on Customer status. This prevents time spent waiting for a customer reply from counting against your resolution target. The timer resumes when the customer responds or the technician moves the ticket back to In Progress. Response time is not paused — it is measured only once (time from creation to first reply).Escalation rules
Configure automatic escalation when an SLA is at risk or breached:- Reassign the ticket to a senior technician or team lead
- Notify a manager via email or in-app notification
- Change priority to escalate urgency
SLA compliance reporting
View SLA performance across clients and time periods in PSA → Reports. The Service Desk Overview report includes:- SLA compliance percentage (met vs breached)
- Average response and resolution times
- Breach trends over time
- Per-client SLA performance breakdown
SLA data is also visible on individual tickets via the SLA badge, and on the PSA dashboard as an aggregate metric.