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

# 建立和編輯訂房

開啟預訂列表或使用房間狀態板中的一個單位的預訂.

![新的預訂](https://4114193002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FORJMZdLSPpqY9fRY4YKZ%2Fuploads%2Fgit-blob-e915bad22f5d679e04174cc7ba2812724c4fe306%2Fnew-booking.png?alt=media)

## 建立預訂

1. 選擇正確的酒店分支,並開啟新的預訂表.
2. 檢查到達,晚上和出發. 改變一個欄位後,檢查其他欄位的計算值.
3. 輸入預訂人數和客人數.
4. 填寫每個客人的姓名,電話,身份/護照和國籍欄位. 性別是不可選的.
5. 在租單元的欄位中選擇正確的房間,公寓或床.
6. 檢視每晚的價格以及其他收費或預付費. 每晚的價格不是總住宿價格.
7. 在登錄檔中新增下班所需的資訊.
8. 儲存並確認預訂顯示了正確的單位和日期.

舉個例子:10月15日抵達和10月18日出發意味著三個晚上. 另一個預訂可以在10月18日的出發時間開始. 一個未登記的客人,即使在計劃出發後,也可以阻止該單位.

## 為什麼沒有一個單位?

這些日期可能與另一個預訂,父母或兒童單位的預訂或不合適的單位狀態衝突. 預訂一個整套公寓,將其房間封鎖在同一時期. 預訂房間會阻礙其床. 在同一房間的單獨租用床可以單獨預訂.

## 編輯日期

1. 開啟預訂詳情.
2. 選擇編輯預訂日期.
3. 檢視並儲存新的日期和價格欄位.
4. 檢查日曆的變化.

您可以在登記後編輯預定日期. 實際到達時間和前一次單位移動保持不變. 新出發必須是未來的,不應與另一個預訂發生衝突. 使用 [換房操作](/zh-tw/ri-chang-ying-yun/move-and-cancel.md) 換個單位.

![預訂列表](https://4114193002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FORJMZdLSPpqY9fRY4YKZ%2Fuploads%2Fgit-blob-20bc26fb698709830e5be3f1e3f783e3a3187d56%2Fbookings.png?alt=media)

接下來: [客人登記](/zh-tw/ri-chang-ying-yun/check-in-out.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/reservations.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.