> 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/shou-fu-ren-yuan-ru-he-jiang-bao-xiu-dan-zhuang-tai-she-ding-wei-yi-jie-dan-apppc.md).

# 售服人員如何將報修單狀態設定為已接單？（App/PC）

#### **路徑：** 

【App】售服系統 > 報修列表

【PC】售服系統 > 客戶線上報修

***

#### **操作方式1（以** App 為例**）：**

1. 前往 **報修列表** 頁面：登入系統後，前往 **售服系統 > 報修列表**。 

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FJfzZCeBPxgjtT1lFQwLi%2Fnote%20(7).jpg?alt=media&amp;token=4f0c206a-ecf6-4de7-8de7-570b7fd84e4b" alt="" width="563"><figcaption></figcaption></figure>
2. 進入報修詳細後，點擊畫面右上方 狀態方塊，將彈出接單確認視窗，接單人員會依登入帳號者判斷。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FXOC41phYUWKCGvkJW2JG%2Fnote%20(8).jpg?alt=media&amp;token=785b695b-7346-4bde-9d29-ede8041e7a80" alt="" width="563"><figcaption></figcaption></figure>
3. 彈出確認接單視窗，點擊 **確認** 按鈕，即完成設定，報修詳細內，狀態將改為「已接單」，並顯示接單人員。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FbYb7bW1hEg1VDURT06uA%2Fnote%20(9).jpg?alt=media&amp;token=9d538ad4-bc78-48c4-9bb2-835486026e2c" alt="" width="375"><figcaption></figcaption></figure>

#### 操作方式2（以 PC 為例）：

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

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FFYIvfBdPNAtnSArltkJA%2Fnote.jpg?alt=media&amp;token=7a2cdb56-e987-4d4a-ad3a-45a41ec36a76" alt="" width="563"><figcaption></figcaption></figure>
2. 點擊 該筆報修右方 **查看** 按鈕。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2Fu5QQf7whZzZlgD8upLHm%2Fimage.png?alt=media&amp;token=3aaf763a-685f-4e4e-9ec9-fd5b204fe64b" alt="" width="563"><figcaption></figcaption></figure>
3. 設定接單人員：報修單詳細 視窗最下方選擇接單人員後，點擊視窗右上方 **送出** 按鈕，即完成設定。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2Fs5OOHCqKvb0tTPtO0fS3%2Fnote%20(6).jpg?alt=media&amp;token=ba79a876-f032-486f-bd82-eabca19949f4" 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/shou-fu-ren-yuan-ru-he-jiang-bao-xiu-dan-zhuang-tai-she-ding-wei-yi-jie-dan-apppc.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.