> 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/point-of-sale/point-of-sale-module/pos-transactions/table-reservation/creating-a-new-table-reservation.md).
# Creating a New Table Reservation
1. If it is a multi-property company, you can select the desired property or company from the options provided in the drop-down list before managing reservations.
2. After selecting the property, choose the desired outlet from the Outlet dropdown list to manage reservations for that specific location. The system displays only those outlets that are enabled with Table reservations within this field.
3. After selecting the outlet, choose the desired session from the Session Selector to view and manage reservations for that session.
4. There are two ways to create a booking.
* By clicking and dragging on the desired place on the table or
* By clicking the (+) icon in the left panel.
5. Wincloud requires the mandatory client details and their status before finalizing the booking. The user is directed to the booking screen upon dragging or clicking the plus icon.
* The outlet name, session, time, and date are automatically populated. However, you can make amendments to the session, time/ duration, and date from the booking screen.
* The pax is shown as one by default, and the user needs to make the necessary changes.
* Status can be given as Confirmed or waiting list.
* Click on the **View Table button** to view the available tables.
* Select the number of tables according to the number of guests. Each table shows the default seating capacity. The pax will be displayed in the booking screen once tables are selected.
*In this example, the number of guests is 5, and the user has selected two tables, each with a default capacity of 4 guests. This is because, by default, each table is set to accommodate four people. user, with each table’s pax as 4.*
* Complete the booking by filling in guest details like mobile number, Guest name, and title.
* Select the guest status from the dropdown menu. The options are populated from the front office data.
* If there are any notes, post them under the instruction field.
* Save the booking. A booking confirmation message pops up to indicate a successful booking with table numbers, pax, and date.
* An SMS/WhatsApp message is sent to the guest confirming their booking.
* Booking confirmations can be integrated with both **SMS and WhatsApp**, according to the client’s preference.
* *The default confirmation setting is set to WhatsApp.*
6. Once the reservation is booked, the left panel of the table reservation screen displays the status of the booking in real time as:
‘Reserved for Mr. Praveen Kumar, at 1 PM, Pax 05, two tables.’
---
# 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/point-of-sale/point-of-sale-module/pos-transactions/table-reservation/creating-a-new-table-reservation.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)