---
title: "Configure Ticketing SLAs and Business Hours"
description: "Set response and resolution targets for tickets with SLA policies and business-hour schedules, including holidays, pause rules, warnings, policy order, and escalation workflows."
url: https://help.aesthetixcrm.com/en/articles/2258-configure-ticketing-slas-and-business-hours
collection: "Ticketing Setup and Email"
updated: 2026-11-20
language: en
---

# Configure Ticketing SLAs and Business Hours

Set response and resolution targets for tickets with SLA policies and business-hour schedules, including holidays, pause rules, warnings, policy order, and escalation workflows.

Service-level agreements (SLAs) define how quickly your team should reply to, assign, resolve, or move a ticket to a milestone. Business-hour schedules decide when a business-hours SLA clock runs, including time zone, weekly hours, and holidays. Both are under **Tickets > Settings**, in the **SLA** and **Business hours** pages.

This guide covers Ticketing SLAs only. For conversation response targets in the Inbox, see Inbox SLAs and Performance.

## Before you begin

Open **Tickets > Settings** as an administrator. Decide which requests need different targets, for example post-treatment questions versus general inquiries, and whether you measure time continuously or only while your practice is open. If you use business hours, create the schedule first and then select it in the SLA policy. Review your priorities, categories, and statuses before using them as policy conditions.

## Available targets

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p><strong>Target</strong></p></th><th colspan="1" rowspan="1"><p><strong>What it measures</strong></p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Time to first reply</strong></p></td><td colspan="1" rowspan="1"><p>From ticket creation to the first agent reply.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Time for next reply</strong></p></td><td colspan="1" rowspan="1"><p>From a customer message to the next agent reply.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Time to close</strong></p></td><td colspan="1" rowspan="1"><p>From ticket creation to closure.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Time to assign</strong></p></td><td colspan="1" rowspan="1"><p>From ticket creation to assignment to an agent.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Time to reach status</strong></p></td><td colspan="1" rowspan="1"><p>Time to reach a status milestone you select.</p></td></tr></tbody></table>

Enable only the targets you plan to track. A policy needs at least one target. Turn on **Different targets per priority** when urgency levels need different durations. A ticket's **due date** is a separate property: setting a due date does not replace an SLA policy. Internal notes do not count as a customer-facing reply for response targets.

## Create a business-hours schedule

1.  Open **Settings > Business hours**.
    
2.  Select **Create schedule**.
    
3.  Enter a name that identifies the team or pattern, such as "Front Desk Hours".
    
4.  Select the schedule's **Time zone**.
    
