Label conditions reference the selected label’s ID. Renaming that label preserves the condition; deleting it and creating another label with the same name does not reconnect the condition.
Understanding SLAs
An SLA policy measures one specific commitment against a target duration. A policy has three pieces:- What to measure — the metric (e.g. time to resolution, time to first response).
- When the clock starts — the starting point (when the SLA is attached, or backdated to when the ticket was created).
- What stops the clock — implied by the metric. Resolution stops on ticket closure; first response stops on the first reply from a member of the ticket’s workspace.
Creating an SLA Policy
1
Open SLA settings
Go to Workspace Settings → SLAs.
2
Add an SLA policy
Click Add SLA.
3
Configure the policy
4
Save the policy
Click Create to activate the SLA policy. Matching tickets will begin tracking automatically.
Metrics
The metric determines what the SLA is measuring — and therefore what stops the clock.First-human-response SLAs only count public replies from human members of the ticket’s workspace. AI messages, internal notes, system messages, and the requester’s own replies do not stop the clock.Public replies received through connected channels, including inbound email, count toward first-human-response SLAs. The clock stops at the reply’s timestamp, even if Serval receives the reply later.
Workspace membership is what makes a reply count. In a shared chat channel, a colleague of the requester might answer before a workspace member does. That reply doesn’t stop the clock unless the colleague also belongs to the ticket’s workspace, directly or through a mapped group.
If a ticket is resolved before a human ever responds (for example, fully handled by AI), the SLA closes out at resolution time. It records as Met if resolution happened within the SLA’s target duration, or Breached if it took longer — same met/breached logic as a normal completion.
Starting Points
The starting point controls when the clock begins.Start the clock after escalation
To time the first human response from the moment a ticket is escalated to a human:- Set What to measure to Time to first human response.
- Set Start the clock to When the SLA is attached.
- Add the Ticket is escalated auto-attach criterion.
ticket_escalated takes no field, op or value. Don’t use a ticket_field criterion with an escalation_level field: SLAs don’t support that field, and the API rejects it.
ticket_field criteria and conditions support these fields: status, type, priority, assignee_id, team_id, requester_id, category_id, escalated and tags. The API rejects a missing or unsupported field with an invalid-argument error.
Calendar Time vs. Business Hours
When creating an SLA, you choose how time is counted:- Calendar time (24/7) — The clock runs continuously, including nights and weekends. Use this for critical issues that require around-the-clock attention.
- Business hours — The clock only runs during your configured working schedule. Use this for standard requests where resolution outside business hours isn’t expected.
Configuring a Business Hours Schedule
If you select business hours, you’ll choose a schedule that defines your team’s working days and hours. Schedules include a timezone and per-day time windows (e.g., Monday–Friday, 9 AM – 5 PM).Schedules are reusable — the same schedule can be shared across SLA policies and assignment rules.
Counting in the Assignee’s or Requester’s Time Zone
When the schedule’s time zone is set to Assignee’s time zone or Requester’s time zone, the SLA counts the schedule’s hours in that person’s own profile time zone. With a Monday–Friday, 9 AM – 5 PM schedule set to Assignee’s time zone, a ticket assigned to someone in New York counts 9–5 Eastern, and one assigned to someone in San Francisco counts 9–5 Pacific. This also applies when the SLA uses the assigned group’s hours: the group decides the schedule, and the schedule’s time zone setting decides whose hours it runs in. See Requester’s and assignee’s time zones.- Unassigned tickets, and people without a time zone on their profile, use the schedule’s fallback time zone.
- When a ticket is reassigned (or its requester changes) to someone in a different time zone, the SLA is re-measured in the new person’s hours. The clock keeps its original start time and pause history, so reassignment does not grant a new full SLA duration. A change to someone in the same time zone leaves the SLA unchanged.
- Bulk assignee updates do not re-measure existing SLAs.
- Changes to a schedule’s time zone setting, or to someone’s profile time zone, apply to SLAs that attach afterwards and on the next reassignment, not to SLAs already running.
Auto-Attach Criteria
SLA policies can automatically apply to tickets based on conditions like:- Priority: Apply to tickets of a specific priority level
- Labels: Apply to tickets with specific labels
- Assignment group: Apply to tickets assigned to one of the assignment groups you select. Available once your workspace has assignment groups configured.
- Requester’s field: Apply based on an attribute of the ticket requester, such as their department, job title, email, timezone, or locale, or a user custom field where enabled. Type a value for text fields, including department. For custom fields with predefined options, select the values to match from a menu.
- Priority: Select Medium, Low, and No priority.
- AND Labels: Choose is not and select Serval Ticket and Spam.
Attach and remove SLAs from workflows
To start an SLA at a particular workflow step, create a policy with no Auto-attach criteria and set Start the clock to When the SLA is attached. A policy without criteria attaches only when explicitly requested. Use the Serval SDK from your workflow:ticketSlaId to remove that specific attachment later.
Attaching the same policy while its instance is active returns that instance without resetting its clock. Attaching a different policy in the same policy group replaces the current instance; other groups remain unchanged. After completion or removal, another attach can create a new instance. The policy’s starting point, business calendar, and pause rules still apply, and an instance can complete immediately if its completion event has already occurred.
Removing an already completed or cancelled instance leaves it unchanged. Removal does not prevent automatic matching from attaching an SLA on a later ticket update. Use a policy without attachment criteria when the workflow should control attachment exclusively.
SLA Pausing
You can configure pause conditions so the SLA timer stops when the ticket is in certain states. This prevents your team from being penalized for time spent waiting on external parties. Common pause scenarios:- Waiting on requester — Pause while waiting for the requester to provide more information
- Waiting on vendor — Pause while waiting for a third-party response
- On hold — Pause for tickets that are intentionally paused
SLA Tracking
SLA Status
Tickets tracked by an SLA policy show their SLA status:- On track — The ticket is within its SLA target
- At risk — The ticket is approaching its SLA deadline
- Breached — The ticket has exceeded its SLA deadline
SLA column in ticket lists
Add the SLA column to any ticket list to see how much time each ticket has before its SLA breaches. The column is hidden by default—turn it on from the ticket list’s column picker. Each cell shows the ticket’s most urgent active SLA:- Time remaining: a live countdown to the breach deadline. It turns red in the final hour.
- Overdue: how long the SLA has been past its deadline.
- Paused: the SLA timer is currently paused.
- Met or Failed: the SLA finished within, or past, its target.
When SLA Tracking Ends
SLA tracking stops when the metric’s completion event fires:- Resolution SLAs stop when the ticket reaches a “Done” or “Canceled” status.
- First-human-response SLAs stop when a human agent posts the first qualifying reply on the ticket after the clock started, or when the ticket is resolved without one.
SLA Reporting
Track SLA performance in analytics: The analytics dashboard includes an SLA performance chart that shows the percentage of tickets meeting SLA targets vs. breaching. You can filter the chart by priority, assignee, or other attributes to drill into specific areas.Common Questions
Can I have multiple SLA policies per workspace?
Can I have multiple SLA policies per workspace?
Yes. You can create different policies for different ticket types using auto-attach criteria. For example, one policy for critical tickets with a 4-hour target and another for low priority with a 72-hour target.
What happens if a ticket matches multiple SLA policies?
What happens if a ticket matches multiple SLA policies?
A ticket can have one active SLA per policy group. Policies without a group use their metric as the group, so by default one resolution SLA and one first-response SLA can coexist. If two policies in the same group both match a ticket, the first matching policy (by name order) attaches and the rest are skipped — use this to build priority ladders, where each rung’s auto-attach criteria target a different priority. Policies in different groups all attach and track independently. The ticket’s headline SLA status reflects the most urgent of the active SLAs (a breached SLA outranks an in-progress one; in-progress outranks paused; if two are tied, the one breaching soonest wins).
Can I have a resolution SLA and a first-response SLA on the same ticket?
Can I have a resolution SLA and a first-response SLA on the same ticket?
Yes — that’s the point of separating what to measure from when the clock starts. Configure two policies (e.g. “Resolve within 4h from creation” and “First response within 15m from attachment”), and both will track independently. The ticket sidepanel shows one row per SLA slot.
Can I run several resolution SLAs with different pause rules on the same ticket?
Can I run several resolution SLAs with different pause rules on the same ticket?
Yes — give each variant its own policy group. For example, create groups “Resolution — full time” (no pause conditions), “Resolution — excluding requester time” (pauses on a Waiting on requester status), and “Resolution — excluding vendor time” (pauses on Waiting on vendor). One SLA from each group attaches, and each clock pauses by its own rules, so you can report total time, time excluding the requester, and time excluding the vendor side by side. Within each group you can still build a priority ladder with several target durations. All policies in one group must measure the same metric, and the ticket sidepanel labels each row with its group name.
Can I change an SLA policy after creating it?
Can I change an SLA policy after creating it?
Yes. Updating an SLA policy affects how future tickets are tracked. Existing tickets that already have the SLA attached continue with their original target.
How do I see which tickets are about to breach?
How do I see which tickets are about to breach?
Filter your ticket list by SLA status to find at-risk or breached tickets. You can also use the SLA performance chart in analytics to see compliance trends.
How do I remove an SLA from a ticket?
How do I remove an SLA from a ticket?
Open the ticket, expand the SLA row in the sidepanel, and select Remove SLA. The SLA moves to a “cancelled” state — it stays in the ticket’s activity history but no longer counts toward breach scanning. Other SLAs on the ticket are untouched.

