> 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/shou-fu-man-yi-du-wen-juan/ru-he-shou-dong-fa-song-man-yi-du-wen-juan-yu-cha-kan-jie-guo.md).
# 如何手動發送滿意度問卷與查看結果？
#### **路徑**：
1. 報修總表
2. 售服系統 > 客戶線上報修
***
#### **操作方法**（以報修總表為例）：
1. 前往 **報修總表** 頁面：登入系統後，選擇對應系統，點擊畫面右方 **報修總表** 按鈕。
2. 發送滿意度問卷：
1. 於 報修總表 頁面，點擊該筆報修右側 **查看**（） 按鈕，進入 **報修詳細資訊** 頁面。
2. 於 **報修詳細資訊** 頁面，進入 **售服結案** 頁面，點擊畫面下方 **寄送滿意度問卷** 按鈕。
3. 確認問卷內容：此視窗可以預覽先前於客戶端管理設定好的問卷題目，確認問題沒問題後，點擊 **寄送** 按鈕，客戶將會收到問卷填寫邀請。
4. 查看問卷結果：有三處可以查看。
1. 前往 **客戶端管理** 頁面。登入系統後，點擊畫面右方 **客戶端管理** 按鈕，進入 **問卷調查結果** 頁面。此頁面可以查看所有依照建案分類的問卷結果。
2. 前往 **報修總表** or **客戶線上報修** 頁面。將報修列表拉至最後，會看到問卷調查欄位，此頁面針對單一報修查看問卷結果。
---
# 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/shou-fu-man-yi-du-wen-juan/ru-he-shou-dong-fa-song-man-yi-du-wen-juan-yu-cha-kan-jie-guo.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.
