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

# Analytics

> Aggregate your AI agent's activity into chats, topics, sentiment, and helpdesk metrics over time

## Overview

**Analytics** aggregates the activity of your AI agent across conversations. It has four pages: **Chats**, **Topics**, **Sentiment**, and **Helpdesk**. By default it shows the activity for all AI agents in your workspace for the last week.

<Card title="What you can do:" icon="chart-scatter">
  See volume, subject matter, and mood at a glance, and tell whether the changes you made last week actually moved anything.
</Card>

<Note>
  **Analytics** aggregates the information, including topics, sentiment, and thumbs down. [Activity](/docs/user-guides/chatbot/activity) shows the data per conversation instead.
</Note>

## Chats

<Frame>
  <img src="https://mintcdn.com/chatbase/iDwh2_Jn2DqKxWHv/user-guides/chatbot/images/analytics/analytics-1.jpg?fit=max&auto=format&n=iDwh2_Jn2DqKxWHv&q=85&s=5fcf694a83c04ff09de740a534b55416" alt="The Chats page in Analytics" width="2528" height="1502" data-path="user-guides/chatbot/images/analytics/analytics-1.jpg" />
</Frame>

The top of the page shows the resolution rate, the total number of chats, total number of messages, the messages that got a thumbs up and a thumbs down, daily active users, weekly active users, and stickiness.

Below the totals, a line chart plots chats over the selected period against the **Previous period** (the dotted line), so you can see whether volume is rising or falling. Hover any point to compare the two dates directly.

**Resolution rate:** The percentage of conversations your agent resolved independently, without creating a ticket or escalating to live chat.

**Chats by country** shades a world map by volume and lists the top countries beside it, with **View all** for the full ranking. Countries are detected from the IP of the users having conversations with the AI agent.

<Frame>
  <img src="https://mintcdn.com/chatbase/vNSeL3jbWe38rTUa/user-guides/chatbot/images/analytics/analytics-2.png?fit=max&auto=format&n=vNSeL3jbWe38rTUa&q=85&s=65f29ccc8b91c66487d18de92ae8b63a" alt="Chats by country, shown as a shaded world map" width="2528" height="1502" data-path="user-guides/chatbot/images/analytics/analytics-2.png" />
</Frame>

**Chats by channel** breaks the same total down by where the conversations came from, such as Widget/Iframe, Playground, or Slack.

**Action calls** ranks how often each of your actions ran over the period, with **View all** for the complete list. It is a quick way to see which actions your AI agent actually uses.

Each panel uses the visualization that suits it: a line chart for chats over time, a shaded world map for **Chats by country**, and horizontal bars for **Chats by channel** and **Action calls**.

### Filtering

You can filter the data by date, using pre-defined ranges such as last 7 days, last 30 days, last 3 months, and last year.

<Frame>
  <img src="https://mintcdn.com/chatbase/4pjz3jKY2rJqVh9o/user-guides/chatbot/images/analytics/analytics-filter.png?fit=max&auto=format&n=4pjz3jKY2rJqVh9o&q=85&s=452eec1a9cb0686ca04f73b37412fa3f" alt="The date filter options in Analytics" width="2528" height="1502" data-path="user-guides/chatbot/images/analytics/analytics-filter.png" />
</Frame>

## Topics

This page shows the topics that came up in conversations and were mentioned by users. Topics are detected automatically by the AI agent.

<Frame>
  <img src="https://mintcdn.com/chatbase/4pjz3jKY2rJqVh9o/user-guides/chatbot/images/analytics/analytics-topics-new.png?fit=max&auto=format&n=4pjz3jKY2rJqVh9o&q=85&s=7d732202848f9d692117c5ab1725910c" alt="The Topics page in Analytics" width="2528" height="1502" data-path="user-guides/chatbot/images/analytics/analytics-topics-new.png" />
</Frame>

Available actions:

* Search topics
* Add topic
* Edit topic
* Delete topic
* **Freeze topics:** stops the AI agent detecting any new topics automatically

You can also add topics manually, using the **View All** button on the right of the page.

<Frame>
  <img src="https://mintcdn.com/chatbase/4pjz3jKY2rJqVh9o/user-guides/chatbot/images/analytics/analytics-4.png?fit=max&auto=format&n=4pjz3jKY2rJqVh9o&q=85&s=2db0be4be3ab69f4f8a8655504ca0d0c" alt="Adding a topic manually from the View All screen" width="2528" height="1502" data-path="user-guides/chatbot/images/analytics/analytics-4.png" />
</Frame>

## Sentiment

This page shows how the AI agent detects the sentiment and emotion of users during conversations. Sentiment analysis is detected automatically by the AI agent.

<Frame>
  <img src="https://mintcdn.com/chatbase/4pjz3jKY2rJqVh9o/user-guides/chatbot/images/analytics/analytics-sentiment-new.png?fit=max&auto=format&n=4pjz3jKY2rJqVh9o&q=85&s=20db7c6696c99bdc6b1eb5db6d4b516b" alt="The Sentiment page in Analytics" width="2528" height="1502" data-path="user-guides/chatbot/images/analytics/analytics-sentiment-new.png" />
