> For the complete documentation index, see [llms.txt](https://docs.dataimpulse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataimpulse.com/dataimpulse-documentation-zh-cn/zhi-chi.md). # 支持 有问题吗？我们的支持团队全天候 24/7 在线。 有问题吗？ **我们的支持团队全天候 24/7 提供服务**. 您可以通过以下方式之一联系我们的支持团队： * **在线聊天**: 通过本文件右下角的在线聊天小组件或我们的 [网站](https://dataimpulse.com/)。在线聊天非常适合快速提问或提交错误报告。 * **电子邮件**: 请联系 用于非紧急问题或建议。 * **Telegram**: 请联系 [@di\_support\_team](https://www.telegram.me/di_support_team) 用于任何紧急问题。 --- # 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://docs.dataimpulse.com/dataimpulse-documentation-zh-cn/zhi-chi.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.