> 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/ru-men/daily-workflow.md).

# 櫃檯班次的完整工作流程

## 班級開始

1. 透過自己的帳戶登入並確認所選擇的酒店分支.
2. 在接待說明板上閱讀緊急和正在進行的任務.
3. 檢查房間狀況委員會的汙穢,不正常和改造單位.
4. 在停留日曆和預訂列表中檢視今天的抵達和出發情況.
5. 考慮遲到的出發以及計劃在同一天再到達的房間.

## 在白天

記錄新預訂 [預訂工作流程](/zh-tw/ri-chang-ying-yun/reservations.md). 檢查到達的客人在現有的預訂,而不是建立第二次預訂. 在移動客人時使用預訂室的房間更換操作. 新增額外的服務到正確的預訂客戶賬戶.

在清潔完成後,更新清潔狀態. 永遠不要將未準備的房間標記為清潔,只是為了透過驗證資訊.

## 在出發時

1. 開啟 [預訂客戶賬戶](/zh-tw/ri-chang-ying-yun/check-in-out.md).
2. 單獨審查住宿和服務費用,收到的支付,退款和保證金.
3. 在您的許可範圍內填寫任何需要的記錄.
4. 確認出境後,請檢查住宿和房間狀況.
5. 如果房間需要做好準備,請留下一個接待通知.

## 轉讓

清楚地記錄未完成的任務,預期的抵達和需要跟進的餘額. 如果您可以訪問轉班和現金報告,請將記錄的現金流動與實際計數的現金進行比較. 當你的工作完成時,請簽署.

相關指南: [接待通知](/zh-tw/ri-chang-ying-yun/reception-notes.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/ru-men/daily-workflow.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.