> For the complete documentation index, see [llms.txt](https://docs.omnivatelehealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnivatelehealth.com/admin/reports/feedback.md).
# Feedback
In this section admin can understand user sentiments and improve platform functionality based on feedback.
### Overview
The Feedback section in the admin panel serves as a valuable resource for understanding user sentiments and improving the platform's functionality based on user experiences.
### **Searching and Filtering**
* **Search by user name:** Easily locate feedback by searching for a specific user's name.
* **Filters:** Use filters to view comments from specific user groups, such as referring providers, consulting providers, or patients.
### **Understanding Feedback**
Admins can review feedback to gain insights into user preferences and concerns:
* Identify areas of satisfaction: Understand what users like about the platform.
* Address concerns: Take note of any dislikes or issues raised by users to address them effectively.
* Continuous improvement: Use feedback to enhance platform features and usability, ensuring a positive user experience.
Feedback
---
# 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.omnivatelehealth.com/admin/reports/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.
