> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/documentation/sales/customer/customer-attributes.md).

# Customer attributes

### What are Customer Attributes?

Customer attributes let you add extra fields to your customer records. Think of them as custom notes or tags where you can store information that matters to your business - things like internal reference numbers, Azure tenant IDs, or the name of the person who manages each account.

### Why would you use them?

Sometimes the standard customer fields don't cover everything you need to track. Maybe you work with reseller partners and need to note which partner handles each customer. Or perhaps you manage Azure subscriptions and want to keep tenant IDs handy. That's where custom attributes come in.

You get three slots to work with, and you can name them whatever makes sense for your setup.

### Setting up your attributes

Getting this configured is pretty straightforward:

Go to **Portal Settings > Customer Settings > Customer Attributes**

From there, you can:

* Name your three attributes
* Edit the names anytime using the pencil icon
* Show or hide them using the eye icon

The settings apply across your whole company, so everyone sees the same fields. When you hide an attribute, the data stays there - you're just tucking it out of sight temporarily.

<figure><img src="/files/cUqkCNHAv3XO0dUVvYPw" alt=""><figcaption></figcaption></figure>

### Real-world examples

Here's how companies typically use these:

**Tracking resellers**\
Set up an attribute called "Reseller" and note which partner company manages each customer. Makes it easy to see who's responsible at a glance.

**Azure tenant IDs**\
If you're managing Microsoft cloud services, you can store the Azure tenant ID right in the customer record. No more hunting through spreadsheets.

**Contact names**\
Keep track of the main person you work with at each customer. Could be "Account Manager", "Primary Contact", or whatever label fits your workflow.

### Where you'll see them

Once configured, these attributes show up in:

* The detailed customer view
* Your customer list
* Anywhere you're managing customer information

<figure><img src="/files/fPpkbLmg0fuiY7bIdn1Y" alt=""><figcaption></figcaption></figure>

### Things to keep in mind

You can only set up three attributes, so choose wisely. Think about what information you find yourself looking up repeatedly - those are good candidates.

The configuration works company-wide. You can't have different attributes for different teams or users.

Hidden attributes keep their data. If you hide something and show it again later, all the values will still be there.

### Common questions

**Can I add more than three?**\
Not right now. The limit is three custom attributes per company.

**What if I change an attribute name?**\
The name changes but all the saved data stays the same.

**My attributes aren't showing up**\
Check that they're set to visible (eye icon should be open, not crossed out).

### Quick tips

Pick clear, descriptive names that your whole team will understand. "Contact" is better than "C1".

You don't have to use all three slots. If you only need one or two, that's fine.

Think about consistency. If you're storing phone numbers in one field, use the same format across all customers.

Hide attributes you're not actively using to keep things tidy, but remember they're still there if you need them later.

<br>


---

# 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:

```
GET https://hub.equipme.io/documentation/sales/customer/customer-attributes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.