> ## Documentation Index
> Fetch the complete documentation index at: https://docs.raum.am/llms.txt
> Use this file to discover all available pages before exploring further.

# Conversations topics

Open **Chatbot → Conversations → Conversations** to review retained customer conversations and their operational state.

## Conversation list

The conversation list shows metadata without dumping message contents into every row.

Available context can include:

* visitor display name/identifier;
* widget/channel;
* conversation status;
* message count;
* escalation count;
* topic/category;
* sentiment;
* smart tags; and
* configured visitor telemetry.

Current status filtering includes **Open**, **Bot active**, **Escalated**, and **Closed**.

## Filters

The current view can filter by:

* Widget
* Status
* Topic
* Sentiment
* Smart tag
* Country
* Device
* Browser
* External entity

These filters are especially useful after enabling Topics and Visitor Data because you can move from an aggregate metric to the actual conversations behind it.

## Conversation detail

Select a conversation to review its retained detail.

Depending on the data still within retention, the detail can include:

* visitor information;
* transcript messages;
* message attachment records;
* handoff/escalation attempts and delivery status;
* topic/sentiment/confidence insight;
* smart tags;
* visitor telemetry; and
* attributed external entities.

The admin detail request is bounded. Very long conversations can indicate that not every message was loaded into one browser response.

## Insights

A finalized Chatbot insight can contain:

* category/topic;
* sentiment;
* summary;
* confidence; and
* processing/finalization state.

Topic processing behavior is configured under **Chatbot → Topics**.

## Escalations and delivery failures

Conversation detail records the handoff/escalation provider and delivery status where applicable.

The Conversations workspace also surfaces terminal failures for handoff delivery and deletion jobs so operational failures are not disguised as successful containment.

## Attachments

Messages can reference validated widget attachments while those files remain within retention.

Expired/deleted attachment content is not recreated merely because the conversation row still exists.

## External entities

When deterministic entity mappings are enabled, a conversation can be linked to external entities such as an order/account identifier derived from an approved source result or host-signed claim.

The classifier cannot invent those links.

[Entity mappings →](https://docs.raum.am/chatbot/entity-mappings.md)

## Export a conversation

Administrators with the required permission can export the selected retained conversation as JSON.

Export only what your organization is authorized to handle and protect the downloaded file according to your own data policy.

## Delete a conversation

Deleting a conversation **schedules** the purge rather than pretending a multi-resource cleanup is instantaneous.

The conversation is closed/revoked and the deletion job follows the configured grace period.

A legal hold blocks deletion.

[Retention, deletion & legal hold →](https://docs.raum.am/chatbot/retention.md)

## Failure queue

Terminal handoff/deletion failures can include states such as:

* Failed
* Dead letter
* Cancelled
* Blocked by legal hold

Review these operational failures rather than relying only on aggregate containment/handoff counts.

> **[Requests](https://docs.raum.am/chatbot/requests.md)**
>
> Work customer handoff submissions assigned to your team.

> **[Topics](https://docs.raum.am/chatbot/topics.md)**
>
> Configure classification, sentiment, smart tags, visitor data, and backfill.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.