> For the complete documentation index, see [llms.txt](https://docs.knowbase.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.knowbase.ai/ai-assistants/conversations.md).

# Conversations

The Conversations tab shows every chat session visitors have had with your assistant.

## Filtering

Filter conversations by:

* **All** — every conversation
* **Positive** — conversations with thumbs up feedback
* **Negative** — conversations with thumbs down feedback
* **Unanswered** — conversations where the assistant couldn't find an answer

## Viewing a conversation

Click any conversation to see the full message thread on the right. Each message shows:

* Whether it's from the visitor or the bot
* Thumbs up/down feedback (if given)
* "Could not answer" badge on messages where the assistant had no relevant context

## What to do with this data

* Spot questions your documents don't cover → upload more content or add [Q\&A Pairs](/ai-assistants/creating-an-assistant.md)
* Find negative feedback → improve your system prompt or add guardrails
* Track unanswered questions → add them as Q\&A Pairs for exact answers


---

# 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.knowbase.ai/ai-assistants/conversations.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.
