> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/es/loyalty-manager/loyalty-concepts/customer-groups.md).

# Grupos de clientes

Este tema explica el papel de los grupos de clientes.

A **grupo de clientes** se utiliza para crear diversas comunidades de clientes con el fin de recopilar o canjear puntos de fidelidad. Al igual que los grupos de incentivos, los grupos de clientes pueden incluirse en (o excluirse de) los programas de acumulación o de canje.

Por ejemplo, es posible crear varios grupos de clientes y asignarles el estado Silver, Gold y Platinum. Cada grupo participaría en programas de acumulación que definen diferentes valores de puntos por dólar utilizando aceleradores o de otro modo.


---

# 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.rmhpos.com/es/loyalty-manager/loyalty-concepts/customer-groups.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.