> For the complete documentation index, see [llms.txt](https://quteng.gitbook.io/ke-hu-wen-da-ji/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quteng.gitbook.io/ke-hu-wen-da-ji/ke-bian/biao-zhun-ke-bian-zuo-ye-liu-cheng/ke-hu-jin-xing-xian-shang-xuan-cai-yu-ke-bian-yu-yue.md).

# 客戶 - 進行線上選材與客變預約

當建商於後台為您的戶別「開放客變」後，您即可登入專屬的客戶端系統。透過線上選單，可以瀏覽各空間的建材選項、加退帳金額，並在線上完成客變預約。

**操作路徑**：&#x20;

客戶端網頁 > 客變服務

***

**操作步驟**：

1. **進入客變服務**： 登入客戶首頁後，點選畫面中央的 **客變服務** 圖示進入專區。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FqIiKD7hhDY2I6Jl379n2%2Fimage.png?alt=media&amp;token=b71c72dc-77b0-4122-822b-4349015d8b50" alt="" width="231"><figcaption></figcaption></figure>
2. **開始線上選材**： 在客變流程五步驟頁面中，點擊 **step 2 線上選材**，接著點擊藍色的 **選風格 / 選材** 按鈕開始選材。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2F1pYbWEvSQHEdHg8LxQ7s%2Fimage.png?alt=media&amp;token=b933221c-e19c-40d7-a85c-ede9b6a64829" alt="" width="375"><figcaption></figcaption></figure>
3. **選擇裝修風格 (若有開放)**： 若您的戶別包含精裝修方案，系統會請您先挑選裝修風格（如：北歐風、工業風）。選定後，點擊下方的 **下一步 - 選材**。*(**註：若為標準戶，系統將直接進入空間選材**)*

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FzUmjkD4dxKnBVxX6ld6u%2Fimage.png?alt=media&amp;token=45cabed2-0b8a-4e8d-b94f-24a165b6ad5e" alt="" width="231"><figcaption></figcaption></figure>
4. **挑選空間建材**： 系統會顯示依空間列出的各項目。請針對各空間的細項（如：地板材質、房門款式、風扇等）挑選您想要的建材。每個選項皆會清楚標示需加價或退減的金額。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FfN4ozz0sK4oZ5hL8H1sV%2Fimage.png?alt=media&amp;token=f40f9484-477a-4072-bd76-d9c779ca7770" alt="" width="232"><figcaption></figcaption></figure>
5. **確認選材明細與總計金額**： 所有空間皆挑選完畢後，系統會彙整出「風格與選材確認」清單。您可在此檢視原始的標配列表，以及客變選材的明細與「總計金額」。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FvYS3A8JKMPq5O2DiFbVa%2Fimage.png?alt=media&amp;token=38a9554e-9508-4da0-b94c-e61979e31262" alt="" width="375"><figcaption></figcaption></figure>
6. **送出與預約客變面談**： 明細確認無誤後，點擊最下方的 **下一步 - 確認簽名** 進行線上簽名確認。送出後畫面會顯示「完成選材」，此時您可以點擊 **查看明細** 留存紀錄，或直接點擊深藍色的 **預約客變** 按鈕，進入預約畫面完成預約實體面談時間。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FqlM7bWrhRHmwjL4vdpXK%2Fimage.png?alt=media&amp;token=cf9e7b2c-e366-447b-a204-6a6d9846ea05" alt="" width="233"><figcaption></figcaption></figure>


---

# 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://quteng.gitbook.io/ke-hu-wen-da-ji/ke-bian/biao-zhun-ke-bian-zuo-ye-liu-cheng/ke-hu-jin-xing-xian-shang-xuan-cai-yu-ke-bian-yu-yue.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.
