> 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/ri-chang-yun-ying/reservations.md).

# 创建和编辑预订

打开预订列表或使用房间状态板中的一个单位的预订.

![新的预订](https://923543600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFYpr3SG1RnMm4DANLHfW%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-cn/ri-chang-yun-ying/move-and-cancel.md) 换个单位.

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

接下来: [客人登记](/zh-cn/ri-chang-yun-ying/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-cn/ri-chang-yun-ying/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.