> For the complete documentation index, see [llms.txt](https://bookit-2.gitbook.io/bookit-template-bubble/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bookit-2.gitbook.io/bookit-template-bubble/basics/markdown.md).

# Using Bookit (Core Features)

This section covers how to use the core features of the Bookit template in real-world scenarios.

Whether you're managing reservations, updating your online menu, or operating from a tablet during service, this part of the documentation will guide you through every functional aspect — with step-by-step instructions, visual examples, and tips to customize Bookit to your workflow.

You'll learn how to:

* Handle reservation and privatisation requests
* Manage your team and client base
* Configure your establishment details and branding
* Keep your online menu up to date
* Use the operational calendar efficiently

Each topic is organized into its own dedicated subpage, focusing on **actions**, **workflows**, and **best practices**.

Let’s dive in.


---

# 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://bookit-2.gitbook.io/bookit-template-bubble/basics/markdown.md?ask=<question>&goal=<endgoal>
```

`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.