> For the complete documentation index, see [llms.txt](https://docs.keeping.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeping.com/help/reporting-and-analytics/classic-reports/setting-work-schedules.md).

# Setting work schedules

In order to more accurately calculate first response time, you can set the working hours for individual team members. Navigate to the[ agents area](https://app.keeping.com/users) in Keeping's settings, and choose the agent you'd like to set a schedule for. Note that only a Keeping admin can adjust an agents work schedule.

{% hint style="info" %}
An agent's working schedule only applies to calculations in Classic Reports.  Advanced Reports use the organizations business hours.
{% endhint %}

![Set your agents' work schedules for more accurate reporting.](/files/a9f4qOgObGEtTrQGqAFC)


---

# 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.keeping.com/help/reporting-and-analytics/classic-reports/setting-work-schedules.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.