Contact Fields
Every contact has the same built-in fields. Anything else you keep about a person, such as a customer reference, an age or a policy type, is a field of your own, defined once and then available on every contact, in every import, and in your assistants' prompts.
Manage them at /client/contacts/fields, or click Fields above the contacts table.
Built-in fields
| Group | Fields |
|---|---|
| Identity | Title, First name, Last name, Phone, Email, Job title, Company |
| Address | Address line 1, Address line 2, Town or city, County, Postcode, Country |
| Contact preferences | Do not call, Do not text, Do not email |
Built-in fields cannot be renamed, retyped or removed. In a prompt or a tool they are {{contact.first_name}}, {{contact.postcode}} and so on. The page shows each one's reference under its name.
Contact preferences are recorded now and are not yet enforced. Enforcement arrives with outbound messaging.
Adding a field of your own
- Click New field.
- Give it a name, "Residential status" for example.
- Choose a type:
- Text: any short value.
- Number: whole or decimal numbers.
- Date: stored and shown as
YYYY-MM-DD. - Yes or no: a single true or false.
- Choice: one value from a list you set, one choice per line, each up to 120 characters. A value outside the list is rejected on save.
- Click Create field.
The name sets the field's reference, so "Residential status" becomes {{contact.custom.residential_status}}. The panel shows the reference as you type. The reference and the type are fixed once the field exists, so a value stored last month still means what it meant then. You can always change the name.
A name is limited to 80 characters. Two fields cannot derive the same reference, so names that differ only in punctuation or capitalisation, such as "Residential status" and "residential-status", will clash.
Ordering and archiving
Drag a field to change where it appears on a contact, in the column picker and in exports.
Archiving stops a field appearing on contacts, in imports and in pickers, and removes its column from the table. Values already stored on your contacts are kept. There is no delete, because removing a field would silently drop data you have already collected.
An archived field also leaves this page, so there is no list of archived fields and no way to bring one back. Archive only when you are sure.
An archived field still holds its reference, so you cannot create a new field that would derive the same one. Pick a different name.
Using your fields
- In a prompt:
{{contact.custom.residential_status}} - In a tool: the same reference, in the body, a header or the URL
- In the contacts table: switch the column on under Columns, in the Your fields group
- In an import: map a column to the field, or create the field from the matching step