> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/support-workflows/slas-and-timers.md).
# SLAs and Timers
Set differentiated service level agreement timers on customer issues.
SLAs (Service Level Agreements) define how quickly you want to respond to, follow up on, and resolve customer issues.
Pylon supports four types of issue SLAs:
1. First Response Time: How long the customer waits for the first qualifying customer-visible reply. For tickets, timing normally begins when the ticket is created. For conversations, it begins with the first qualifying customer message. Replies from Pylon AI Agents count as a first response. Internal notes, private messages, and trigger-generated automatic messages do not count.
2. Next Response Time: How long the customer waits for a subsequent reply after the first response. Timing begins when the customer sends another qualifying message and ends when a team member sends a qualifying customer-visible reply.
3. Follow-up Time: How long it takes your team to send another customer-visible update when your team was the last to respond. Unlike Next Response Time, Follow-up Time is proactive and it measures whether your team follows up without waiting for another customer message. Internal notes do not count.
4. Resolution Time: How long it takes to resolve an issue. Closing the issue finalizes resolution time. Pylon measures it through the latest qualifying customer-visible reply from your team. If there is no qualifying reply, it uses the time the issue was closed. For a team SLA, Pylon uses that team’s latest qualifying reply or falls back to the close time.
Changes to SLA rules and support-hour settings apply going forward. Completed historical metrics are not recalculated.
Pylon also tracks **active time** — how long teammates actually spend working an issue. It has no target and cannot breach, so it is not an SLA, but it appears alongside the SLA timers on the issue and shares their counting settings.
## [](https://docs.usepylon.com/ticketing/sla#setup)Setup
1. Visit the [SLAs page](https://app.usepylon.com/settings/slas) and hit Create
2. Select from one of the available templates for common SLA configurations for a good starting point
3. Modify the trigger with the conditions and values that make sense for your business. SLAs can be applied based on many factors, including the priority of the issue, the type of customer who raised it, etc.
### Notification
To setup notifications for SLAs, choose the "Send Slack notification on SLA breaches" template. Update the channel to your preferred one, or the action to a different notification type (such as email).
When an issue violates an SLA
1. The configured action will be taken, for example notifying a Slack channel
2. Users can also subscribe to notifications for SLA breaches on issues they are assigned to on the [notifications page](https://app.usepylon.com/settings/notifications).
### Support Hours
If you want SLAs to only increment during your working hours, you can configure Support Hours on the [Settings Page](https://app.usepylon.com/settings/support-hours). This makes sure that weekends and evenings will not inflate your count of SLA breaches.
### Team SLAs
Team SLAs allow setting SLAs on how long a team is assigned to an issue. These run independently from issue SLAs. Team SLAs are visible in [analytics](https://app.usepylon.com/analytics?tab=general) and can be created via [trigger templates](https://app.usepylon.com/settings/slas/create?groupID=b929bfac-4b9a-475d-9075-0e13074d79f3\&category=teamSla).
### SLAs vs Team SLAs
The key difference is what each SLA measures. Issue SLAs measure the customer’s overall experience. For tickets, timing normally begins when the conversation becomes a ticket; for non-ticket conversations, it begins with the first qualifying customer message. Team SLAs measure a specific team’s performance and start when the SLA is applied or the issue is assigned to that team, whichever happens later. This prevents a team from being penalized for\
time before it owned the issue.
Issue SLAs should be used when:
* You want to measure the overall customer experience from issue creation to resolution.
Team SLAs should be used when:
* You want to measure individual team performance separately from the overall customer experience.
### Active Time
Active time measures hands-on effort per person, per issue, rather than elapsed time. It is configured in the same place as SLA counting — **Settings → SLAs → Counting** — and appears in the SLAs sidebar module on every issue. See [Active Time](/pylon-docs/support-workflows/slas-and-timers/active-time.md) for the full behavior.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.usepylon.com/pylon-docs/support-workflows/slas-and-timers.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
