# Attributes

Attributes are available on the Diamond and Whale Plan\
\
There are several attributes that are pre-populated by Mava:

* Discord ID (Discord Ticket)
* Discord Role  (Discord Ticket)
* Telegram Username (Telegram Ticket)
* Device Type (Web Chat Ticket)
* Browser Language  (Web Chat Ticket)
* Page Origin  (Web Chat Ticket)
* Wallet  (Web Chat Ticket, if wallet is connected)
* Email (Web Chat Ticket, if email setting is on)

Any other attributes can be linked to form questions in [Mava's Chatbot](/mava-docs/getting-started/chatbot-builder.md), or automatically injected via the [web chat SDK](/mava-docs/getting-started/integration-setup/web-chat-setup.md). The data will be visible on the right hand side panel; agents can also edit the data from the panel. <br>

**Ticket vs User Attributes**

Ticket attributes are displayed on a specific ticket, whereas user attributes are displayed for each ticket the user opens. For example, if a support agent adds an email to a Discord ticket in "user attributes", and the same user opens another Discord ticket, their email will automatically be displayed.<br>

[**Use Cases**](#user-content-fn-1)[^1]\
\
As an example, you could ask a user what their company name is, and link it to an attribute called "Company Name".&#x20;

<figure><img src="/files/Frs9IHePGA6oTcPcyuEI" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="/files/WLcAlUhf4vsi547XyFCG" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="/files/nTIyb0ODDHyLgPGUVeLm" alt="" width="291"><figcaption></figcaption></figure>

Users on a premium plan can create unlimited custom attributes. <br>

[^1]:


---

# Agent Instructions: 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://mava.gitbook.io/mava-docs/getting-started/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.