> 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-ren-yuan-jie-dan-zhuan-gong-wu-jie-an/ru-he-cha-kan-bao-xiu-xiang-guan-chu-li-ren-yuan-pc.md).

# 如何查看報修相關處理人員？（PC）

#### **路徑：** 

【路徑一】售服系統 > 客戶線上報修  

【路徑二】登入系統後，畫面右上方 報修總表 按鈕

***

#### **操作方式（以 路徑一 為例）：** 

1. 前往 **客戶線上報修** 頁面：選擇建案後，進入 **售服系統 > 客戶線上報修。**

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FRJin599vwP4LDRkxxr5u%2Fnote%20(43).jpg?alt=media&amp;token=431c3926-fca5-48b2-af05-40265bd8136d" alt="" width="563"><figcaption></figcaption></figure>
2. 在 **客戶線上報修** 頁面，將滑鼠移至該筆報修的狀態欄位上。
3. 即可查看：
   1. 報修人員
   2. 接單人員
   3. 售服人員
   4. 工務主管
   5. 派工人員
   6. 結案人員<br>

      <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2Fj6aafBOMw2LlbR4sQS5D%2Fimage.png?alt=media&amp;token=e4cd47e5-c3de-4be1-896b-62e5b9f27160" alt="" width="563"><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/shou-fu-ren-yuan-jie-dan-zhuan-gong-wu-jie-an/ru-he-cha-kan-bao-xiu-xiang-guan-chu-li-ren-yuan-pc.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.