> 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-frontdesk/faq-on-front-desk/how-to-change-the-guest-room.md).

# How to change the Guest Room?

To change a guest's room, you can use the dedicated Change Room menu or the interactive Calendar screen.

**Method 1: Via the Change Room Menu**

This is the standard procedure for moving a guest who is already in-house:

1. Navigate to the **Front Desk Main Menu** and click on **Front Desk > Change Room** Menu.
2. Select the specific guest for whom you want to change the room in the Guest Name option.
3. Choose the destination **Room no.** to which the guest would like to move.
4. Enter the reason for the move in the Narration field.
5. Click **Save** to complete the process. A pop-up message will appear confirming the change was successful.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-86268eb8873e97b93fea86a36d4f95210b23ef1b%2Fimage%20(1390).png?alt=media" alt=""><figcaption></figcaption></figure>

**Method 2: Via the Calendar (Room Chart)**

You can also perform a room change visually through the room chart:

1\. Go to the **Front Office** module and select **Queries > Calendar**.

2\. Locate the guest on the chart and simply drag and drop your cursor to move the guest from one room number to another.

**Monitoring Room Changes**

If you need to review room moves that have occurred over a specific period, you can use the Guest Shift Rooms report. This report can be generated as a Reason Summary to show the direct number of shifts and their associated reasons, or as a detailed report for in-depth information on each shift.


---

# 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-frontdesk/faq-on-front-desk/how-to-change-the-guest-room.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.
