> 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-queries1/faq-on-queries/how-do-i-filter-for-specific-room-features-during-search.md).
# How do I filter for specific room features during search?
To filter for or identify rooms with specific features during your search, you can utilise the Room Search screen during the reservation process or the Vacant Rooms query for a more detailed analysis.
**Identifying Features via the Room Search Screen**
When you are creating a reservation and click the Room number field, the system opens the Room Search screen.
* **Visual Identification:** Once you highlight a specific room from the list, its assigned features (such as "Sea View" or "King Bed") are displayed in the Room Feature section located in the footer of the window.
* **Status Filtering:** The search screen also uses **color codes** to help you visually filter rooms by their current condition, such as Vacant, Dirty, Occupied, or Blocked for maintenance.
**Advanced Filtering in Vacant Rooms Query**
For a more proactive search, you can navigate to **FRONT OFFICE > QUERIES > VACANT ROOMS.**
**Advanced Search Options:** Within this report, you can click on the filter option to access advance room search options. This allows you to set specific date ranges and view unoccupied rooms based on criteria like floor or bed type.
**Configuration Requirements for Filtering**
For room features to be visible and searchable, they must be properly linked in the back-end:
* **Linking Features:** In the Room Master **(MASTERS > ROOMS > ROOM MASTER)**, you must add amenities to specific rooms under the **"FEATURE DETAILS"** section. You can link multiple features to a single room by clicking the plus icon (+) to add new rows.
* **Master Setup:** These features must be pre-created in the Room Feature master tool, where you define each amenity with a unique ID and Name.
---
# 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-queries1/faq-on-queries/how-do-i-filter-for-specific-room-features-during-search.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.
