# Dashboard

If you don't see any data in the overview, you might be viewing the **DRAFT** data of your unpublished bot. Your customers are interacting with the [**LIVE** or published version](/publish/publishing-your-bot.md). Switch your filter to **LIVE** to see actual customer data. 

{% hint style="info" %}
Not familiar with analytics? We recommend that you have a look at our [Analytics concepts](/bot-answers/definitions.md).
{% endhint %}

## Filtering

<figure><img src="/files/JavgU8jwgARxNyAkRAzU" alt=""><figcaption><p>Filtering features for your Analytics dashboard.</p></figcaption></figure>

Use these filters to customize the dashboard view and create specific insights for your bot, helping you monitor its progress over time:

* **All channels** allows you to filter on specific channels.
* **All languages** shows information about your bot in different languages.

{% hint style="info" %}
The timestamp of the data you see in the analytics dashboard is based on the timezone of your browser.
{% endhint %}

## Analytics overview

### Customers

The [**Customers**](#customers) tab in Analytics allows you to check your new and returning customers.

<figure><img src="/files/xB26RzX0rvqhdnbSwDTp" alt="" width="375"><figcaption><p>Customers analytics.</p></figcaption></figure>

### Conversations

The [**Conversations**](/navigation/analytics/conversations.md) tab shows the distribution of bot conversations in all available languages.&#x20;

{% hint style="info" %}
[Switching from **Languages** to **Channels** ](#filtering)will show the use of the bot over different channels (if these are used of course).
{% endhint %}

<figure><img src="/files/g0G9T6nZAJQWRC563ICE" alt="" width="375"><figcaption><p>Conversations analytics.</p></figcaption></figure>

[**Conversations**](/navigation/analytics/conversations.md) also display the proportions of conversations with handover, average number of messages and time spend.

<figure><img src="/files/PjSeUR25FJ8e9e3Z4bis" alt="" width="375"><figcaption><p>Conversations analytics.</p></figcaption></figure>

{% hint style="warning" %}
Is the number of conversations in the Dashboard different from the number of conversations in the conversation [**History**](/navigation/history.md)? That's because in **Analytics**, we show all conversations, whereas in the **History** overview, we only include conversations where the user actually replied.
{% endhint %}

### User messages

<figure><img src="/files/qvxEKNeMDtkloyecFnz3" alt="" width="375"><figcaption></figcaption></figure>

The **User messages** tab takes you to the [Conversations](/navigation/analytics/conversations.md) page with an overview of how many messages are understood, not understood, or clicked.

### Top intents

The top intents tab is showing the top 5 triggered intents most often, including the number of calls and their percentages. Clicking on **Details** in the right upper corner will bring you to the [**Intents** ](https://docs.chatlayer.ai/bot-answers/analytics/intents)page.&#x20;

<figure><img src="/files/Elz4El2GLrZx1fTWb3Mi" alt="" width="375"><figcaption><p>Top intents analytics.</p></figcaption></figure>

### Customers activity

Customers activity gives an idea of when your users are interacting the most with the bot throughout the day.

<figure><img src="/files/9AAv3tVg7sVKe0gGoz0j" alt="" width="375"><figcaption><p>Customers activity analytics.</p></figcaption></figure>

### Customer flow

The [**User flow**](/navigation/analytics/user-flow.md) tab gives an overview of the user journey through the bot.

<figure><img src="/files/LwwBQZVQSZA1Lx97Vjnc" alt="" width="375"><figcaption><p>User flow analytics.</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.chatlayer.ai/navigation/analytics/dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.