> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/ressources-and-support/support-portal-status.md).

# 支持门户状态

为了让您更清楚地了解请求进展，以下说明了每种工单状态的含义，以及您会在什么情况下看到该状态：

* **新建**\
  – 我们已收到您的请求，正在等待审核。
* **已开启**\
  – 您的工单已审核，并已排队等待处理。
* **处理中**\
  – DocBits 正在处理您的问题。
* **等待客户回复**\
  – 我们需要您提供更多信息或说明。我们向您提问或请求文件时，您会看到此状态。
* **等待客户确认**\
  – 我们已实施修复或提供指导，正在等待您确认问题是否已解决。
* **等待产品团队处理**\
  – 您的请求是功能建议，或涉及已知产品问题，并已记录到产品团队的路线图中。
* **已关闭 – 已解决**\
  – 问题已完全解决并得到确认，或无需进一步处理。
* **已关闭 – 未收到回复**\
  – 多次跟进仍未收到回复后，我们会关闭工单。您随时可以通过回复重新开启工单。
* **已关闭 – 已知问题**\
  – 此工单用于跟踪已列入待办事项的已知产品错误。工单在此处关闭，但仍会显示在我们的内部规划中。
* **已关闭 – 已记录为创意**\
  – 您的建议已记录，供产品团队日后考虑。
* **重复**\
  – 我们已将此工单合并到一个涵盖相同问题的现有工单中。
* **暂不计划**\
  – 此请求合理，但目前不在我们的路线图中。我们会将其存档，以供日后确定优先级时参考。
* **垃圾信息**\
  – 此工单被认定为与产品无关（例如机器人提交的内容或无关咨询），因此已关闭。


---

# 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.docbits.com/chinese/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/ressources-and-support/support-portal-status.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.
