> 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/chat/groups.md).
# Groups
### How to create a group
1. Go to the menu **Chat**.
2. Click on the option **Groups**.
3. Select the icon **+** to create a new group.
1. Enter the **group name**.
2. Click **Send** to finish creating it.
### Configuring the group
After creating the group, click on the icon **Group Information** (letter **"i"**icon) to access the settings.
On this screen, you can:
* Change the group name;
* Set a description to make it easier to identify;
* Add or remove group members.
### Use in flows
If the group is used in platform automations, enable the option **`flow_visible`**.
When this setting is enabled, the group will be available for selection in flow actions, allowing its use in automations and routing.
### Group statistics
In the upper-right corner of the screen, click **Statistics** to view the group's performance indicators.
The available information includes:
* Average response time;
* Average wait time;
* Total messages received;
* Number of group participants;
* General summary of the support provided.
These metrics help track productivity, interaction volume, and group performance, making it easier to analyze operations.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.hablla.com/hablla-docs-en/chat/groups.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.