> 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/~/revisions/tkMgcRwylvf1GG81MVcV/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](/~/revisions/tkMgcRwylvf1GG81MVcV/account-administration/account-admins.md) can set your workspace's working hours from the Admin Settings [here](https://slack.wrangle.io/settings/working-hours).
You can choose the timezone, days of the week, and times of day that your team is available.
{% hint style="info" %}
If you have a distributed team, consider setting your working hours to cover all regions' schedules. \
\
For example, let's assume half of your team is in New York, the other half is in California, and everyone works 9AM-5PM in their respective time zone. Set your working hours as 9AM-8PM Eastern Time to ensure coverage for both locations while still excluding hours where neither team is active.
{% endhint %}
---
# 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/~/revisions/tkMgcRwylvf1GG81MVcV/account-administration/working-hours.md?ask=&goal=
```
`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.