> For the complete documentation index, see [llms.txt](https://docs.getdot.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getdot.ai/train-dot/user-feedback.md).
# User Feedback
is valuable input for learning
Users can either upvote or downvote a response from Dot. This feedback tells admins where Dot's knowledge base needs work.
## Negative feedback
👎 is the signal worth acting on. Dot learns from being corrected far more than from being approved of: a downvote, ideally with a sentence about what the right answer was, tells an admin exactly which definition, table, or note is missing or wrong.
Users rate an answer with 👍 or 👎
## Positive Feedback
👍 marks an answer as good. It is a light-touch signal — useful for seeing which topics are working, but it does not by itself change how Dot answers in the future.
## Admin Overview
Admins can see the history of all users on the **History** page. Its **Review** column shows what users clicked: a thumbs down when a conversation has at least one dislike, and a thumbs up when it has only likes.
The same column shows Dot's own review of each conversation, such as **Issue** or **Success**. Dot reviews its answers in the background whether or not anyone clicks anything. See [Maintaining Dot](/train-dot/maintaining-dot.md) for how to work through both signals.
To see only chats that built or edited an app, pick **App building** under **Type**. To get these chats as a CSV file, use the [API](/developers/api/commonly-used-endpoints.md#export-conversation-history).
