> For the complete documentation index, see [llms.txt](https://tutorials.kuasa.io/getting-started/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tutorials.kuasa.io/getting-started/kuasa-appointment/appointment/how-to-setup-availability.md).
# How to Setup Availability
1. For this part, you need to plan in advance to set the start date and the end date to simplify your schedule and the clients.
2. For this part, you can plan if you want your appointment form to open a few days after the start date. In this section there are 2 different things namely;
* **Calendar days**: 7 days (including Saturday and Sunday)
* **Weekdays**: 5 days (excluding Saturday and Sunday)
3. In this section, you need to set the frequency of time slots available for the client.
4. For this part, you need to set how long your appointment will last. For example, for the whole you have scheduled for 7 hours to meet the client then you need to set it to 7 hours.
5. For this part, you need to set according to your schedule what days are available to meet the client.
6. For this part, you are given some time to prepare or finish the booked event.
---
# 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://tutorials.kuasa.io/getting-started/kuasa-appointment/appointment/how-to-setup-availability.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.
