> 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/store-manager/manage-customers/setting-up-customer-policy.md).
# Create a customer policy
Use a customer policy to identify mandatory fields for customers or a required telephone number format.
{% hint style="info" %}
If you create a customer policy, it is only applied to new customers added in POS or Store Manager. It is not applied to existing customers. When new customers are added, if mandatory fields are not filled out or the telephone number does not conform to the required format, the **Save** button is disabled in POS and an error message displays in Store Manager. Each store can set up and use its own unique customer policy.
{% endhint %}
1. Click **Setup**.
2. Expand **Customer**.
3. Click **Customer Policy**.
4. On the **Options** tab, select all of the fields that should be mandatory for new customers.
5. (Optional) On the **Mask** tab, define the required telephone number format.
Use # to represent the number of required digits for the country code, area code, or telephone number. Add any other formatting requirements, such as dashes. For example: ###-###-###-#### or 1-###-###-####. There are no restrictions on the number of digits you use for the country code, area code, or telephone number. However, you can only enter a maximum of 30 characters in the field.
6. Click **Save and Close**.
If you selected required fields, they are identified by a \* and bold text:
If you defined a mask, prompts display on screen to help cashiers and store managers enter telephone numbers in the required format:
---
# 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.rmhpos.com/store-manager/manage-customers/setting-up-customer-policy.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.