> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/reports/hablla-reports-and-logs.md).

# Hablla Reports and Logs

Hablla's reports are designed to transform operational data into **actionable insights**, connecting Marketing, Sales, Support and Customer Success from the perspective of **Conversation Revenue**.

#### 1. Consumption

* **Messaging Sessions** → Volume of opened conversation windows.
* **Flow Executions** → Real-time monitoring of automations.
* **Total AI Consumption** → Tokens consumed per AI model, transcription time and usage distribution (ideal for cost optimization).

#### 2. Service Interactions

* **Service Times** → SLA, queue time, bot time and average handling time.
* **Interactions per User** → Individual performance comparison: CSAT, FCR and productivity.
* **Interactions by Tag** → Grouping of interactions by TAGs (e.g.: error, support, sales).
* **Interactions by Closure Reason** → Analysis of closures (issue resolved, no response, not interested etc.).

#### 3. Leads and People

* **People by Tag** → Engagement and contact segmentation (Onboarding, Workspace created, Referral).

#### 4. Tasks

* **Tasks per User** → Management of individual deliveries, efficiency and delays.

#### 5. Logs

* **User Logs** → Record of availability, unavailability and reasons (absence, high demand etc.).

***

💡 **Strategic insight:** This reporting structure ensures a 360º view of the operation, enabling everything from **granular control** (e.g.: average response time) to **macro performance analysis** (e.g.: AI usage by model, departmental efficiency, reasons for losing leads).

Thus, the manager can act in a **proactive**, adjusting conversational journeys, allocating resources and prioritizing improvements that directly impact conversational revenue.


---

# 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://docs.hablla.com/hablla-docs-en/reports/hablla-reports-and-logs.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.
