> For the complete documentation index, see [llms.txt](https://docs.wrangle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wrangle.io/account-administration/working-hours.md).

# Working Hours

Whether your team has 24/7 coverage, a standard 9-5, or a four-day workweek, Wrangle lets you set your own working hours. Once working hours are set, Wrangle will exclude off hours from your response time and resolution time calculations. Additionally, Wrangle will not send any late reminders outside of working hours. \
\
Any [account admin](/account-administration/account-admins.md) can set your workspace's working hours from the Admin Settings [here](https://slack.wrangle.io/settings/working-hours).

<figure><img src="/files/TlSav7PcuRWCuwsRO9T3" alt="" width="563"><figcaption></figcaption></figure>

You can choose the timezone, days of the week, and times of day that your team is available.&#x20;

### Working Hours by Team (User schedules)

Have teams in different timezones, or people working different schedules?  Outside of the workspace-level default working hours, you can also set as many user or team-specific schedules as you want. &#x20;

<figure><img src="/files/L2aOdhwhhBmUCAltyFTE" alt="" width="563"><figcaption></figcaption></figure>

#### How to set up a user schedule

Go to **Admin Settings** -> **Working Hours**.  Make sure to go to the **By Team** tab.  Click the **Add User Schedule** button.  Notice in the pop-up modal that there are two tabs you will want to fill out: **Schedule Settings** and **Assignments**. &#x20;

<figure><img src="/files/RGodJaILrPYewa8252mh" alt="" width="375"><figcaption></figcaption></figure>

Enter your user's or team's Schedule Name, and then in **Schedule Settings** fill out the timezone, days, and working hours. &#x20;

On the **Assignments** tab, assign one or more users or user groups to the schedule.  A specific user or user group can only be assigned to one team schedule, although a user can be in multiple user groups that each have different team schedules. &#x20;

#### How schedules are applied

* **Direct user assignment** takes priority over user group assignments
* If a user belongs to **multiple user groups** with different schedules, their effective hours combine both schedules
* Each user can be directly assigned to only **one** schedule
* Each user group can be assigned to only **one** schedule
* **Holidays** are set at the workspace level and apply to all users, including those on team schedules

#### What team schedules affect

Team schedules are used for:

* **Auto-assignment** — tickets assign only to agents currently within their working hours
* **Auto-responder** — the [auto-responder](/tickets/setting-up-your-inbox/ticket-lifecycle/auto-responder.md) sends only when no inbox agents are within their working hours
* **Agent performance reports** — response and assignment time metrics respect each agent's schedule

To see which agents on an inbox have custom schedules, open Inbox Settings and select the **Working Hours** tab:

<figure><img src="/files/ApfZ1OPf5pzJsQhJuIen" alt="" width="375"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.wrangle.io/account-administration/working-hours.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
