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

# 第一天：準備您的住宿設施

本頁面是針對已經由技術團隊建立賬戶和業務的經理. 如果酒店分支已經在使用,請檢查現有記錄,而不是建立複製的房間或床.

## 建議設定順序

1. 開啟酒店分支的個人資料,並驗證商業和酒店分公司的資訊.
2. 在地板和房間定義中,建立地板並分配房間和公寓.
3. 每個房間,請選擇是否將整個房間或其單獨的床單租.
4. 定義實際的床傢俱. 對於旅館,請檢查床位水平和提供的床位.
5. 在相關編輯表格中填寫房間和酒店分支設施和庫存數量.
6. 在員工定義中審查員工角色和酒店分支機構訪問.
7. 準備業務資訊和所需的文件模板語言版本.
8. 在房間狀態委員會上檢視目前的清潔和維護狀態.

![樓層和房間的定義](https://4114193002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FORJMZdLSPpqY9fRY4YKZ%2Fuploads%2Fgit-blob-1c3f48db0cfc367caee91477bee69e897a87d31f%2Fproperty.png?alt=media)

## 在第一次預訂之前

| 檢查      | 預期結果                  |
| ------- | --------------------- |
| 酒店分店和樓層 | 房間出現在正確的酒店分支和樓下.      |
| 租金方式    | 您可以選擇您打算租來的房間或床.      |
| 清潔      | 機器已準備好,並標記為清潔.        |
| 日期      | 抵達和出發是正確的,沒有矛盾的保留.    |
| 工作人員    | 每個員工可以使用自己的帳戶訪問所需的頁面. |

在培訓過程中,請使用經理指定的測試環境,以免取樣交易與現場業務記錄混合.

繼續使用 [酒店分支結構](/zh-tw/zhu-su-she-shi-guan-li/structure.md) 和 [預訂的建立](/zh-tw/ri-chang-ying-yun/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-tw/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.