Custom Fields

Custom fields let each agency capture data unique to its operation — without a developer or a migration.

Defining a field #

Create a custom field with a label and type, and choose what it is for: a contact, a platform account or a team member. A contact or platform account field immediately becomes available on the forms it applies to (see Sub-agencies below). Values are stored per contact or per platform account, so different agencies can track entirely different things.

Using them #

Custom field values appear on the contact profile alongside the built-in fields. They're a good fit for things like internal IDs, referral sources, contract notes, or any attribute your workflow needs that isn't already a first-class field.

Sub-agencies #

A custom field can belong to a sub-agency. A platform account shows the fields of its sub-agency, and an account in no sub-agency (or in a deleted one) shows the fields with no sub-agency. A host's contact form shows the fields of each sub-agency they have an account in, and the fields with no sub-agency when one of their accounts is in none or they have no account yet.

People attached to a sub-agency see and manage only their own sub-agency's fields, on these forms and in the Custom Fields list, and can't create fields for team members. A field for team members always belongs to the whole agency.

Existing fields: what stops applying. Fields created before sub-agencies had their own have no sub-agency. A platform account in a sub-agency no longer shows them, and neither does the contact form of a host whose accounts are all in sub-agencies. Their values are kept: saving a form keeps the values of the fields it doesn't show, and they show again if the account leaves its sub-agency.

Related #

For categorization and segmentation, also consider Tags, which are filterable in messaging campaigns.