> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/feature-templates/appointment-booking/time-slots-screen.md).
# Time Slots Screen
The Time Slots Screen showcases all available appointments associated with a particular coach.
Once a user selects a coach they are interested in booking an appointment with, they will be taken to the Time Slots Screen. This screen displays all the open appointments that are available to book in the future.
This screen is similar to other screens in the template that have lists. It does, however, contain a custom filter.
Here’s what this filter means:
* This list is a list of all appointments that are offered by the “Current User.” In other words, the appointments offered by the coach that the user picked from the list on the ‘Coaches’ Screen.
* The list is filtered to only display appointments where BOOKED = FALSE or where the appointment does not show as booked in the database.
* AND the Date & Time for the appointments shown must be after the CURRENT TIME, as in, the time that the user is looking at the list.
⚡ **List Actions**
* Link Action to ‘Book Appointment’ Screen
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.adalo.com/feature-templates/appointment-booking/time-slots-screen.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
