> 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
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 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://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 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.