Version: Latest

Conversation Review

Conversation Review allows you to review conversations users have had with your assistant. It helps you detect patterns in conversations that might explain why certain skills are not working well—whether due to bad design, limited scope, bad routing, or implementation error.

Conversation View is available for both CALM and NLU-based assistants.

Configure Rasa Pro assistant for Conversation Review

In order for Studio to display conversation data, you need to configure your Rasa Pro assistant to send conversation data to Studio via a Kafka broker. Make sure that your assistant and Studio are both connected to same Kafka instance and are listening to the same topic. Look here to know more about Kafka configuration in Rasa Pro. Make sure the that assistant_id field in the config.yml of your Rasa Pro assistant is set to the same value as the assistant name in Studio.

Getting started

Choose an assistant from the dropdown menu in the left navigation bar.

image

Select Conversation Review in the left navigation bar.

image

You will now see Conversation Review’s Conversations Table

image

Conversations Table

The Conversations Table lists all conversations your assistant has had with your users. By default, the Conversations Table shows the 100 most recent conversations occurring within the last seven days, sorted by descending start time.

The Conversations Table has the following columns:

Column NameDescription
Conversation IDThe unique ID associated with a user conversation. Also called a Session or User ID.
Session StartThe timestamp for the first event in the conversation session. Note that the session start time in the Conversations Table and the session start time elsewhere may differ: Studio auto-adjusts the default UTC timestamp to reflect the time in your local timezone.
TagsTags associated with the Conversation ID that you or your teammates have added.
MessagesThe number of messages the user sent during the conversation.
ReviewedWhen you or another user has viewed a conversation and marked it as reviewed, a green checkbox will appear in this column.

Filters

Applying filters to the Conversations Table helps you quickly identify conversations that need analysis. To access filters, click the Filters icon in the top left corner of the Conversations Table.

image

The following filters are available:

Column NameDescription
TimeframeThe timestamp for the first event in the conversation session
Conversation IDThe unique ID associated with a user conversation.
Predicted IntentThe intents predicted during the course of the conversation.
Flow (CALM assistants only)The Flows started during the course of the conversation.
TagsTags associated with the Conversation ID.
Reviewed conversationsWhether or not a conversation has been reviewed.

Conversation Details Panel

The Details panel shows session, user and event data that will help you with conversation evaluation. The panel shows the following session-level data for every conversation:

image
Column NameDescription
Conversation IDThe unique ID assigned to the conversation you are viewing.
Session StartThe timestamp for the first event in the conversation session.
Model IDThe unique ID assigned to the model your assistant is using.
ChannelThe channel where the conversation took place.
User MessagesThe total number of user messages sent during the session.
Flows (CALM assistants only)The Flows started during the course of the conversation.
Flows attributesThe attributes associated with the Flow.
Predicted intents (NLU assistants only)The intents predicted during the course of the conversation.
Predicted entities (NLU assistants only)The entities predicted during the course of the conversation.
TagsTags associated with the Conversation ID.

Adding Tags

The Details section is also where you can append tags to the conversation you’re reviewing. Scrolling to the bottom of the details panel will allow you to add and delete tags associated with a Conversation.

Learn more about tags and how to use Tags.

Conversation Stream

The Conversation Stream is a turn-by-turn breakdown of the conversation you selected for review. Clicking on messages, responses and certain event types will show you more information in the Details panel.

User Messages

User messages are shown on the right hand side of the stream. Clicking on a message will show more details about the message in the Details panel:

  • Message timestamp: The time at which the message was sent.
  • Message ID: The unique ID of the user message.
  • Message in conversation: The sequential number of the message in the conversation.image

If you are analyzing an NLU assistant, you will also see:

  • Predicted intents with confidence scores

Events

Slot and Flow events are represented with a colored banner. Clicking on the banner reveals additional details about the events.

Slot events

Slots are your bot's memory. They store information a user has provided (for example, their name or phone number) or information the assistant can access about the user (for example, their account ID or device in use). The bot can then refer to this information throughout the conversation. When a slot is set during the course of a conversation, you will see a yellow banner. Clicking on the banner will show more details about the set slot in the Details panel:

  • Event timestamp: The time at which the Slot event took place.
  • Event ID: The unique ID associated with the event.
  • Event in Conversation: The sequence of the event in the conversation.
  • Slot Name: The name of the slot that was set.
  • Slot Value: The information about the user or conversation that is now stored in the slot.image

Flow events (CALM assistants only)

CALM assistants are powered by Flows. Flows are abstract representations of the business processes your assistant completes. If you are analyzing a conversation with a CALM assistant, you will see the following Flow events:

  • Flow started: The assistant started a Flow in response to a user question.
  • Flow interrupted: The Flow stopped before completion. It will continue once the interrupted flow is finished.
  • Flow resumed: The Flow restarted after stopping. Flow restart at the point where it left off.
  • Flow completed: The Flow was completed within the session window.
  • Flow cancelled: The user cancelled the Flow during the conversation session.

When a Flow event happens during the course of a conversation, you will see a blue banner. Clicking on the banner will show more details about the Flow event in the Details panel:

  • Timestamp of event: The time at which the Flow event took place.
  • Event ID: The unique ID associated with the event.
  • Event in Conversation: The sequence of the event in the conversation.
  • Flow name: The name of the Flow.
  • Flow event type: The type of Flow event triggered.image

Conversation Tags

Tags are a way for your team to supercharge your review workflows.

Imagine a scenario where you are analyzing a conversation between a user and a weather app assistant. During the conversation, the user requested information on the pollen index for their zip code. However, the assistant was designed to only answer questions directly related to weather events, and so the question triggered the assistant’s fallback behavior. With tags, you could:

  • Batch this conversation with similar ones by assigning a tag like out-of-scope to denote the user asked a question outside of the assistant’s domain
  • Batch this conversation with similar ones by assigning a tag like topic-pollen-index to denote the user asked a question related to the pollen index for their location
  • Specify what action the team should take next by assigning a tag like needs-further-analysis, implement-behavior, or a even a knowledgeable teammate’s name.imageThese conversations can then be easily surfaced in the Conversations Table.

Automatic Conversation Deletion

To manage data retention and ensure compliance with data protection regulations, old conversations can be automatically deleted periodically. Learn more about automatic conversation deletion

Conversations via API

For developers looking to programmatically tag and delete conversations, please refer to our Conversations API Documentation.