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

# 前台班次的完整工作流程

## 班级开始

1. 通过自己的帐户登录并确认所选择的酒店分支.
2. 在接待说明板上阅读紧急和正在进行的任务.
3. 检查房间状况委员会的污秽,不正常和改造单位.
4. 在停留日历和预订列表中查看今天的抵达和出发情况.
5. 考虑迟到的出发以及计划在同一天再到达的房间.

## 在白天

记录新预订 [预订工作流程](/zh-cn/ri-chang-yun-ying/reservations.md). 检查到达的客人在现有的预订,而不是创建第二次预订. 在移动客人时使用预订室的房间更换操作. 添加额外的服务到正确的预订客户账户.

在清洁完成后,更新清洁状态. 永远不要将未准备的房间标记为清洁,只是为了通过验证信息.

## 在出发时

1. 打开 [预订客户账户](/zh-cn/ri-chang-yun-ying/check-in-out.md).
2. 单独审查住宿和服务费用,收到的支付,退款和保证金.
3. 在您的许可范围内填写任何需要的记录.
4. 确认出境后,请检查住宿和房间状况.
5. 如果房间需要做好准备,请留下一个接待通知.

## 转让

清楚地记录未完成的任务,预期的抵达和需要跟进的余额. 如果您可以访问转班和现金报告,请将记录的现金流动与实际计数的现金进行比较. 当你的工作完成时,请签署.

相关指南: [接待通知](/zh-cn/ri-chang-yun-ying/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-cn/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.