Field and rule types reference

Field types

The same types are used for what you store about your own records and for what the bot asks a lead. The picker shows the names in the first column; the second is the name the API uses.

What a lead says is read more loosely than what you type into a record form:

• A number or an amount written as the lead writes it ("50k", "2 lakh", "€3.000") is read as the number they meant. Amounts are read in your workspace's currency; money in another currency is not stored or converted (Intake fields). A money question set "per month", "per day" or "per hour" records only an amount that names that period, or one that converts exactly (a year to a month is divided by 12). A bare "around 60k" the lead volunteers is not recorded: the assistant asks which period they mean. An amount that answers the "how much per month?" question is recorded as that period.
• A choice is matched to one of your active options, ignoring case, and a close wording ("lower back" for "Lower back pain") still lands on it. A reply that matches nothing is not recorded, and the bot asks again.
• Text, email, phone and links are kept as the lead wrote them. The minimum, maximum and length limits under More on a question are not checked against what a lead says.

Photos (IMAGE)

A record can hold up to 4 photos in each Image field, and your workspace up to 200 in all. A photo is a JPEG or PNG of at most 5 MB; the dashboard turns and shrinks whatever you choose (an iPhone's HEIC works in Safari), and removes a phone's location. The first photo is the record's cover. The type is offered only for your records' fields, because a lead cannot send a photo through a question yet. A field that holds photos cannot be renamed or changed to another type; add a new field instead. All of it is in Adding photos to your records.

Currency is stored in cents

Whole cents, always, with no fractional part. 50,000 is stored as 5000000.

The dashboard converts for you: you type what you mean and read what you meant. A qualification rule's number is typed in whole units everywhere, on the rule's card and in its full edit form alike: a minimum budget of 50,000 is typed as 50000 and stored as 5000000. The storage format only becomes visible in one place, and it catches people out —

• Imports and API calls, where nothing converts for you.

Integers rather than decimals is deliberate: a price that is the sum of three numbers should not depend on how a floating-point number rounded.

What a lead may see of a record

A lead sees a record's name, and only the fields you switch on, and only when you have turned on showing options.

• On your records' fields page there is a Lead can see switch on each field. It starts off everywhere. A field your template suggests is marked Suggested, and is only ticked for you on the to-do card; it is not shown until you say yes.
• An IMAGE field has the switch too. It is how photos reach a lead: the first photo of the first Image field a lead may see goes with each option (Pictures). A new Image field starts on when options are on.
• EMAIL and PHONE fields have no switch and can never be shown to a lead. The product refuses the request if it is made another way, and a field you change to one of those types is switched off.
• Everything else comes out as a short line in the lead's language (a photo is sent as a picture instead of a line): a CURRENCY as a price in your currency, a choice by its name, a long text on one line, and a URL_LIST as links (only https:// ones).
• If your records are people, a lead sees only the first word of the name (past a title such as Dr.).

Choice fields and category groups

Single choice and multiple choice fields read from a category group — a named list managed at Business setup → Categories.

• An option must be active to be chosen. Deactivating one stops it being offered without rewriting the history of everything already tagged with it.
• One group can serve both sides. That is what makes Category overlap matching work: the lead's answer and your record's tags come from the same vocabulary, so overlap means something.

Rule types

When you add a rule you pick a Condition. The first column is what the page says, and a rule is written as the miss: "Budget is less than 50,000" is missed by a lead under 50,000.

Three behaviours are worth stating plainly:

• A rule you can add today passes on an empty answer. There is nothing to judge. There is no "must answer" rule type: to insist on an answer, mark the question Must know before your team calls on its row under What your bot finds out, and add a rule for the range. An older rule that reads "is missing" still shows and can be edited or switched off, but a new one cannot be added.
• Every rule is hard or negotiable, your choice. The type says what is checked; hard or negotiable says what a miss means. See Your sales approach.
• IN_LIST on a multi-select requires every chosen value to be allowed, not just one.

Match types

A missing value on either side scores 0.5 and never fails a hard filter. Full explanation in Matching dimensions and weights.