SLAs and business hours
Business hours
Set the time zone, the hours for each weekday (several windows a day if you need them) and holidays (one off or every year). Without business hours, SLAs count calendar time.
Policies
A policy has conditions (like priority or brand) and targets per priority, in minutes:
- First response: from creation to the first public reply by an agent or the AI agent. Automatic acknowledgements do not count.
- Next reply: from a customer’s follow up to the next public reply.
- Resolution: from creation to solved.
The first active policy whose conditions match applies. Targets are recomputed from timestamps whenever the ticket changes, so a priority change moves the clocks.
Pauses
The resolution clock stops while a ticket is pending or on hold (waiting on the customer or someone else), and those business minutes are added back when it resumes.
Warnings, breaches and escalation
The assignee is warned before a target is due (30 minutes by default). When a target is missed, the breach is recorded once, a note is added, the assignee (or the group’s supervisors) is notified, triggers run with the sla_breached event, a sla.breached webhook is sent, and the policy can raise the priority or move the ticket to another group.
Reporting
Reports show first response and resolution compliance and the number of breached tickets.