5. Manage contact attributes
Contact attributes store structured information your team needs, such as a service plan, renewal date or collection preference. Use them when a label alone would not capture enough detail.
An Admin defines fields in Settings → Contact attributes. Staff can edit their values on individual contacts.
Attribute creation
- Select New attribute.
- Enter Name and a Key of up to 63 lowercase letters, digits or underscores, starting with a letter.
- Choose Type.
- For List, add the permitted Options.
- Select Save, then open a contact to populate the field.
Attribute types
| Type | Example value |
|---|---|
| Text | Preferred workshop: Riverside |
| Number | Number of bicycles: 2 |
| Date | Renewal date: 2026-12-01 |
| Boolean | Collection requested: true |
| List | Service plan: Annual, selected from defined options |
Keys and validation
Names and keys identify the definition; the key must be unique within the business. Custom field values are not automatically unique customer identifiers. The current editor does not offer a required-value or unique-value switch. Built-in contact details such as Name, email and phone have their own identity and validation rules.
Editing definitions
Open the definition to edit its name, type or list options. The key is fixed after creation. Changing a type or options updates the definition; it does not provide a conversion wizard for existing values. Review populated contacts before making a change that would make their values unsuitable.
Attribute deletion
Deleting a definition removes its stored values from contacts. It does not delete the contacts. There is no restore action for the removed field values.
Attribute values
Populate values through:
- The contact editor.
- Supported attributes in signed widget identity tokens.
Contact CSV import and a general public API-key workflow are not available. Tags describe categories; attributes store structured values. Neither creates an assignment rule automatically.
Related guides: Contacts, Tags, Widget identity.