> 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/checking-a-reserved-guest-in.md).
# Checking a Reserved Guest in
Guests can be checked in using two methods:
* **Through the table reservation screen:**
* In the Table Reservation screen, select the guest from the booking list in the left panel and click on the ellipsis (three dots) corresponding to the guest.
* Select **Seated from the pop-up window**.
#### From the TPOS Screen
* In TPOS, click the reserved table.
* A pop-up message will appear, prompting for a check-in.
* Click Yes to check in the table.
* Once the Guest is seated, the pop-up screen prompting reservation check-in is displayed. Click OK to proceed.
* Once Check-in is initiated, the reservation status color on the Table reservation screen changes.
#### To Customize the Reservation Statuses,
* **Go to POS>>Masters3 >> Outlet settings.**
* **Click Open file**
* Select **Main Menu**
* Select **All-day Dining** from the Outlet drop-down.
* Click on the colored boxes to open the color palette.
* Select the colors from the given palettes.
* **Save**
Once the guest is checked in, another pop-up message will appear, after which the KOT process can be initiated.
---
# 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/checking-a-reserved-guest-in.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)
* Select **Main Menu**
* Select **All-day Dining** from the Outlet drop-down.
* Click on the colored boxes to open the color palette.
* Select the colors from the given palettes.
* **Save** 
Once the guest is checked in, another pop-up message will appear, after which the KOT process can be initiated.
.png?alt=media)