> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/ui-customers/customers.md).
# Customers
Learn about the Customer object, equivalent to a CRM "Account," and set up custom fields before importing or adding your customers.
Customers in the Nalpeiron Growth Platform are equivalent to "Accounts" or "Companies" in your CRM system - your customers at a company level. This level can also be used in a B2C situation.
The Customer object corresponds to a company type level and has only a few basic attributes by default.
**We assume you will keep most of your customer data within your CRM system and link that back via the account ref ID we provide.**
However, if you wish to use the Nalpeiron Growth Platform as a more powerful tool for managing your clients and their entitlements, we offer a broad set of [useful fields](/zentitle2-docs/ui-customers/customers/adding-managing-customers/the-customer-page/fields-explained.md) to manage your customer data.
If we don't offer the field you need via the standard fields, we suggest adding all the fields you use in your business via the[ custom field feature.](/zentitle2-docs/ui-administration/configuration/custom-fields.md)
We suggest getting that right **before** you import or add any of your customers to the Nalpeiron Growth Platform.
---
# 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.nalpeiron.com/zentitle2-docs/ui-customers/customers.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.
