> For the complete documentation index, see [llms.txt](https://www.usemotion.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.usemotion.com/help/time-management/booking-links/concept-booking-links/best-practices.md).

# Best Practices

#### Best Practices for Booking Links

| Best Practice              | Why It Matters                                            | Example                                                              |
| -------------------------- | --------------------------------------------------------- | -------------------------------------------------------------------- |
| **Set clear availability** | Prevents surprise bookings outside your working hours.    | Limit Schedule to Working day, 9–5.                                  |
| **Use buffers**            | Protects your focus and gives time to prepare or recover. | Add a 15-minute buffer before and after meetings.                    |
| **Limit daily meetings**   | Prevents meeting overload.                                | Cap at 4 external meetings per day.                                  |
| **Customize details**      | Gives invitees context and reduces back-and-forth.        | Add agenda fields or attendee requirements in the booking form.      |
| **Share wisely**           | Make your link easy to find but controlled.               | Add it to your email signature, or share 1:1 for specific use cases. |


---

# 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://www.usemotion.com/help/time-management/booking-links/concept-booking-links/best-practices.md?ask=<question>&goal=<user_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.