> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/front-office-module/fo-masters/faq-on-masters/how-to-configure-overbooking-parameters-for-room-type.md).

# How to configure overbooking parameters for room type

**How do I configure overbooking parameters for a room type?**

To configure **overbooking parameters** for a specific **room type**, use the **Room Type Master** in the **Front Office** module.

#### **Steps to Configure Overbooking**

1. **Navigate to the Menu:**\
   Go to **FRONT OFFICE → MASTERS → ROOMS → ROOM TYPE**.\
   Click **New** to create a new room type or select an existing room type to modify.
2. **Enable Overbooking:**\
   Select the **Overbooking** checkbox to allow the system to accept reservations beyond the available physical rooms for that room category.
3. **Set the Overbooking Percentage:**\
   Enter the **overbooking percentage** that will be permitted for the room type.
4. **Select the System Parameter:**\
   Choose the appropriate **system parameter** that determines how the overbooking logic is applied.
5. **Define Allotment Limits (Optional):**\
   If required, specify the **maximum allotted persons per room** to apply additional occupancy restrictions.
6. **Save the Configuration:**\
   Click the **Save** icon to apply the overbooking settings.

While configuring the room type, you can also define the **maximum occupancy** by setting separate limits for **adults** and **children**.


---

# 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.rbsgo.com/front-office-module/fo-masters/faq-on-masters/how-to-configure-overbooking-parameters-for-room-type.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.