Each service commits to two delays: the first response and the resolution. The help desk counts them in business hours, shows them to the requester, reminds the agent of the deadline and escalates a missed one. This article explains how to set and read them.
Before you start #
- You need the Administer the help center right (Execute level) to set a service’s hours and commitments.
- Commitments are shown on each ticket, to agents and to the requester.
Service hours #
On the service page (Settings › Help center › Services), the Service hours section says when the delays run:
- one or more slots per day of the week (a day without a slot is Closed);
- the Reference office (public holidays): its public holidays do not count; None: no public holiday;
- the Time zone: the office’s or the company’s.

The commitment grid #
The Service commitments section sets, for each priority, the First response delay and the Resolution delay, in business hours. An empty field: no commitment on that delay. As long as a row has not been changed, it reads “Standard grid” and follows the default grid:
| Priority | First response | Resolution |
|---|---|---|
| Critical | 1 h | 4 h |
| High | 2 h | 8 h |
| Normal | 4 h | 24 h |
| Low | 8 h | 40 h |

In the same section:
- “Waiting for a third party” stops the resolution clock: tick it if waiting for a supplier or another service should not count against the team. “Waiting for the requester” always stops it.
- Escalation of a missed deadline: by default, The service managers. You can choose a group instead: its members who hold the agent right receive the escalation and read the service’s tickets, without acting on them (escalation readers). Without a manager, the escalation goes to the service’s agents.
The deadline reminder #
In Settings › Help center › Ticket lifecycle, Deadline reminder at (% of the delay) sets when the reminder goes out: once this share of the delay has elapsed (75% by default, between 10 and 95%), the agent holding the ticket, otherwise the service’s agents, gets a reminder in the notification bell and by e-mail. The “When a deadline approaches” rules run at the same time; the escalation runs the “When a deadline is missed” rules.

Read a ticket’s commitments #
The Service commitments card of the ticket page shows, for each delay, the deadline and its state: On time, Due soon, Overdue, Paused, then Met or Missed (with how early or late, in business hours). It also says when the reminder and the escalation were sent.

The requester sees the expected reply date in their request, and “Paused” when the team is waiting for them.
Good to know #
- Delays are fixed when the ticket is filed: changing a service’s grid moves no deadline already announced.
- Only a priority requalification, a transfer to another service and linking the requester to an organisation under contract recalculate the deadlines, from the filing date and with the grid of the moment; the timeline tells the requester.
- A customer organisation under contract has its own delays, which take precedence over this grid: see The help desk and the CRM.
- The first response never stops: it is an agent’s first public reply. Neither an internal note, nor simply taking the ticket, nor a rule’s automatic reply counts (see Help desk automations: rules and macros).
- During a pause, the resolution deadline is suspended: no reminder, no escalation. When work resumes, it moves by the business time spent paused. Time spent “Resolved” does not count if the requester reopens.
- A ticket waiting for approval has no reminder or escalation; once approved, its delays run from the decision.
- A ticket attached to a major incident has its deadlines paused: no reminder or escalation, first response included. Once detached, its resolution deadline restarts, shifted by the time spent paused; the first-response deadline is not shifted (see Major incidents and problems).
- The resolution deadline of a service catalogue request covers those of its tasks: it is extended to the latest one (see The service catalogue).
- Results (met or missed) feed the reporting: see Satisfaction and reporting.
