> 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/fo-frontdesk-tag-room-as-dirty-inspected-pickup.md).

# Room Status Tagging

Steps to tag status for rooms

1.Go to **Front office>>** **Front Desk >>** **Room as Room Status Tagging**

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

2. The screen displays a list of rooms. You can filter the rooms based on their status, such as Occupied, Vacant, or Guest Block.
3. The supervisor can inspect the rooms and mark them as dirty if required by selecting the checkbox under the “Tag Dirty” field.

4\. Once the room is marked or tagged as dirty, choose the priority level, and enter the narration.

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

5\. Click save ![](https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-e5a7484eacbd59f2216932d81104ad1d2774e689%2Fimage%20\(188\).png?alt=media)to complete the process. A confirmation message pops up to confirm the change of status.

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

6. Once the rooms are tagged as dirty, if the user wants, he can list out all the dirty rooms by clicking the dirty room filter.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-b9b1a6e9c73da5619ee963ce61072c76fc4a1d76%2Fimage%20(190).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-frontdesk/fo-frontdesk-tag-room-as-dirty-inspected-pickup.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.