</Frame>

## Helpdesk

Track ticket volume over time to monitor your support workload and resolution trends. Every metric on this page shows its change against the previous period, and each chart plots the **Selected period** as a solid line against the **Previous period** as a dotted one.

<Frame>
  <img src="https://mintcdn.com/chatbase/4pjz3jKY2rJqVh9o/user-guides/chatbot/images/analytics/helpdesk-analytics.png?fit=max&auto=format&n=4pjz3jKY2rJqVh9o&q=85&s=e414639dd9d097dd94a39ee75d46f31e" alt="Helpdesk in Analytics" width="2530" height="1496" data-path="user-guides/chatbot/images/analytics/helpdesk-analytics.png" />
</Frame>

### Team member performance

The table at the top of the page breaks the period down by team member, so you can see how the workload is spread across your human agents:

* **Solved tickets:** tickets that member marked solved.
* **Tickets replied:** tickets they replied to at least once.
* **Replies sent:** the total number of replies they sent.
* **Median first response time:** how long customers waited for that member's first reply.
* **Median response time:** the median across all of their replies.
* **Median time to close:** how long their tickets stayed open before being solved.

Every column is sortable. Scroll the table sideways to reach the columns that don't fit on screen. The **All agents** row totals the counts for the whole team, and a dash means there is no data for that member in the selected period.

### Ticket volume

* **Created tickets:** tickets opened during the period.
* **Solved tickets:** tickets marked solved during the period.
* **Unsolved tickets:** the outstanding backlog, plotted on its own chart so you can see whether it is growing or shrinking.
* **Agent replies sent:** replies sent by human agents during the period, charted beside Unsolved tickets. Internal notes, automated messages, and AI agent replies are excluded.

### Response times

* **Median first response time:** how long a customer waits for the first human reply.
* **Median response time:** the median across all replies, not just the first.
* **Median time to close:** how long a ticket stays open before it is solved.

Medians are used rather than averages, so a handful of long-running tickets don't skew the figure. A chart below the three tiles plots response time across the period.

### Tickets by channel

Breaks ticket volume down by where the tickets arrived from, such as **Email**, **Widget/Iframe**, or **API**.

### Customer satisfaction (CSAT)

Shows how customers rated the support they received, based on the [satisfaction surveys](/docs/user-guides/chatbot/help-desk/satisfaction-surveys) sent after tickets are closed. Each figure shows its underlying counts and its change against the previous period.

<Frame>
  <img src="https://mintcdn.com/chatbase/LLYBc5rL9oYZui8P/user-guides/images/help-desk/satisfaction/analytics-card.png?fit=max&auto=format&n=LLYBc5rL9oYZui8P&q=85&s=52988fdfa7aa6447c93d1aae3af41add" alt="Customer satisfaction card in Helpdesk analytics" width="2576" height="912" data-path="user-guides/images/help-desk/satisfaction/analytics-card.png" />
</Frame>

* **CSAT score:** answers rated Good as a share of all answers.
* **Response rate:** answered surveys as a share of surveys sent.
* **Coverage:** surveys sent as a share of closed tickets that could have been surveyed.

Figures are grouped by the day the survey went out, so a late answer counts toward that day. **View all** lists the individual answers with their comments, the ticket they belong to, and the teammate who handled it, along with a breakdown of tickets that were not surveyed and why.

### Filtering

Use the date range picker to set the period. The filter button beside it narrows the whole page by **Assignee**, **Channel**, **Type**, or **Last message by**. Pick a field, choose an operator such as **is any of**, then select the values and click **Apply**. **Discard** clears the filter you were editing.

## Limitations

* **Data is updated with a 1-day delay,** reflecting the previous day's information.
* **Data is only recorded once you subscribe to a plan.** Topics and sentiment are only available after the upgrade, and anything from before it is not included.
* **Message totals and credits are counted differently.** The page shows the total number of messages, including all conversation messages, but credits are only calculated for AI-generated responses, excluding the initial messages.

## Next steps

<CardGroup cols={2}>
  <Card title="Activity" icon="chart-area" href="/docs/user-guides/chatbot/activity">
    Read the individual conversations behind these totals.
  </Card>

  <Card title="Usage" icon="chart-line" href="/docs/user-guides/workspace/usage">
    Track message credits consumed across your AI agents.
  </Card>

  <Card title="Help Desk" icon="headset" href="/docs/user-guides/chatbot/help-desk/help-desk-overview">
    Work the tickets these helpdesk metrics are measuring.
  </Card>

  <Card title="Best Practices" icon="star" href="/docs/user-guides/quick-start/best-practices">
    Act on what the numbers tell you about answer quality.
  </Card>
</CardGroup>
