The Analytics page of watsonx Assistant provides a history of chatbot conversations. You can use this history to improve how your assistants understand and respond to user requests and verify natural-language processing (NLP) chatbot performance.

Containment: Number of conversations in which the assistant is able to satisfy the customer's request without human intervention.

Coverage: Number of conversations in which the assistant is confident that it can address a customer's request.

Total conversations: The total number of conversations between active users and your assistant during the selected time period.

Average messages per conversation: The total messages received during the selected time period divided by the total conversations during the selected time period.

Total messages: The total number of messages received from active users over the selected time period.

Active users: The number of unique users who have engaged with your assistant within the selected time period.

Average conversations per user: The total conversations divided by the total number of unique users during the selected time period.

Retention rate: Percentage of users that return to using the chatbot in the given time frame.

Use your Action completion page to view all.

The Analytics Overview page provides a summary of chatbot interactions. You can view the amount of traffic for a given time period, as well as the intents and entities that were recognized most often in user conversations.

You can choose your metrics: whether to view chatbot data analytics for a single day, a week, a month, or a quarter. In each case, the data points on the graph adjust to an appropriate measurement period. For example, when viewing a graph for a day, the data is presented in hourly values, but when viewing a graph for a week, the data is shown by day. A week always runs from Sunday through Saturday. You can create custom time periods also, such as a week that runs from Thursday to the following Wednesday, or a month that begins on any date other than the first.

Chatbot chatbot analytics tools can measure the number of individual messages with weak understanding. These messages are not classified by an intent, and do not contain any known entities. Reviewing unrecognized messages can help you to identify potential dialog problems.

Use built-in metrics to analyze logs from conversations between customers and your assistant to gauge how well it's doing and identify areas for improvement.

The Analytics dashboard of watsonx Assistant provides a history of conversations between users and a deployed assistant. In this use case, history to measure the number of users interacting with your assistant.

A single conversation consists of messages that an active user sends to your assistant, and the messages your assistant sends to the user to initiate the conversation or respond. If your assistant starts by saying "Hi, how can I help you?", and then the user closes the browser without responding, that message is included in the total conversation count.

The Analytics dashboard of watsonx Assistant provides a history of conversations between users and a deployed assistant. You can use this history to determine the total number of conversations and messages.

To measure containment accurately, the metric must be able to identify when a human intervention occurs. The metric primarily uses the Connect to human agent response type as an indicator. If a user conversation log includes a call to a Connect to human agent response type, then the conversation is considered to be not contained.

A chatbot triggers a fallback message when it can't intelligently respond to a message it receives from a user.

By integrating with Watson Natural Language Understanding (NLU) you can measure sentiment analysis.

You can view the logs for a version of a skill that is running in production from the Analytics tab of a development version of the skill. As you find misclassifications or other issues, you can correct them in the development version of the skill, and then deploy the improved version to production after testing. See the page on improving across assistants for more details.