> For the complete documentation index, see [llms.txt](https://doc.moze.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.moze.app/about/contact.md).

# 聯絡我們

* [臉書粉專](https://www.facebook.com/mozeapp/)：版本更新公告、優惠活動、未來方向都會第一時間在這裡分享，有問題也可以直接私訊小編。
* [臉書社團](https://www.facebook.com/groups/moze3/)：目前最大的討論區（14000+），任何記帳的疑難雜症都可以在這裡發文討論，也有很多熱心的記帳高手會協助你解決問題。
* [Telegram](https://t.me/+Qm1UaD36Ga-Ohpk7)：聚集台灣、大陸、香港等用戶的聊天室（1500+），可以在這裡分享記帳心得和建議。
* [Email](mailto:hello@moze.app)：從 App 內的「回報問題」直接來信，說明問題並附上截圖，我們會盡快回覆。


---

# 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://doc.moze.app/about/contact.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.
