> For the complete documentation index, see [llms.txt](https://support.dashworks.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.dashworks.ai/optimize/feedback.md). # Feedback {% hint style="info" %} Any feedback you share with Dashworks is only used to improve responses to questions asked in your workspace. In no case is your content or feedback shared with any other Dashworks customer. {% endhint %} When you ask Dashworks a question, it searches through all the apps you have connected to it to find relevant documents that might have the answer. It then ranks these sources using various signals such as the recency of the information, the source's authority, its relevance to the question, and more.\ \ However, sometimes Dashworks may get confused if the search results are similar or if the information is out of date or conflicting. In such cases, it may prioritize or deprioritize incorrect search results. To rectify this, you can use the thumbs up and thumbs down buttons below each response to give an upvote or downvote on specific references. This will let Dashworks know which sources are most helpful or least helpful. Dashworks will use this feedback to prioritize or deprioritize similar references for future questions. --- # 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.dashworks.ai/optimize/feedback.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.