Skip to content

Conditional logic: showing fields only when they are needed

Use conditions to show a follow-up question only when an earlier answer calls for it, so customers never see questions that do not apply to them.

A shorter form gets finished more often. Conditions let you ask a follow-up question only when it is relevant, such as asking about pets only when the customer has said they have some.

Adding a condition

  1. On the Build tab, select the field you want to show or hide.
  2. In the field settings, open Conditions.
  3. Under Show this field when…, choose an earlier question, a comparison and a value.
  4. Add more conditions if you need them, and choose whether all of them or any of them must match.

A field with no conditions is always shown.

What you can compare

ComparisonExample
Is / is not"Any pets at home?" is Yes
Contains / does not contain"Treatments" contains Stain treatment
Greater than / less than"Bedrooms" is greater than 4
Is empty / is not empty"Company name" is not empty

For choice fields you pick the option from a list. For checkboxes and optional extras, "contains" matches when that option is one of those ticked.

All or any

  • All — every condition must match. Use it to narrow things down: show "Gate code" when "Is there a locked gate?" is Yes and "Will you be at home?" is No.
  • Any — one match is enough. Use it to group answers: show "Where should we collect the keys?" when the customer chooses either "Collect from the letting agent" or "Another arrangement".

A field can have up to 10 conditions.

How hidden fields behave

  • A hidden field is never required. A customer cannot be blocked by a question they cannot see.
  • A hidden field is not saved. If a customer answers a follow-up question and then changes the earlier answer so that it disappears, the follow-up answer is discarded.
  • A hidden field is not priced. Any price attached to it drops out of the estimate.
  • Hiding a field hides its dependants. If question C depends on question B, and B is hidden, C is hidden too.

The same rules are applied again on the server when the form is sent, so the saved request always matches what the customer could see.

Examples from the templates

  • Domestic cleaning: "Tell us about your pets" appears only when "Any pets at home?" is Yes.
  • Carpet cleaning: "Stain treatment details" appears only when Stain treatment is ticked.
  • Gardening enquiry: "How often would you like us to visit?" appears only for regular maintenance.
  • Mobile car valeting: a short reassuring paragraph appears only when the customer says there is no outside tap or power socket. Layout fields can have conditions too.

Conditions in pricing

Adjustments on the Pricing tab can use the same kind of conditions. For example, add a 25% surcharge only when the customer prefers an evening or Saturday visit. See Discounts, surcharges, minimum charges and VAT.

Things that stop a form being published

  • A condition that refers to a deleted field. Open the field and remove or change the condition.
  • A loop. If field A is shown when B is answered, and B is shown when A is answered, neither can ever appear. Remove one of the conditions.
  • A field that depends on itself.

The builder points out the field concerned. Duplicating a field does not copy its conditions, so check the copy.

Tips

  • Put the question that controls a condition before the field it reveals, ideally on the same step.
  • Make follow-up questions optional unless you truly need the answer.
  • Test both paths in Preview before you publish.

Back to the help centre