# SLAs

SLAs (AKA Service Level Agreements) are rules for how quickly you want to respond to and resolve customer issues.

Pylon supports three types of issue SLAs:

1. First Response Time: how quickly someone on your team should respond to an initial message or request from the customer.
2. Next Response Time: how quickly someone on your team should respond to each subsequent message in a customer request after the first.
3. Resolution Time: how long it takes to resolve a request after it’s been started (more often called Time to Resolution).

## [​](https://docs.usepylon.com/ticketing/sla#setup)Setup <a href="#setup" id="setup"></a>

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

<figure><img src="/files/fb2MTIls3TwShLMUEo1e" alt=""><figcaption></figcaption></figure>

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 <a href="#sla-alerts" id="sla-alerts"></a>

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 <a href="#support-hours" id="support-hours"></a>

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).

<figure><img src="/files/IxVC7bZ1DhnHJNHMkOit" alt="" width="375"><figcaption></figcaption></figure>

### SLAs vs Team SLAs

The key benefit is that Team SLAs only start ticking when the issue is assigned to that specific team, whereas SLAs start from issue creation. This prevents situations where, for ex. a sales team holds an issue for a week before passing it to support, and then support gets penalized for the entire week plus their response time.

SLAs should be used when:

* You want to measure the overall customer experience from issue creation to resolution.

<figure><img src="/files/dFQSFHi9iDlQewmdovOF" alt=""><figcaption></figcaption></figure>

Team SLAs should be used when:

* You want to measure individual team performance separately from the overall customer experience.

<figure><img src="/files/0jIJlCDSFQWCXzwbtYY4" alt="" width="311"><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.usepylon.com/pylon-docs/support-workflows/slas.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.