> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/admin/customer/customer-group/creating-customer-groups.md).
# Creating Customer Groups
Creating and managing customer groups allows you to tailor their strategies and communications based on different customer segments.
{% hint style="info" %}
To create an customer group, go to: ***Menu > Admin > Customer > Customer Group***
{% endhint %}
In the Customer Group module, enter the name of the customer group and click on "**Save**" to create the customer group.
All the customer groups created in the system will be listed in the Customer Group Centre.
### Assigning Customer Group
After creating a customer group, the next step is to assign it to your customers. Follow these steps to efficiently categorize your customers into their respective groups.
1. Open the desired customer profile you wish to assign to a group.
2. Go to the **"Other Info"** tab within the customer's profile.
3. From the **"Customer Group"** dropdown, select the customer group.
4. Click **"Save"** or **"Update"** to finalize the assignment of the customer to the selected group.
---
# 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.xorosoft.com/xoroerp-1/admin/customer/customer-group/creating-customer-groups.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.
