> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/cregis-wallet-guide/zh-cn/resources/contact_us.md).
# 联系我们
## **Cregis Support – 随时为您服务**
我们致力于为每一位用户提供优质的支持服务，无论何时何地，Cregis Support 团队都将随时待命，解答您的疑问，协助解决问题。法定节假日期间服务时间将有所调整，具体以官网公告为准。
若需帮助，请随时通过 **** 联系我们，我们将尽快为您提供协助。Cregis Support，您的信赖伙伴！
---
# 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://support.cregis.com/cregis-wallet-guide/zh-cn/resources/contact_us.md?ask=&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.