> 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-label.md).
# Interactions by label
Report of interactions by tags (TAGs).
#### Attendances by Tag
The report of **Attendances by Tag** organizes and analyzes attendances based on the applied TAGs, offering a clear view of the most recurring demands, usage patterns, and the areas that require greater strategic attention.
Main features and benefits:
* **Distribution by TAGs**: allows identifying which subjects concentrate the highest volume of attendances, such as functional doubts, flow errors, migrations or operational issues.
* **Prioritization view**: by understanding the most frequent categories, it becomes possible to direct improvements in automations, team training or even product adjustments.
* **Comparative analysis by users and departments**: allows filtering and understanding which areas of the organization are most impacted by certain types of attendance.
* **Efficiency mapping**: by monitoring TAGs such as “error”, “no show” or “mass completion”, managers can detect bottlenecks, implement action plans and raise the quality of the customer experience.
This report works as a **thermometer of critical topics**, allowing internal prioritization to be aligned based on real interaction data.
---
# 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-label.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.
