Settings
Custom Fields
Store additional client data for operators, templates, and automation.
Custom fields extend the client profile with additional data that matters to your workflow.
Use custom fields for IDs, campaign values, language, source, deposit status, account data, or any other client attribute your operators need.
Custom Fields Table
The Custom Fields page lists all configured fields.
| Column | Description |
|---|---|
| Name | The readable field name shown in the interface. |
| Key | The internal field key used in variables and automation. |
| Type | The data type: Text, Number, or Select. |
| Visible | Whether operators can see the field. |
| Editable | Whether operators can change the field value. |
| Actions | Edit or delete the field. |
Create a Custom Field
- Open Settings.
- Go to Custom Fields.
- Click Create Custom Field.
- Enter the field name.
- Set a unique key.
- Choose the field type.
- Decide whether the field should be visible.
- Decide whether operators can edit it.
- Save the field.
For a Select field, configure the allowed options. Operators choose from these values instead of entering free text.
Field Types
| Type | Operator input | Good for |
|---|---|---|
| Text | Free text | External IDs, source, language, notes, or status labels. |
| Number | Numeric input | Scores, amounts, counters, or account values. |
| Select | One configured option | Markets, stages, languages, or controlled statuses. |
Visibility and Editing
| Option | Meaning |
|---|---|
| Visible | Operators can see the field in the client context. |
| Editable | Operators can update the field value. |
Use Visible for data operators need during a conversation. Use Editable only when operators are allowed to maintain that value manually.
Use in Templates
Custom fields can be inserted into message templates with variables:
{client.customfield.<key>}Example:
Your player ID is {client.customfield.player_id}.See Message Variables for syntax details.
Best Practices
- Keep keys stable after creating a field.
- Use lowercase keys with underscores, for example
player_idorclick_id. - Avoid deleting fields that are used in templates or automation.
- Make sensitive fields visible only when operators actually need them.