> 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/end-user-and-partner-section/end-user-section/ressources-and-support/support-portal-status.md).

# Support Portal Status

To give you better visibility into your requests, here’s what each ticket status means and when you’ll see it used:

* **New**\
  – We’ve received your request and it’s awaiting review.
* **Open**\
  – Your ticket has been reviewed and queued for action.
* **In Progress**\
  – DocBits is actively working on your issue.
* **Waiting on Customer Response**\
  – We need more information or clarification from you. You’ll see this when we’ve asked questions or requested files.
* **Waiting for Customer Confirmation**\
  – We’ve implemented a fix or provided guidance and are waiting for you to confirm the issue is resolved.
* **Waiting on Product Team**\
  – Your request is a feature suggestion or involves a known product issue and has been logged for the Product team’s roadmap.
* **Closed – Resolved**\
  – The issue is fully resolved and confirmed, or no further action is needed.
* **Closed – No Response**\
  – After multiple follow-ups with no reply, we close the ticket. You can always reopen it by responding.
* **Closed – Known Issue**\
  – This ticket tracks a known product bug that’s already on our backlog. It’s closed here but remains visible in our internal planning.
* **Closed – Logged as Idea**\
  – Your suggestion has been noted for future consideration by our Product team.
* **Duplicate**\
  – We’ve merged this ticket into an existing one covering the same issue.
* **Not Planned**\
  – This request is valid but isn’t in our current roadmap. We’ll keep it on file for future prioritization.
* **Spam**\
  – This ticket was identified as non–product-related (e.g. bot or unrelated inquiry) and has been closed.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.docbits.com/end-user-and-partner-section/end-user-section/ressources-and-support/support-portal-status.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.