5.  Turn on the working days and set start and end times.
    
    ![](https://files.us.gleap.ai/pf/g/640067b236b432d4bc3c20bb-I0rsTdDTpgB10UrneyrN53bkOIX4q0Uutk9hxmm5M06bE6Ybqb2lt7Ag6NGAEiXuVi86D49SwiL.png?v=1&k=us1&s=api&e=1795348800&sig=k7c3yCWY9GqXk3O_t_Hr2HzjAMWf3vIgg1_guTvAl-g)
6.  Use **\+ Add hours** for split shifts, such as a morning and an afternoon block.
    
7.  Add holidays as needed, then select **Create schedule**.
    

The editor offers presets: **Weekdays 9-5**, **Open 24/7**, and **Copy Monday to weekdays**. Review the day-by-day hours before saving. Closed days pause the clock for any policy using the schedule.

### Add holidays

1.  Scroll to **Holidays** in the schedule editor.
    
2.  Select **Add holiday**, enter a name and start and end dates, and save the schedule. For a one-day closure, use the same date for both.
    
    ![](https://files.us.gleap.ai/pf/g/640067b236b432d4bc3c20bb-mhJDSfQBZQI7JJTrRzaNB1DNB5zlLhcTBjHAoi0iXmUXkcH7OwLFpiubksE6DVX3OkDFdKyJF0z.png?v=1&k=us1&s=api&e=1795348800&sig=qnfwBfNGhf8Amg0Lhk7fw7pecbQ5mnkExhEntbiF_Jc)
3.  Or use **Import public holidays** and review the resulting dates.
    

Holiday dates are whole days during which applicable SLA timers pause.

### Choose a default schedule

Select **Set as default** on the schedule to use when a business-hours policy does not name another one. The schedule list shows the default, weekly hours, holiday counts, and usage. You cannot delete the default schedule until you set another as default, so review affected policies first. You can keep several schedules, for example one for the front desk and one for the clinical team.

## Create an SLA policy

1.  Open **Settings > SLA** and select **Create SLA**.
    
2.  Enter the **Policy name** and an optional description.
    
3.  Under **Applies to**, choose Category and Priority values, or leave both as All for broad coverage.
    
4.  Use **Advanced filters** for other conditions such as status, subject, or assignee.
    
5.  Turn on at least one target and set its duration. For **Time to reach status**, choose the milestone status.
    
    ![](https://files.us.gleap.ai/pf/g/640067b236b432d4bc3c20bb-qc6OkJdr5glnzlsSG8AfDUfj1QgwMj3cugAwNqOD0joi64Z4ZBcGF4dQH7eZRrO1MhmNr5wMEsR.png?v=1&k=us1&s=api&e=1795348800&sig=1CHvDOH0gz9GccJsCErq78hCn9EC26Yxk4r26yB17UM)
6.  Choose the clock settings (below).
    
7.  Review the policy summary and select **Create policy**.
    

For example, create one policy for Urgent post-treatment questions with a short first-reply target, and a broader policy for everything else. Set durations that match your real service commitments.

A ticket with no priority or category will not match a policy that requires one.

## Choose when the clock runs

In the policy's **Clock** section:

-   **24 / 7** counts elapsed time continuously.
    
-   **Business hours** counts only time inside the selected schedule. Review the shown hours, time zone, and holidays.
    
-   **Pause when** lets you choose statuses that pause the clock, such as Waiting on Customer.
    
-   **Warn at** sets when the ticket enters the **Due soon** state before a breach.
    
    ![](https://files.us.gleap.ai/pf/g/640067b236b432d4bc3c20bb-0e6doAnVU3efpTBBcAYxsMv1NAJ2LV4vEZB8PvQVoI9FYqCs5pmoiK2rjrFNEtqmaybBKEiEF5L.png?v=1&k=us1&s=api&e=1795348800&sig=lgfUi7ZnBnaAgXrvHh7jzmXMfW0BON9BiS92RZ4wB7E)

Naming a status "Waiting on Customer" does not select it as a pause status. Add it under **Pause when** if that fits your process.

### Business-hours example

Say your schedule is Monday to Friday, 9:00 to 17:00, with no holidays, and the first-reply target is four business hours. A ticket created Friday at 16:00 uses one hour on Friday and three on Monday, so the target is Monday at 12:00 in the schedule's time zone, assuming no pause applies. With a 24/7 clock, the same four-hour target would fall Friday at 20:00.

## Arrange and maintain policies

-   Policies are evaluated in order, and the first matching policy applies. Put specific policies (such as Urgent) above broad ones.
    
-   The **Default Policy** stays last and covers everything else. You can edit or disable it but not delete it.
    
-   Use row controls to enable, disable, duplicate, or remove other policies. Review conditions after duplicating.
    
-   Changing conditions, schedules, or durations can change service expectations on open work, so review the ticket targets afterward.
    

## Monitor SLA progress

Open a ticket and expand **SLA details** in the right panel to see the applied policy and target information. The ticket list also provides SLA fields and metrics (such as **SLA breached** and **Due soon**).

![](https://files.us.gleap.ai/pf/g/640067b236b432d4bc3c20bb-psSS8KZUBB6kvG6iMBXLOVwP4TLl8E8giZXHkbFMCBfI24p8rbiZEPZ7hWKm8XNs00EZhZQd12P.png?v=1&k=us1&s=api&e=1795348800&sig=QZWEWfKU_KUsTKp1xAp5thJ-tBetLfTC-dsaRu3e--k)

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p><strong>State</strong></p></th><th colspan="1" rowspan="1"><p><strong>Meaning</strong></p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>No SLA</strong></p></td><td colspan="1" rowspan="1"><p>No applicable SLA is attached.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>On track</strong></p></td><td colspan="1" rowspan="1"><p>The target is within its allowed time.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Due soon</strong></p></td><td colspan="1" rowspan="1"><p>The warning threshold has been reached.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Breached</strong></p></td><td colspan="1" rowspan="1"><p>A tracked target exceeded its allowed time.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Met</strong></p></td><td colspan="1" rowspan="1"><p>The target was satisfied.</p></td></tr></tbody></table>

## Escalate with workflows

An SLA target alone does not decide who gets notified. Use the **SLA Warning** and **SLA Breached** workflow triggers to alert the right person, for example a practice manager. See Automate Ticketing with Workflows.

## Troubleshooting

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p><strong>Issue</strong></p></th><th colspan="1" rowspan="1"><p><strong>What to check</strong></p></th></tr><tr><td colspan="1" rowspan="1"><p>The expected policy did not apply</p></td><td colspan="1" rowspan="1"><p>The ticket's properties, the policy conditions, whether it is enabled, and the evaluation order.</p></td></tr><tr><td colspan="1" rowspan="1"><p>The clock runs outside office hours</p></td><td colspan="1" rowspan="1"><p>Confirm the policy uses <strong>Business hours</strong>, with the right schedule and time zone.</p></td></tr><tr><td colspan="1" rowspan="1"><p>The clock pauses unexpectedly</p></td><td colspan="1" rowspan="1"><p>Closed days, holidays, and <strong>Pause when</strong> statuses.</p></td></tr><tr><td colspan="1" rowspan="1"><p>An urgent ticket uses a general policy</p></td><td colspan="1" rowspan="1"><p>Move the specific policy above the broader one and review its conditions.</p></td></tr><tr><td colspan="1" rowspan="1"><p>A breach did not notify anyone</p></td><td colspan="1" rowspan="1"><p>The workflow trigger, filters, publication state, and notification action.</p></td></tr><tr><td colspan="1" rowspan="1"><p>A policy cannot be created</p></td><td colspan="1" rowspan="1"><p>Enter a name, turn on a target, complete its inputs, and fix validation messages.</p></td></tr></tbody></table>

## Frequently Asked Questions

**Can I create more than one business-hours schedule?**

Yes. Name each for its use and select the right one in each policy.

**Do holidays affect 24/7 policies?**

No. Holiday pauses belong to business-hours schedules. Choose **Business hours** for a policy that should follow holidays.

**Can I stop the clock while waiting for a patient?**

Yes. Add the waiting status under **Pause when** in the policy.

**Can I set different targets for different priorities?**

Yes. Use separate policies matched by priority, or turn on **Different targets per priority**.

**What is the difference between a due date and an SLA target?**

A due date is a date recorded on the ticket. SLA targets track specific service commitments such as first reply.

**Can I delete the Default Policy?**

No. You can edit or disable it.

**Does resolving a ticket stop the SLA clock?**

Yes, if the status you use has **This status means the ticket is resolved** turned on.

**Who is notified when an SLA is breached?**

Only who you configure in a workflow using the SLA Breached or SLA Warning trigger.
