SLA
How SLAs work in Elion ITSM and how you set them up with business calendars, policies, the priority matrix, pauses and warnings.
On this page
The SLA is the committed time to handle a service desk ticket. Elion ITSM measures it with two clocks, First response and Resolution, which count only business time, and it warns you before they are breached.
How to read the SLA inside a ticket is explained in Read a ticket's SLA. This page explains how to set it up.
The pieces
Piece | Where | What it is for |
|---|---|---|
Calendars | Settings → Calendars | The business hours and holidays the clocks run on. |
Policies | Settings → SLA, Policies tab | First response and resolution targets, and which tickets they apply to. |
Priority matrix | Settings → SLA, Priority matrix tab | Which priority a ticket gets based on its impact and urgency. |
Simulator | Settings → SLA, Simulator tab | Which policy a test ticket would get and when it would be due. |
Escalation | Settings → Resolver groups, Escalation button | Who is notified as the SLA is used up. |
How a ticket's policy is chosen
When the ticket is created, its priority comes from the impact and urgency matrix (or an agent sets it manually).
Elion ITSM checks the enabled policies in list order and uses the first one that matches the ticket.
If none matches, the ticket has no SLA.
In a CSM desk, if the customer account has an active contract with an SLA policy, the contract's policy takes precedence. See Accounts and contracts (CSM).
What a new company comes with
Two calendars: Chile hábil (Monday to Friday from 08:30 to 18:00, with Chile's national holidays; it is the default calendar) and 24x7.
Five policies by priority, in business minutes of the Chile hábil calendar:
Policy | First response | Resolution |
|---|---|---|
P1 · Critical | 1 h | 4 h |
P2 · High | 2 h | 8 h |
P3 · Medium | 4 h | 1 d (24 business h) |
P4 · Low | 8 h | 2 d (48 business h) |
P5 · Planned | 16 h | 3 d 8 h (80 business h) |
All of them warn at 75% used and pause resolution while the ticket waits on the requester or a vendor. You can change, reorder or delete them.
Pauses and warnings
Pauses: each policy decides which waiting reasons pause the resolution clock: Waiting for the requester, Waiting for a vendor, Waiting for a change or Other reason.
Warnings: when a clock uses up its policy's warning percentage, the ticket goes at risk and the assignee is notified. When it is breached, they are notified again and the group's escalation steps fire.
Who can set it up
To see the policies and the matrix and use the simulator you need View in the SLAs and calendars module.
To create, sort, edit and delete policies and calendars you need Administer in that module (for example, the Administrator role).
This module exists only if your company's plan includes service desks.