> 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/guest-information-amendment.md).
# In-House Guest Amend
Steps to amend in house guest information
Guest Information Amendment – allows authorized users to update or correct guest details such as name, contact information, ID proof, or preferences in the hospitality software.
To edit a chosen guest detail:
1. Go to the **Front Desk Main Menu.**
2. Click on **In-House Guest Amend**
3. Guest Information amendment can be used to amend the following details, like **Tariff, Company Name, Travel Agent Name, Guest Personal Information, and Guest Statistics**
4. To edit the Rate, click on the [**Rate Edit**](/front-office-module/fo-reserv/reservation-creation/reservation-creation.md#rate-edit) option as shown below
.png?alt=media)
5. Once the user has clicked on the Rate Edit, the following details can be amended, such as **Rate Type, Tariff, Discount%, Discount Amount, Discount Reason, Company, Adult & Child Information**
6\. To amend the guest details, double-click on the guest row from the guest list. This will take the user to the specific guest file. To fill in or amend the guest details, click on the pencil icon next to the guest name.
7\. The user can then fill in or amend the Guest Personal Details, Likes & Dislikes, Passport & Other Document Details from the guest profile, as shown below
9. The User can amend the Statistics like Business source, Guest Type, Group, Plan, Billing Instructions, Payments, Discounts etc.
10\. All the above amendments will be saved .png?alt=media)in the log and reflected in the relevant audit reports.
---
# 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/guest-information-amendment.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)