> For the complete documentation index, see [llms.txt](https://docs.interaktifotel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interaktifotel.com/zh-tw/ri-chang-ying-yun/room-board.md).

# 房況看板與清潔管理

在酒店運營下開啟房間狀態表.

![房間狀態板](https://4114193002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FORJMZdLSPpqY9fRY4YKZ%2Fuploads%2Fgit-blob-7cc957a5c2bb09cb38b9e86db2d46962bda5e78a%2Fboard.png?alt=media)

## 閱讀一個房間卡

閱讀單位程式碼,客人或預訂資訊以及抵達/出發日期. 佔用和清潔是不同的:一個清潔的房間可能被佔用,一個空的房間仍然需要清潔. 閱讀狀態標籤,而不是隻依賴顏色.

## 找一個單位

1. 確認所選擇的酒店分支.
2. 根據需要調整搜尋,地板和日期過選器.
3. 檢視卡上的單位程式碼.
4. 開啟卡的動作選單. 在桌面上,右鍵選單還提供預訂,客人,狀態和文件操作.

在檢視另一個日期時,不要把該日期的預訂狀態和當前的清潔狀態混為一談.

## 改變清潔狀態

1. 確認準備的房間程式碼與負責人員.
2. 開啟卡上的房間狀態控制.
3. 根據實際情況,選擇清潔或髒.
4. 等待確認,然後檢查更新的標籤.

授權的賬戶還有空置,不正常和改造的選項. 在記錄維護或故障之前,請檢查現有的住宿和即將到來的預訂. 填寫申請所要求的理由或確認欄位.

## 如果登入被阻止

申請檢查清潔,活躍逗留和可用性,從實際到達時間到計劃出發. 如果出現汙房警告,請檢視房間或床的確切程式碼,更新並驗證當前狀態.

如果問題繼續,請按照 [解決問題步驟](/zh-tw/shuo-ming-yu-can-kao/troubleshooting.md).


---

# 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://docs.interaktifotel.com/zh-tw/ri-chang-ying-yun/room-board.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.