> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/faq/faq-generale/minimum-de-participants-a-la-reservation-pourquoi-ce-nest-pas-possible.md). # Minimum number of participants required for booking: why is it not possible? Some service providers would like their activities to be bookable online only for a certain number of participants (for example, a minimum of 4 people). This request, while understandable from an operational perspective, is not compatible with best practices for online sales. ### ❌ An obstacle to booking If you prevent bookings before a group of 4 people arrives, you risk **blocking sales completely**. This is because: * Individuals will never be able to book alone or in pairs, * They will not know if there are already any registered people, * And so they won’t dare to book… even if a session is almost full! 👉 Result: **no session is triggered**, and filling becomes much more difficult. ### ✅ It is better to capture the customer, even if it means rescheduling In **online sales**, it's better to **take a reservation, even a one-time one**, than to lose it due to a minimum number of participants. A session can always be: * **Confirmed** if other customers are added, * **Rescheduled or canceled** with a clear and professional message. This allows you to **start group building**, instead of waiting for an entire group to spontaneously show up. ### 🛠️ Tip: the "Minimum Capacity" order data A good practice is to create a **custom order data**, for example titled **"Minimum Capacity"**. This allows you to inform the customer at the time of booking: > **This session requires a minimum of X participants. If this threshold is not reached, it may be rescheduled.** It’s a **transparent** way to secure the **customer relationship** without blocking the sale. ### 🚀 An effective alternative: potential planning To go further and maximize your chances of filling your sessions without blocking sales, we recommend using **potential planning** (or **"AI planning"**). This system allows: * To **automatically open a session** upon first booking, * To **favorite this session** in online display, * And to **block competing sales** in this slot if you wish. This **greatly increases** the chances of getting 3 or 4 participants together, without blocking the sale at the base. ### 📣 Need help setting up your schedule? Our support team can guide you step by step. Contact us at or via chat. --- # 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://docs.yoplanning.support/en/faq/faq-generale/minimum-de-participants-a-la-reservation-pourquoi-ce-nest-pas-possible.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.