> 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/interactions-by-user.md).
# Interactions by user
Consolidated report of completed interactions from D-1. Only interactions that were handled by an agent.
#### Attendances per User
The report of **Attendances per User** consolidates the completed attendances for each team member, allowing detailed analyses of individual performance and operational efficiency.
Main indicators available:
* **Number of attendances per user and sector**, enabling the assessment of workload and distribution among teams.
* **TMF (Average Time in Queue), TME (Average Wait Time) and TMA (Average Service Time)**, providing a granular view of the customer's journey in each interaction.
* **Satisfaction ratings (CSAT)**, highlighting the proportion of ratings ≥ 4, ensuring continuous monitoring of the customer experience.
* **FCR (First Contact Resolution)**, a strategic indicator of efficiency in resolving requests on the first contact.
* **Dynamic filters** by user, sector and period, allowing comparative analyses and identification of best practices or critical points.
This report is essential for **team management and individual accountability**, enabling the development of development plans, recognition of high performance and identification of training needs.
---
# 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/interactions-by-user.md?ask=&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.
