> For the complete documentation index, see [llms.txt](https://help.reekolect.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.reekolect.ai/reekolect-resource-center/frequently-asked-questions-faqs/analytics-faqs.md).

# Analytics FAQs

This section contains FAQs related to the Analytics section

<details>

<summary><strong>What do messages mean?</strong></summary>

Messages are the count of messages sent by a chatbot during a conversation. You are assigned a specific number of messages per billing period according to your plan that you can see on your dashboard.

</details>

<details>

<summary>What do Conversations mean?</summary>

Conversations are the unique chat sessions visitors engage with your chatbot during their visit. You can track your conversations with your dashboard and the inbox dashboard. A conversation terminates when a user closes the chat widget.

</details>

<details>

<summary><strong>How do we count messages?</strong></summary>

We count only the messages the chatbot sends to the bot user during any billing period. It will not count any messages sent by the user.

</details>

<details>

<summary><strong>What are the leads?</strong></summary>

The people who leave their contact information, like phone numbers and email addresses, are considered leads. A lead is part of qualified traffic on your website. These visitors have a high chance of purchasing your services or products.

</details>

<details>

<summary><strong>What is considered the lead?</strong></summary>

The visitors who leave their contact information, like phone numbers and email addresses, are leads with our chatbots. In your chatbot, you can mark any question for lead consideration. If the user replies to that question, it will be considered a lead.

</details>

<details>

<summary><strong>What is a subscriber?</strong></summary>

Anyone who interacts with Telegram, WhatsApp, and the Facebook bot is considered a subscriber. Subscribers are visible on your Analytics dashboard. You may find them as a contact as well.

</details>

<details>

<summary>How to check individual Bot uses or all account uses?</summary>

1. You can check out all users on your account in the Analytics. It has a detailed summary of both categories.
2. To Check All Bot Uses, Navigate To Analytics.
3. Find the "Analytics Summary" Tab
4. Change The Leftmost dropdown to all bots and the rightmost dropdown to the period you want (weekly, monthly, yearly)
5. To Check A Specific Bot Usage, Navigate To Analytics.
6. Find the "Analytics Summary" Tab
7. Change The Leftmost dropdown to the Bot you want to check for and the rightmost dropdown to the time period you want (weekly, monthly, yearly)

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.reekolect.ai/reekolect-resource-center/frequently-asked-questions-faqs/analytics-faqs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.