# Ticket SLAs

Set first response and resolution targets for each ticket priority, and find the tickets that are close to or over their target

A ticket SLA is a time target for a ticket: one target for the first response and one target for the resolution. Each department sets its targets for each ticket priority on **Settings > \<department> > SLAs**.

> **Info:** Ticket SLAs are in early access. If **SLAs** does not show in your department
> settings, or the page shows "SLAs are not available for your organization,"
> contact Risotto support to turn on SLAs for your organization.

## How it works

1. A ticket gets two SLA clocks when it is created: **Response** and **Resolution**. Both clocks start at the time Risotto creates the ticket.
2. Risotto takes the targets from the ticket's department and priority. The priority is the one set by a person, or else the [priority that Risotto suggests](https://www.tryrisotto.com/docs/dashboard/settings/ticket-priority#ai-suggested-priority).
3. The **Response** clock stops at the first response on the ticket. See [When each clock stops](#when-each-clock-stops).
4. The **Resolution** clock stops when the ticket is resolved or closed. It does not count the time that the ticket is paused or waits for the requestor.
5. Each clock shows a state: on track, at risk, breached, or met. A clock is at risk in the last 25% of its target. For example, a 60-minute target is at risk in its last 15 minutes.
6. When a clock becomes at risk, Risotto adds an internal note to the ticket.

SLA clocks use calendar time, 24 hours a day, 7 days a week. They do not use business hours, time zones, or holidays.

## Turn on SLAs for a department

SLAs are off for each department until you turn them on. An Org Admin, a Manager, or a Supervisor of the department (or of its parent department) can change the SLA settings. See [Permissions](https://www.tryrisotto.com/docs/operating/permissions).

1. **Open the SLAs page**

   Go to **Settings > \<department> > SLAs**. **SLAs** is in the
   **Workflow** section of the department's settings.

2. **Turn on Track SLAs**

   Turn on the **Track SLAs** switch. The message "SLAs are on. Existing
   tickets update in the background." appears.

   *Product example: A department's SLAs page in the Risotto dashboard, with Track SLAs on and the SLAs of existing tickets being calculated.*

3. **Wait for existing tickets**

   Risotto calculates the SLAs of all the department's existing tickets, open
   tickets first. Below
   the switch, "Calculating the SLAs of existing tickets: 312 of 1,240 done"
   shows the progress. When the calculation is complete, the text changes to
   "SLAs are calculated for all tickets".

Risotto measures existing tickets from the time they were created. An old open ticket can show as breached immediately after you turn on SLAs.

When you turn off **Track SLAs**, the message "SLAs are off for this department" appears, and the department's tickets no longer show SLAs. Risotto does not delete the SLA data. If you turn the switch on again, Risotto calculates the SLAs again.

## Set targets

The **SLAs** card has one row for each priority: **Urgent**, **High**, **Medium**, and **Low**. Each row has two targets in minutes: **First response (min)** and **Resolution (min)**.

1. **Enter a target**

   Type the number of minutes in a field. Below the field, the target shows in
   days, hours, and minutes, for example "= 1d 4h" for 1680 minutes.

2. **Save**

   Click **Save**. The message "SLA settings updated" appears. To discard your
   changes instead, click **Cancel**.

   *Product example: A department's SLAs card in the Risotto dashboard, with the Urgent first response and High resolution targets changed, and Save.*

A target is a whole number from 1 to 525,600 minutes (365 days). If you leave a field empty, the department uses the default target. The empty field shows the default in minutes, and the text below it shows the default as a duration, for example "Default: 4h".

| Priority   | Default first response | Default resolution |
| ---------- | ---------------------- | ------------------ |
| **Urgent** | 15 minutes             | 4 hours            |
| **High**   | 1 hour                 | 8 hours            |
| **Medium** | 4 hours                | 1 day              |
| **Low**    | 8 hours                | 2 days             |

When you change a target, Risotto updates the open clocks of that priority in the background. A clock that already stopped keeps the target it was measured against. A lower target can make an open ticket breached.

A new [sub-department](https://www.tryrisotto.com/docs/dashboard/settings/sub-departments) starts with a copy of its parent's targets. After that, you change the targets of each department separately. **Track SLAs** is not copied: it starts off for the new sub-department.

## When each clock stops

### Response

The **Response** clock stops at the first response on the ticket, for example:

- Risotto's first reply to the requestor
- an escalation of the ticket to your team
- a reply from your team in the Slack thread of the ticket

If the ticket is resolved or closed before any response, that counts as the first response. The **Response** clock does not pause.

> **Note:** A comment in the dashboard, or a comment in a synced ticketing system such as
> Jira, does not stop the **Response** clock.

### Resolution

The **Resolution** clock stops when the ticket moves to **Resolved** or **Closed**. While the ticket is **Paused** or **Awaiting response**, the clock stops and the target does not count that time. The clock runs again when the ticket leaves that status.

The clock does not stop for **Awaiting support** or **Awaiting approval**.

### Changes to an open ticket

- **Priority or department change.** The open clocks use the target of the new priority in the new department. Risotto still measures from the time the ticket was created. If the new department has SLAs off, the ticket shows no SLA.
- **Reopen.** If a resolved or closed ticket [reopens](https://www.tryrisotto.com/docs/concepts/ticket-lifecycle#reopening-a-finished-ticket), the **Resolution** clock runs again. The time that the ticket was resolved or closed counts toward the target. If the ticket had a first response before it was resolved or closed, the **Response** clock does not change.
- **No priority.** A ticket with no priority has no SLA. The ticket shows "Set a priority to track SLA". When someone sets a priority, the clocks start, measured from the time the ticket was created.
- **Duplicate.** A ticket marked as a duplicate has no SLA.

## SLA states

| State        | What it means                                                           |
| ------------ | ----------------------------------------------------------------------- |
| **On track** | The clock runs and has more than 25% of its target left.                |
| **At risk**  | The clock runs and has 25% or less of its target left.                  |
| **Breached** | The clock is over its target.                                           |
| **Met**      | The clock stopped inside its target.                                    |
| **No SLA**   | The ticket has no SLA, for example because its department has SLAs off. |

A ticket's state is the worse state of its two clocks. A stopped clock is never at risk. It shows as breached only if it was already over its target.

## Where SLAs show

### Ticket details

In the ticket details, the **Properties** section has two rows, **Response SLA** and **Resolution SLA**. Each row shows the time left or the result, with an icon for the clock's state, for example:

- "Due in 3h 20m"
- "Clock stopped, 2h left" while the ticket is paused or waits for the requestor
- "Breached 6m ago"
- "Missed by 20m" for a clock that stopped over its target
- "Met"

Hover over **Response SLA** or **Resolution SLA** to see how the clock was measured. **Response SLA** shows when the first response came. **Resolution SLA** shows the active time so far, and the time that the clock stopped while the ticket was paused or waiting for a response. Both show the target for the ticket's priority.

*Product example: A ticket's details in the Risotto dashboard, with Response SLA met and Resolution SLA due in 3h 20m.*

### Ticket list

In [**Tickets > All**](https://www.tryrisotto.com/docs/dashboard/tickets/all), the **SLA** column shows the ticket's state as a badge. Hover over the badge to see each clock, for example "At risk, due in 6m", and its due time. Sort by the **SLA** column to see the next deadline first.

You can filter the list on **SLA**, **Response SLA**, or **Resolution SLA**. Each filter takes one or more states.

*Product example: Tickets in the Risotto dashboard with the SLA column: Breached, At risk, On track, Met, and no SLA.*

### Inbox

In the [Inbox](https://www.tryrisotto.com/docs/dashboard/tickets/inbox), the **SLA attention** section is above the other sections. It shows open tickets with a clock that is breached or at risk, breached tickets first. The section includes unassigned tickets. Each row tells you which clock needs attention, for example "Resolution SLA at risk: 6m left of 30m".

To sort the inbox by deadline, click **Filter** and set **Sort by** to **SLA**. Breached tickets come first, then the tickets with the nearest deadline.

*Product example: The Risotto inbox with the SLA attention section above Needs action and Waiting on others.*

The column, the filters, the inbox section, and the sort show only when a department in view has SLAs on.

### At-risk note

When a clock becomes at risk, Risotto adds an internal note to the ticket, for example:

> The response SLA is at risk: 14 minutes left of the 1 hour target.

Risotto checks the clocks every 3 minutes, so the note can come up to 3 minutes after the clock becomes at risk. The note is visible to your team only. Risotto does not send it to chat, email, or a synced ticketing system. The note moves the ticket to the top of the inbox when you sort by **Recent**. You cannot turn off the note.

## Limits

- SLAs use calendar time only. Business hours, time zones, and holidays are not supported.
- Risotto does not send an alert when a clock is breached. To find breached tickets, use the **SLA attention** section or the **SLA** filter.
- SLA data is not in the [MCP server](https://www.tryrisotto.com/docs/integrations/mcp-server), [webhooks](https://www.tryrisotto.com/docs/integrations/webhooks), or the CSV export.
- Targets are set for each department and priority. You cannot set a target for one category, requestor, or request source.

## Troubleshooting

### The SLAs page is missing from the department settings

SLAs are in early access and are not on for your organization. Contact
Risotto support.

### A ticket shows no SLA

The ticket's department has **Track SLAs** off, the ticket has no priority,
or the ticket is a duplicate. Turn on **Track SLAs** for the department, or
set a priority on the ticket.

### Old tickets show as breached after I turned on SLAs

Risotto measures every existing ticket from the time it was created. Resolve
or close tickets that are no longer active, or filter the list on recent
tickets.

### The response clock still runs after my team replied in Jira

A comment in a synced ticketing system or in the dashboard does not stop the
**Response** clock. A reply in the Slack thread, an escalation, or Risotto's
first reply stops it.

## Related

- [Ticket Priority](https://www.tryrisotto.com/docs/dashboard/settings/ticket-priority)
- [Departments](https://www.tryrisotto.com/docs/dashboard/settings/departments)
- [Ticket lifecycle](https://www.tryrisotto.com/docs/concepts/ticket-lifecycle)
- [Ticket Inbox](https://www.tryrisotto.com/docs/dashboard/tickets/all)

Source: https://www.tryrisotto.com/docs/dashboard/settings/slas
