> 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/book-appointment-screen.md).
# Book Appointment Screen
The Book Appointment Screen will allow your users to book an appointment and displays all relevant information that a user would like to know before deciding to book: from the description of the class to related images, dates, and more.
All information that is shown on this screen is connected to properties found in the appointments database. If properties are removed from the database, that may impact how the information shows up on this screen.
## New Components
Most components have already been covered in detail on other screens, however, there is a BOOK Button on this screen.
This button is how someone will register for the available appointment. This button will only show IF the appointment has not yet been booked by another user (Current Appointment > Booked > is false).
⚡ **Book Button Actions**
* Update Appointment
* Booked is TRUE
* Guest is Logged In User
* Link Action to ‘Success’ 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/book-appointment-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.