> 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/gong-wu-ren-yuan-pai-gong-hui-bao-jin-du/app-bao-xiu-lie-biao-nei-kan-yan-hui-bao-gong-neng.md).

# App 報修列表內「勘驗回報」功能

#### **路徑**：

App售服系統 > 報修列表 > 勘驗回報

***

#### **介紹**：

售服人員在開始修繕之前，請工務組進行初步勘驗並且回報，以利後續評估該筆售服報修。

***

#### **操作方法**：

1. 前往 **報修列表** 頁面：登入系統後，點擊 **售服系統 > 報修列表。**
2. 畫面下方可以看到「勘驗回報」頁面，點擊綠色**+** 按鈕，開始新增一筆勘驗回報。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FxJVoKqkvZE15CSHaKNyU%2Fimage.png?alt=media&amp;token=08c9eb77-1c83-49f2-aa38-2cb993e508a6" alt="" width="230"><figcaption></figcaption></figure>
3. 依序輸入勘驗人、勘驗內容、勘驗日期、勘驗時間與勘驗照片/影片。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2Fb0xdNW7ESe9rrQVhh904%2Fimage.png?alt=media&amp;token=f9efd1a4-8d28-4c32-b3f0-783a6868c5af" alt="" width="230"><figcaption></figcaption></figure>
4. 輸入完勘驗資訊後，點擊 畫面下方 **確定** 按鈕，即完成勘驗回報。

<figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FLMdryBFVAk6qZaF1Q2rT%2Fnote%20(18).jpg?alt=media&amp;token=5131d019-1175-4bc8-a772-7befd484429e" alt=""><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/shou-fu/gong-wu-ren-yuan-pai-gong-hui-bao-jin-du/app-bao-xiu-lie-biao-nei-kan-yan-hui-bao-gong-neng.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.