> 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/move-and-cancel.md).

# 换房、互换房源与取消预订

## 移送客人到另一个单位

1. 打开预订,然后选择更换室.
2. 选择移动操作.
3. 选择可用的目的地房间,公寓或床.
4. 检查客人,日期和目的地,然后确认.
5. 检查客人是否出现在新单位的卡上.

对于已登记的客人来说,此举从运营时间开始生效. 在前一个单位度过的时间仍然是历史的. 不要试图通过手动更改单元代码来重写历史.

## 交换两个预订单位

1. 换衣室开放,一个预订.
2. 选择交换操作.
3. 选择正确的第二次预订.
4. 检查两个客人,两个单位和他们的日期.
5. 后面确认和检查两个预订.

两方都被共同验证. 可用性或客人容量限制可能会阻碍交换. 不要创建两个新的预订,以绕过错误.

## 在登记前取消预订

1. 选择正确的预订.
2. 开放 取消预订.
3. 填写确认和任何必要的理由.
4. 检查更新的预订状态.
5. 如果收到钱, [金融交易记录](/zh-cn/cai-wu-yu-bao-biao/transactions.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/move-and-cancel.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.