> 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/shou-fu/ke-hu-duan-xiang-guan-she-ding-yu-shuo-ming/ke-hu-bao-xiu-mian-deng-ru-qian-ming-ye-yu-lian-jie-qu-de-fang-shi.md).
# 客戶報修-免登入簽名頁與連結取得方式
在報修案件修繕完成後，客戶可透過 免登入簽名頁面 完成自主簽名，不需登入帳號即可確認修繕結果。
#### **路徑**：
【PC】
1. 報修總表
2. 售服系統 > 客戶線上報修
【App】
1. 報修總表
2. 售服系統 > 報修列表 > 立即結案
3. 售服系統 > 修繕列表 > 客戶簽名，立即簽名
***
#### **【PC】操作方法**（以 報修總表 為例 ）：
1. 登入系統後，前往 **報修總表** 頁面。
2. 找到欲發送免登入簽名連結的報修，點擊右側的 （）**查看** 按鈕。
3. 於視窗上的「報修資訊」分頁下拉到底，即可看到結案資訊-報修連結，進行複製或點擊導至新分頁。
***
#### **【App】操作方法**（以 修繕列表 為例）：
1. 前往 **售服系統 > 修繕列表** 頁面
2. 選擇一筆報修，點擊 **客戶簽名，立即結案** 按鈕
3. 視窗下方即可看到客戶連結，進行複製或分享，供後續客戶查看與簽署。
---
# 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/shou-fu/ke-hu-duan-xiang-guan-she-ding-yu-shuo-ming/ke-hu-bao-xiu-mian-deng-ru-qian-ming-ye-yu-lian-jie-qu-de-fang-shi.md?ask=&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.
.jpg?alt=media&token=6694e8e3-90f9-416a-8fc1-8c32128074b1)
.jpg?alt=media&token=dbd2bd18-bd0f-4bbc-83af-27e143db2c6a)
.jpg?alt=media&token=c972433f-0b71-477b-bd61-69eeb69d8be4)