> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/conversation-manager.md).

# Conversation manager

**Manager** helps you inspect conversations from a published interface. Use it to find a user's request, read the exchange, and locate the related workflow execution.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2F5axhc2i6VMGomLX8a0fy%2FG066.mp4?alt=media&token=571fafdd-e2b7-46ac-b0fd-da1d00472d21>" %}

## Before you start

Use an account with access to the project’s Manager and Analytics views.

## Find a conversation

Open the project's Manager tab to browse conversations.

![Conversation Manager search view](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/OSfGHgZ4UtDOZ0d9BvfV/assets/g066-g066-01-manager.png)

Use the identity and other details on each entry to distinguish users and exchanges.

Use Search to find the relevant user identity.

![Conversation Manager search view](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/5HhjgUS4oezOzPcyafkA/assets/g066-g066-02-search.png)

Open a result and check its contents rather than relying on a similar-looking list label.

## Read the exchange

Read the selected transcript and compare the user's request with the assistant's response.

![Conversation Manager transcript view](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/GV2Y91WSmvDs94hcWaXt/assets/g066-g066-03-transcript.png)

Review the full exchange before deciding whether the answer addressed the question.

## Inspect the corresponding run

Open Analytics and locate the corresponding execution.

![Conversation execution in Analytics](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/7BIL0w7o5CwuOaVWPP9w/assets/g066-g066-04-analytics.png)

Match the input, time, and conversation identity with the transcript you reviewed.

Open Run Details and inspect the input, output, and node progress.

![Conversation execution in Analytics](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/mk3hdV00d532nhHgmgLm/assets/g066-g066-05-details.png)

A successful execution status does not guarantee that the answer is correct or useful.

## Review conversation context

Return to Manager to review the surrounding conversation.

![Conversation history and surrounding context](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/1YWVOOdigztjbBB05sNo/assets/g066-g066-06-multi-turn.png)

Earlier messages and attachments can explain context that is not clear from a single response.

## Important behavior

A successful run status means execution completed. Review the answer and source information to assess whether it addressed the user’s request.

## Continue

* [Debug a recorded run](https://docs.stackai.com/guides-and-quickstarts/evaluations-and-observability/debug-a-recorded-run.md)
* [Interface branding and feedback](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/interface-branding-and-feedback.md)


---

# 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.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/conversation-manager.md?ask=<question>&goal=<user_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.
