> 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/getting-started/pylonboarding/slas.md).

# SLAs

Maintain high service levels on your customer issues.

## Overview

SLAs (Service Level Agreements) help ensure timely, consistent support by defining how quickly your team should respond to and resolve customer issues. With Pylon, you can customize SLAs to match the expectations of different customer segments, prioritize critical issues, and automate reminders or escalations when targets are missed.<br>

Pylon supports four types of SLAs:

* **First Response Time** – The time it takes for your team to respond to the first customer message
* **Next Response Time** – The time between a customer’s follow-up and your next reply
* **Follow-up Time** – The time it takes your team to send another update when your team was the last to respond
* **Resolution Time** – The total time it takes to fully resolve an issue

All SLAs can be configured to respect business hours and customized by priority, customer tier, and more. See [SLAs and Timers](/pylon-docs/support-workflows/slas-and-timers.md) for details.

***

## Setup

{% embed url="<https://demo.arcade.software/9xPNl8bk4fh5HvbtuKKI?embed=&embed_desktop=inline&embed_mobile=tab&show_copy_link=true>" fullWidth="true" %}

***

## Use Cases

* Tiered Support
  * Set stricter SLAs for enterprise accounts and more flexible targets for standard users
* Priority-Based Routing
  * Assign faster SLAs to issues marked as “Urgent” or related to critical workflows
* Proactive Escalations
  * Automatically alert managers or trigger escalation workflows when a deadline is missed
* Time-Sensitive Channels
  * Create different SLAs for Slack, in-app chat, or email based on the nature of each channel
* Resolution Reporting
  * Track SLA performance over time to identify trends and improve team efficiency

***

## Best Practices

* Use Templates to Start
  * Begin with a prebuilt SLA template and customize it to fit your needs
* Set Support Hours
  * Enable [Support Hours](/pylon-docs/support-workflows/support-hours.md) to prevent off-hours SLA breaches
* Enable Notifications
  * Set up breach alerts via Slack or email to keep your team aware and responsive
* Review SLA Breaches
  * Use Analytics dashboards to analyze performance and fine-tune thresholds and routing over time


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.usepylon.com/pylon-docs/getting-started/pylonboarding/slas.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.