> 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 displays all information regarding a certain available appointment that is displayed from information found in the database.
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 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/book-appointment-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.
