Skip to content

Custom fields

Every business asks its customers something the CRM does not ship with — a coaching centre asks which course, a property dealer asks the budget range, a travel agent asks the travel dates. Custom fields are how you add those questions.

Read "What you cannot change later" before you create your first field. Two things freeze permanently and catch people out.

Before you start

  • You need the tenant.custom_fields.manage permission.
  • Decide the type before you create it. See the warning below.

Steps

  1. Go to Settings → Custom fields.
  2. New field, then set:
Setting Notes
Label What your team sees. Can be changed later, freely
Attaches to Lead, Contact or Deal
Type See the list below. Permanent once answered
Required Whether the form refuses to save without it
Default Pre-fills the create form. It is not written to records that arrive from an import or the API
Options For Choice fields
  1. Save. The field appears on that record's form immediately.

The field types

Twelve are available:

Type Use for
Text A short answer
Long text A paragraph
Number A whole number
Decimal An amount. Four decimal places
Date A date
Date and time
Yes / No See the note below
Choice One option from a list
Multiple choice Several options
Email
Phone
Link Shown as a clickable link

Yes/No shows three options, not a tick box. A tick box cannot tell "No" from "Not answered", and those are different facts about a customer. So you get Yes, No, and blank.

Not available yet. File upload, currency, address, and fields that link to another record. Nine of the twenty-one types in the system have storage but no way to fill them in yet.

Contacts are different

Contacts have no create or edit form — a contact is the identity that lead capture, calls and WhatsApp resolve to, so nobody types one in. A contact custom field is answered on the contact's profile page instead.

What this affects elsewhere

  • The field appears on the create and edit forms for that record type.
  • Answers show on the record's detail page.
  • The API accepts and stores them on leads.

Not available yet. Custom fields in reports, filters and exports. The answers are stored and readable on each record, but you cannot yet filter a list by one or include one in an export.

What you cannot change later

The type and what it attaches to freeze the moment anybody answers. Both decide how every stored answer was interpreted when it was written — "Yes" in a Yes/No field cannot be read back as a date. The screen blocks the change rather than performing it. If you need a different type, create a new field; the old answers stay readable.

Renaming is always free. Nothing stores the wording, so every answer stays attached. Rename as often as you like.

A field with answers cannot be deleted — only switched off. A switched-off field leaves the forms and still shows its answers on records that have one, marked no longer asked.

An option that records are using cannot be removed. Relabelling an option is fine and flows through to every record that chose it.

If it does not work

What you see What it means What to do
You cannot change the type Something has already answered it Create a new field
You cannot delete the field It has answers Switch it off instead
You cannot remove an option Records are using it Relabel it, or leave it
The field is not on the contact form Contacts have no form Answer it on the contact's profile
1.23456 was refused Decimal holds four places Enter four, or use Text

Last checked against the product on 2026-10-10. Needs the tenant.custom_fields.manage permission.