SLA Policies
In the app: Settings → SLA Policies
Needs the 'View SLA' permission.
An SLA policy sets how fast a ticket should get its first reply and how fast it should be closed. This page lists your policies and lets you create, change, reorder and delete them. Policies belong to the organization and apply to every store, unless a policy is limited to certain mailboxes.
Policy list
The list shows every policy, active and inactive, in the order Squid tries them. The order matters: for each ticket, the first active non-default policy whose conditions match is used. The default is tried as a fallback.
Each row shows:
- the policy's name, with a "Default" badge on the default policy and an "Inactive" badge on a policy that is switched off;
- its description, when it has one;
- its targets, as "First response:" and "Resolution:";
- its conditions as small labels: the channels, priorities, tags and mailboxes it is limited to, and "Business-hours schedule" when it pauses outside business hours.
An older policy without any target shows "No response or resolution target — this policy measures nothing". Edit it and give it a target.
What you can do in a row:
- Reorder. Drag the handle on the left ("Drag to reorder") to move a policy up or down. The new order is saved at once and decides which policy is tried first.
- Activate or deactivate. The "Activate" or "Deactivate" button switches the policy on or off without opening it. Deactivating asks you to confirm first.
- Edit. The "Edit policy" button opens the policy.
- Delete. The "Delete policy" button deletes the policy after you confirm. This cannot be undone. The default policy cannot be deleted: make another policy the default first. Deleting a policy unlinks it from the tickets that used it; due times already set on those tickets stay.
"Create Policy" at the top opens an empty policy. When there are no policies, the page shows "No SLA policies yet" with a "Create Your First Policy" button. Without any policy, new tickets get no response or resolution due times. Due times already set on existing tickets can remain.
Seeing this page needs the 'View SLA' permission. Creating, editing, reordering, switching on or off and deleting need the 'Edit SLA' permission. The buttons are shown to everyone who can open the page; without 'Edit SLA' the action is refused.
A teammate whose access is limited to certain stores (Settings → Team) can read every policy, but can only create or change a policy that is limited to mailboxes of their own stores. A policy without a "Mailbox" condition applies to every store, so they cannot create, change or delete it.
Create or edit a policy
Needs the 'Edit SLA' permission.
"Create Policy" opens the "Create SLA Policy" dialog; the "Edit policy" button in a row opens "Edit Policy" for an existing one. The dialog holds the policy's name, its targets, its conditions and three switches. Nothing is saved until you click "Create" or "Update". "Cancel" discards your changes.
"Name" is required and can be up to 255 characters. It is what the list and reports call the policy.
"Description" is optional. Use it to note when the policy is meant to apply. A description can be changed but not emptied: saving it empty keeps the previous text.
Response and resolution targets
Needs the 'Edit SLA' permission.
"First Response Time" is how long a ticket may wait for its first reply to the customer.
"Resolution Time" is how long a ticket may stay open before it is closed.
For each target you type a number and choose minutes or hours. Rules:
- A policy needs at least one of the two targets. Leave the other empty, or at zero, to not measure it.
- The shortest target is 1 minute. The longest is 999 hours.
- Hours can be entered in quarters, such as 1.5 hours.
- When both are set, the resolution time must be equal to or longer than the first response time.
When you change a target on an existing policy, Squid recalculates due times for tickets that use the policy and are neither closed nor deleted. A first response that is already recorded is not given a new deadline when its target changes. The new due time is counted from the moment that ticket's clock started, not from the moment you saved.
Conditions
Needs the 'Edit SLA' permission.
Conditions limit which tickets a policy applies to. With every condition left empty, the policy applies to all tickets.
- "Channels": the policy only applies to tickets from the channels you select.
- "Priorities": the policy only applies to tickets with one of the selected priorities: "Low", "Normal", "High" or "Urgent".
- "Tags": the policy only applies to tickets that carry at least one of the selected tags. Tags are matched by name. Policies belong to the whole organization, so a tag name matches in every store that has a tag with that name. When no tags exist yet, create them under Settings → Tags first.
- "Mailbox": the policy only applies to tickets that arrived at one of the selected email addresses. A ticket with no receiving mailbox, such as a new live chat, does not match a policy limited to a mailbox. The mailbox condition checks the saved receiving address, so a ticket converted from email can still match it. When no mailboxes are set up, set up email under Settings → Email first.
How conditions combine: inside one condition, any selected value is enough. Across conditions, all of them must match. A policy with the channel "Email" and the priorities "High" and "Urgent" applies to email tickets that are high or urgent.
Pause outside business hours
Needs the 'Edit SLA' permission.
"Pause outside business hours" is off by default. When it is off, the clock counts every hour of every day.
When it is on, the clock only counts time inside the policy's own schedule, shown as "SLA business-hours schedule":
- "Schedule timezone": the timezone the schedule is in, written as a region and city, such as Europe/Amsterdam.
- Days: tick each day you are open. A ticked day starts at 09:00 to 17:00 and you can change both times. Unticked days are closed all day.
- Opening and closing time must be on the same day, and opening must be before closing. At least one day must be ticked.
Each policy has its own schedule. A change to the schedule applies to clocks that start or restart after you save. Tickets whose clock is already running keep the schedule they started with. An older policy marked "Business hours need activation" still counts every hour: edit it, turn on the switch and save a schedule to activate it.
Snoozing a ticket pauses its clock too, whether or not this switch is on.
Active and default policies
Needs the 'Edit SLA' permission.
"Policy active" is on for a new policy. Turning it off in the create dialog currently has no effect: the new policy is still saved as active. Create it first, then deactivate it in the list or edit it. An inactive policy is skipped when Squid picks a policy for a ticket. Tickets that already have the policy keep their due times.
"Default policy" marks the policy as the fallback. The default policy is used only when no other active policy matches the ticket, wherever it stands in the list. It still has to match its own conditions, so leave its conditions empty if it should catch every remaining ticket.
Only one policy can be the default. Making a policy the default removes the mark from the previous one, and the dialog tells you which policy stops being the default. A teammate whose access is limited to certain stores cannot change which policy is the default.
How a policy is applied to a ticket
Squid picks a policy for a ticket at these moments:
- when the ticket is created: a new email, a new live chat, a ticket someone creates by hand, a follow-up ticket or an imported ticket;
- when an email from the customer reopens a closed or snoozed ticket;
- when the ticket's priority or channel is changed, by a person or by an automation rule.
At that moment Squid goes through the active policies in list order and takes the first one whose conditions match. If none matches, it takes the default policy, when that one matches. If nothing matches, the ticket has no SLA.
The clock starts at that moment, also when the ticket had a clock before: a reopened ticket or a ticket whose priority changed gets new due times counted from that moment, and an earlier breach mark is cleared. The first response due time is the start plus the first response target, and the resolution due time is the start plus the resolution target, counting only scheduled hours when the policy pauses outside business hours.
A ticket breaches its first response target when no first reply was sent before the due time. It breaches its resolution target when it was not closed before the due time.
Things that do not change a ticket's policy: adding or removing a tag afterwards, and editing a policy's conditions. A tag-based policy therefore only catches tickets that already carry the tag at one of the moments above.
SLA results are in Reports, on the "SLA" tab.