> 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/first-day.md).

# 第一天：准备您的住宿设施

本页面是针对已经由技术团队创建账户和业务的经理. 如果酒店分支已经在使用,请检查现有记录,而不是创建复制的房间或床.

## 建议设置顺序

1. 打开酒店分支的个人资料,并验证商业和酒店分公司的信息.
2. 在地板和房间定义中,创建地板并分配房间和公寓.
3. 每个房间,请选择是否将整个房间或其单独的床单租.
4. 定义实际的床家具. 对于旅馆,请检查床位水平和提供的床位.
5. 在相关编辑表格中填写房间和酒店分支设施和库存数量.
6. 在员工定义中审查员工角色和酒店分支机构访问.
7. 准备业务信息和所需的文档模板语言版本.
8. 在房间状态委员会上查看目前的清洁和维护状态.

![楼层和房间的定义](https://923543600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFYpr3SG1RnMm4DANLHfW%2Fuploads%2Fgit-blob-1c3f48db0cfc367caee91477bee69e897a87d31f%2Fproperty.png?alt=media)

## 在第一次预订之前

| 检查      | 预期结果                  |
| ------- | --------------------- |
| 酒店分店和楼层 | 房间出现在正确的酒店分支和楼下.      |
| 租金方式    | 您可以选择您打算租来的房间或床.      |
| 清洁      | 机器已准备好,并标记为清洁.        |
| 日期      | 抵达和出发是正确的,没有矛盾的保留.    |
| 工作人员    | 每个员工可以使用自己的帐户访问所需的页面. |

在培训过程中,请使用经理指定的测试环境,以免采样交易与现场业务记录混合.

继续使用 [酒店分支结构](/zh-cn/zhu-su-she-shi-guan-li/structure.md) 和 [预订的创建](/zh-cn/ri-chang-yun-ying/reservations.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/first-day.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.