> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/booking-links/my-booking-page.md).
# My booking page
Give visitors one page where they can choose the meeting that suits them. Your booking page brings together up to six of your personal links in the current workspace.
## Set up your page
1. Open **Booking links → My booking page**.
2. Enter a **Greeting** and **Description** to introduce the meetings you offer.
3. Choose your **Profile URL**. This address is separate from your username and individual booking-link URLs.
4. Under **Meeting links**, select the personal links to include. Drag them into order, or focus a drag handle and use the up and down arrow keys.
5. Review the desktop and mobile previews, then click **Save profile**.
6. Turn on **Publish**, then use **Copy link** to share your page.
Create a [personal link](/booking-links/create-a-booking-link.md) first if the list is empty. You can include your own available personal links from this workspace. Group links and routers do not appear in this list.
Choose the meetings to include and check the live preview before saving.
## Choose the appearance
Choose **Cards**, **List**, or **Spotlight** under **Page style**, then select a background pattern. Each selected meeting can have an icon or an image from the workspace's [Asset library](/settings/workspace-settings/asset-library.md). Star one meeting to recommend it and set its label.
Your page uses the workspace's published default [booking theme](/settings/workspace-settings/branding.md) for branding. **Color mode** can follow the workspace default or use **Light**, **Dark**, or **Visitor**. Visitor follows the guest's device. Booking pages opened from this profile follow its color mode.
Guests choose a meeting before checking its current availability. Each link keeps its own event type, questions, CRM settings, and booking appearance. Adding a link to your page does not change those settings.
## Save, publish, and make private
**Save profile** saves your content and appearance. If your page is already published, those saved changes become visible to visitors. **View profile** opens the published page, or your saved profile while it is private; save first to include your latest edits.
The **Publish** switch changes public access immediately. On an existing profile, it does not save other unsaved edits. At least one available meeting link is needed before publishing.
Turn off **Publish** to make the profile private. Your individual booking links remain available separately. Removing a link from the profile only removes its listing; deleting that link also removes it from the public profile. The profile becomes unavailable if you leave the workspace.
## Change the address
Each profile can reserve up to three addresses, including its current one. Previous addresses redirect to the current address while the profile is published. After using all three, keep your current address or reuse a previous one.
Each workspace membership has its own profile. Check the workspace before editing or sharing yours.
---
# 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.distro.so/booking-links/my-booking-page.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.
