# Service levels: answer and resolve requests on time

> Run a table as a service desk: say what each status means and when your team works, and set service levels such as "first response within 2 working hours for High". Each gets a due time and an On track, At risk, Breached or Met field, kept up to date for you.

Source: https://artavolo.com/page/service-levels

A service level (an SLA) is a promise about time: *we answer every High request within 2 working hours*, *we resolve every request within 3 working days*. Artavolo keeps a clock for each promise on each request, counts only your working hours, and shows where each one stands in two ordinary fields, so your views, boards, client portals and automations can use them.

## Set up the service desk

1. In the table of requests, open the views menu and choose the **Service desk** button beside a view. Only the base's owners see it.
2. **Statuses**: pick the status field and say what each option means: Open, Waiting on us, Waiting on the client, Resolved or Closed. Artavolo guesses from the names. Pick the priority field and the assignee field if the table has them.
3. **Working hours**: your time zone, the hours of each day, and closed days such as holidays.
4. **Service levels**: two are ready, Time to first response and Time to resolution. Change their targets, in hours, for each priority, or add your own (up to six).
5. Choose **Turn on the service desk**. Tick **Also start the clocks of open requests now** to include the requests you already have.

Each service level gets two fields: **<name> due**, the date and time it is due in your time zone, and **<name>**, which says On track, At risk, Paused, Met or Breached. Artavolo writes them; people cannot change them by hand.

## How the clocks run

- A clock starts when a request is created, or, if you choose, when its status becomes one you pick.
- It counts only working hours, unless you set it to count around the clock.
- It pauses while the request waits on the client, and goes on with the time left when the status moves on.
- Time to first response stops at the team's first public reply in the record's comments, or a reply by e-mail. An internal note, or a comment by the client, does not stop it.
- Resolving or closing a request stops the clocks: Met if it was in time, Breached if not. Reopening it goes on from where it stopped.
- Changing a request's priority moves its due time to the new target.
- At the share of the time you choose (75% at first) it turns At risk, and past its due time, Breached. The assignee is told both times, in their notifications and on their phone; with no assignee, the person who set up the desk is.

## Use them

- Sort a grid by *Time to resolution due* to work on what is due first, or filter it to Breached.
- Colour a kanban board's cards by *Time to first response*.
- Start an [automation](https://artavolo.com/page/automations) when a service level becomes Breached: tell the team lead, post in a chat channel, or raise the priority.
- Count Met and Breached in a chart for a report on how you did.
- Your clients see them only if you add the fields to their [portal](https://artavolo.com/page/client-portals) page.

## Good to know

- **Turn off** stops the clocks. The fields stay in the table with their last values; turning the desk on again uses them again.
- Changing a target or the working hours works out the running clocks again.

## Related

- [Client portals](https://artavolo.com/page/client-portals)
- [Automations](https://artavolo.com/page/automations)
