> 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-reserv/faq-on-reservations/what-is-the-difference-between-a-new-and-repeat-guest.md).

# What is the difference between a New and Repeat guest?

The primary difference between a New Guest and a Repeat Guest lies in how their information is entered into the system and how the hotel utilizes their historical data for service and reporting.

1\. **Information Entry and Selection**

* **New Guest:** You must manually type the guest's name into the designated columns by clicking the pencil icon or double-clicking the row. A new profile is created by entering all required personal details.
* **Repeat Guest:** Instead of manual entry, you click the magnifier (search) icon to search the existing list by the guest's last name. Once found, you double-click the name to automatically populate the reservation with their existing profile data.

2\. **Operational Significance**

* **Advance Recognition:** Categorizing a guest as a **"Repeat Guest"** under Guest Type serves as a clue for hoteliers to provide specific treatment or personalized service in advance.
* **Analytics:** The system tracks repeat business through the Business Source field, which is compulsory because it indicates opportunities for repeat business and has financial implications.

3\. **Reporting and Analysis**

* **Repeaters Definition:** In the Guest In House report, **"Repeaters"** are specifically identified as guests who have stayed at the hotel at least twice.
* **Detailed Analysis:** There is a dedicated Repeat Guest analysis report that allows you to filter and view specific details like mobile numbers, email, company affiliation, and nationality for these returning individuals.
* **Emerging Markets:** The system also generates reports like "New Guest Arrivals and Guest Nights by Nationality," which helps the hotel identify emerging markets by tracking guests who have never stayed at the property before.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-368317c18413923fa9c30f0c83aa99acc53bd7b2%2FScreenshot%20From%202026-06-11%2010-17-36.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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-reserv/faq-on-reservations/what-is-the-difference-between-a-new-and-repeat-guest.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.
