When to use it
- You need to record specific data per conversation (e.g.: contact reason, category, resolution deadline)
- You need to record specific data per contact (e.g.: birthday, plan, tier)
- You want to use these fields later in automations, macros or dynamic variables
Prerequisites
- Be logged in as an administrator in Cloud Chat
About this tutorial
In this article you will learn how to create custom fields (custom attributes) for contacts and conversations in Cloud Chat.
Step by step
Step 1 — Access Custom Attributes
- Go to "Configurações" (Settings)

- Select "Atributos personalizados" (Custom attributes)

You will see the custom fields for Conversations and Contacts:


Step 2 — Create the custom attribute
- Click on "Criar o atributo personalizado" (Create custom attribute)

-
Choose the scope: Contact or Conversation
-
Set a name (e.g.: "birthday") and a key
The key is generated automatically from the name, but you can change it. It works as a unique identifier — we recommend keeping the generated one unless you need something specific.
If you want to create fields on conversations that only appear under specific conditions (for example, depending on the value of another field), see Conditional conversation custom attributes.

Step 3 — Configure type and description
-
Add a description (e.g.: "this is the customer's birth date")
-
Choose the field type:
-
Text
-
Number
-
Link
-
Date
-
List
-
Multiple list
-
Checkbox (yes or no)
-

- Click on Create
Your custom field is created and available for use in conversations/contacts, automations and macros.

Notes
-
To validate the field content with a regular expression: Validation with regular expressions (REGEX) in custom fields
-
To create conditional fields that only appear under certain rules: Conditional conversation custom attributes
-
To use these fields in automations: How to manage automations in Cloud Chat
-
To use them in macros: How to use macros with custom attributes in Cloud Chat
-
To update attribute values via API: How to update custom attributes on conversations via API