> 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/banquet/banquet-module/transaction/block.md).
# Block
The **Block** feature is used to temporarily reserve or block a venue for specific purposes such as a **Wait List** or **Maintenance Block**. This helps prevent the venue from being booked for other reservations during the selected date and session.
## Steps to Create a Venue Block
Step 1: Go to the **Banquet module** in the system dashboard.
1. Click on **Block** option available under the **Transactions** Menu.
Step 2: Click **New** button , a form will open.
* Choose the **Block Type** as:
* *Wait List Block* (for tentative bookings), or
* *Maintenance Block* (for blocking venue due to maintenance or non-availability)
* Fill in the required details carefully:
* **Guest Name** – Name of the guest or event organiser
* **Date** – Scheduled date of the block
* **Session** – Time slot (e.g., Morning / Evening / Full Day)
* **Venue** – Select the required venue/location
* **Plan** – Applicable plan or package details
* **Guaranteed Pax** – Confirmed number of participants
* **Expected Pax** – Estimated number of participants
* **Function Type** – Type of event (e.g., Wedding, Meeting, Conference)
* **Business Source** – Source of booking (e.g., Direct, Agent, Corporate)
* **Market Segment** – Category of customer (e.g., Corporate, Leisure, Wedding)
Ensure all information is entered accurately to avoid booking conflicts.
Step 3: After verifying all entered details, click on the **Save** button.
* The system will create and register the Block successfully.
---
# 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/banquet/banquet-module/transaction/block.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.
