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

# Conversations

Review individual Sagent sessions, flags, outcomes, and tool activity.

Use **Conversations** to review individual sessions behind trends in **Overview**.

Start with the conversation list. Then open a session to inspect its full thread.

Use this tab to validate what caused a drop, spike, or flag pattern.

### Conversation list

The conversation list is a browsable view of recent sessions.

Each row includes metadata to help you scan quickly:

* **Messages** — number of messages in the conversation.
* **Flags** — monitoring classifications triggered in that conversation.
* **Outcome** — whether the recorded conversation completed or remained incomplete.
* **Product shown/found** — number of products shown or found.
* **CTA clicked** — a recorded CTA click, if any.
* **Date** — when the conversation occurred.

The list can also show sessions that may need attention.

An incomplete outcome does not show why a shopper left. A missing CTA click does not prove absent purchase intent.

### Read the list

Use the list to spot patterns quickly:

* Short sessions with no products shown may indicate drop-off.
* Repeated CTAs can show which actions users take most often.
* Incomplete sessions can help identify friction in the flow.

Use flags to find risky or off-path sessions faster.

### Individual conversation view

Open any row to inspect the full conversation.

The conversation view shows the complete dialogue in order. It includes user messages and Sagent responses.

This view is read-only. You cannot take actions from this screen.

The conversation view can also include:

* Flags where triggered.
* Tool usage per Sagent response.
* Quality signals where available.

### Filters and retention

Use the selected date range to focus the conversation list on a relevant period.

Monitoring data is retained for 30 days.

Sensitive user data is masked in the conversation experience. Personal details should not appear in plain form.

Use shorter review cycles when investigating individual conversations. Data older than 30 days is unavailable in Monitoring.

### When to use Conversations

Use this tab after detecting a change in **Overview**.

It moves you from a trend to the underlying session behavior.

Use it to:

* Review flagged sessions.
* Inspect incomplete conversations.
* Confirm which tools were used.
* Understand why a CTA was or was not clicked.


---

# 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.crobox.com/how-to-guides/sagent/monitoring/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.