> 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/chang-jian-wen-ti/ke-hu-bao-xiu-hou-wei-shen-mo-xiang-guan-ren-yuan-mei-you-shou-dao-app-tong-zhi.md).

# 客戶報修後，為什麼相關人員沒有收到 APP 通知？

1. 請確認負責該建案的員工皆已下載「福爾摩沙建設整合系統」APP 並成功登入過至少一次。
2. 檢查 APP 內的通知設定是否開啟。
3. 若問題持續，可能是系統 Bug，請回報給渠騰人員處理。


---

# 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/chang-jian-wen-ti/ke-hu-bao-xiu-hou-wei-shen-mo-xiang-guan-ren-yuan-mei-you-shou-dao-app-tong-zhi.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.