A service level (SLA) tells Desk how fast you promise to answer. Every conversation that matches a policy gets its own clocks, you see them next to the conversation, and the right people hear about a miss once, not repeatedly. Open Desk settings → SLA and Desk settings → Queues. Owners and admins can change them; everyone else can read them.
Policies and the three clocks
A policy has up to three targets, each in minutes:
- First reply - from the first customer message to the first reply the customer can see.
- Next reply - from a customer writing again after you answered to your next reply.
- Resolution - from the first customer message to resolved. If the customer writes again after you resolved it, the conversation counts as reopened and a new resolution clock starts.
A policy applies to the channels you tick, or to every channel when none is ticked. Under the priority fields you can give urgent conversations shorter targets than normal ones. Switch a policy off to stop matching new conversations; clocks already running keep their targets.
What counts as a reply
Only a reply the customer can see stops a clock. An internal note never does, and neither does a reply the mail provider refused to deliver or that bounced.
Business hours and holidays
When a policy uses business hours and your open hours are on, targets count only the time you are open. A message that arrives on a Friday evening before a holiday Monday is due on the next open day after the holiday.
Under Holidays pick a country calendar and add your own closed dates, such as a company day. Holidays only matter while business hours are on. Daylight saving changes are handled for you.
When a clock pauses
A clock pauses while a conversation waits on the customer, while it is snoozed, and while the customer's mailbox has answered one of your replies with an automatic reply such as an out-of-office. That automatic reply is noted on the conversation, does not count as the customer writing back and does not reopen a resolved conversation. The clocks run again as soon as the customer writes for real, or after 72 hours. The conversation shows a short note saying why. It resumes with the time that was left when the customer replies or the snooze ends, so waiting on them never costs you time.
Escalation rules
An escalation rule acts on a clock that is at risk or late. Under Run choose a warning (set At % of the target to a value from 10 to 99, for example 80) or a missed target. Tick the clocks it applies to, or none for all of them, and pick what happens:
- Reassign to a teammate.
- Move to queue.
- Set priority to a higher level.
- Notify by email one or more teammates.
Each rule runs once per clock, and a missed target produces one alert, not one per check.
Queues and round robin
A queue is a pool of agents. A routing rule can send new conversations into a queue, and Desk hands them out:
Under Hand out by choose:
- Round robin - in turn, skipping anyone who is away.
- Least loaded - to the agent with the fewest open conversations.
Set Open limit per agent to stop handing a person more than that many open conversations. If nobody in the queue is available, the conversation stays unassigned in the queue instead of waiting on someone who is away.
Away status
Under Desk settings → Queues you can mark yourself away, optionally with a Back on time that ends the absence by itself. While you are away, new conversations skip you. Conversations you already own stay yours.
From the API and agents
Everything on this page is also available through the REST API (/api/v1/desk/sla, /api/v1/desk/queues) and the MCP tools get_desk_sla_settings, save_desk_sla_policy, set_desk_holidays, save_desk_escalation_rule, save_desk_queue and set_desk_availability. See the API reference.
Next
- Business hours and reports → - open hours, reports and the weekly email
- Routing rules → - send conversations into a queue
