> 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/l-ke-yu-wen-jian/history.md).

# 旅客資料、搜尋與住宿紀錄

## 客人的詳細資訊

1. 在預訂表中開啟客人行,或使用已有的預訂中編輯客人.
2. 在指定欄位中輸入每個人的正確姓名,聯絡方式和身份資訊.
3. 從國家列表中選擇國籍. 你可以按國家名稱或程式碼搜尋.
4. 加入一個客人排列,以便後者加入.
5. 儲存和驗證預訂的客人名單.

不要假設兩個同名的人是同一個客人. 該應用程式不僅僅基於類似的名字的人員合併. 在房間/公寓預訂中,客人數和單獨租用床的容量限制是單獨的處理.

## 找到過去的逗留

1. 開放客人搜尋和歷史.
2. 設定日期和狀態過選器.
3. 用名字,身份資訊或電話號碼搜尋.
4. 開啟記錄,檢查逗留日期和單位分配.
5. 如果客人搬家,請檢查以前的單位和每個期間共住的人.

## 輸出列表

在使用Excel或PDF出口之前檢查您的過 ?? 器. 客戶出口不僅覆蓋可見頁面,覆蓋過度查詢, 覆蓋到10,000行. 為更大的結果,縮小日期範圍.

如果PDF生成失敗,請將錯誤傳送給管理員,而不是重複提交相同的請求. 伺服器的PDF生成元件可能需要注意.

相關指南: [檔案和模板](/zh-tw/l-ke-yu-wen-jian/documents.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/l-ke-yu-wen-jian/history.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.