Create smart forms that adapt based on user responses. Different form formats offer different logic features – Conversational forms use Jump To for page routing, while Classic forms use Conditions for field visibility.
When creating a form, you choose between two presentation formats. Each format has its own logic system:
Format
Layout
Logic Feature
Conversational
One field per page
Jump To – Route to different pages based on answers
Classic
Multiple fields per page
Conditions – Show/hide fields based on answers
What to capture: The form creation flow showing the two format options.
Show: The “Conversational” and “Classic” buttons with their descriptions.
Jump To (Conversational Format)
In Conversational forms, each field is on its own page. Jump To lets you skip users to different pages based on their answer to the current field.
Accessing Jump To
Open your form in Conversational format
Navigate to any field page (not Welcome or Thank You)
Look for the “Jump To” button in the page header (next to the Delete button)
Click it to open the Jump To popover
Note: The Jump To button only appears on field pages, not on Welcome or Thank You pages.
What to capture: A Conversational form showing the page header.
Show: The page indicator (e.g., “Card 2 of 10”), and the “Jump To” button with branching icon next to the red “Delete” button.
Highlight: Circle the “Jump To” button.
Setting Up Jump To Rules
Click the ON button to enable Jump To
A rule is automatically created with the field pre-selected
Configure the rule:
IF [field] – Shows which field triggers this rule
Select condition – Choose “is”, “is not”, “is answered”, etc.
Select value – Pick from the field’s options or enter a value
Skip to here – Choose the destination page
Click “+ Add rule” to create additional routing rules
What to capture: The Jump To modal with a rule configured.
Show: OFF/ON toggle (ON selected), rule showing “IF [field name]” with condition selected, value selected, and destination page selected. Also show “+ Add rule” button and “Default: Continue to next page” text.
When Jump To is enabled, if none of your rules match the user’s answer, the form continues to the next page as normal. This is shown as “Default: Continue to next page” at the bottom of the popover.
Jump To Indicator
When Jump To is enabled for a page, the button turns purple with a small dot indicator.
What to capture: The page header with Jump To enabled.
Show: The Jump To button in purple with the small dot indicator.
Jump To Example
Field: “Are you a new or existing customer?”
Rule 1: IF answer is “New Customer” → Skip to Card 3 (New customer details)
Rule 2: IF answer is “Existing Customer” → Skip to Card 5 (Account lookup)
Default: Continue to next page
Conditions (Classic Format)
In Classic forms, multiple fields appear on the same page. Conditions let you show, hide, or make fields required based on how the user answered other fields on the same page.
Accessing Conditions
Open your form in Classic format
Hover over any field on the canvas
Look for the action icons in the top-right corner of the field
Click the Conditions icon (branching symbol) – it’s below the copy and delete icons
The Conditions popover opens
What to capture: A Classic form with multiple fields. Hover over a field to show the action icons.
Show: The three icons in the top-right: copy, trash, and branching/conditions.
Highlight: Circle the branching/conditions icon.
Setting Up a Condition
Click the ON button to enable conditions
Choose what should happen when the condition is met:
Show – Field appears when condition is true
Hide – Field disappears when condition is true
Make required – Field becomes required when condition is true
Under “When these conditions are met,” configure your rule:
Select the triggering field from the dropdown
Choose an operator (is, is not, is answered, etc.)
Select or enter the value to match
Click “+ Add condition” for additional rules
What to capture: The Conditions modal with a condition configured.
Show: OFF/ON toggle (ON selected), the three action buttons (Show, Hide, Make required) with one selected, “What should happen?” label, “When these conditions are met:” section with IF dropdown, operator, and value configured, and “+ Add condition” button.
“Are you in a supported region?” → If No, skip to ineligibility message
Business vs Personal Fields (Classic + Conditions)
Show additional fields for business accounts:
Show “Company Name” when Account Type is Business
Show “Tax ID” when Account Type is Business
Show “Purchase Order” when Account Type is Business
Follow-Up Questions (Classic + Conditions)
Show follow-up fields only when relevant:
“Do you have dietary restrictions?” (Yes/No)
“Please describe” field → Show only if Yes
“Other” Option Detail (Classic + Conditions)
Show a text field when user selects “Other”:
“How did you hear about us?” with “Other” option
“Please specify” field → Show when “Other” is selected
Frequently Asked Questions
Do hidden fields still collect data?
No. If a field is hidden due to conditional logic, it won’t be included in the submission.
Can I make a field required only when visible?
Yes. When a field is hidden by conditions, its “required” validation is automatically skipped. You can also use the “Make required” action to make a field required based on a condition.
Can I switch between formats after creating a form?
Yes, you can change the presentation format in Design settings. However, Jump To rules won’t work in Classic format, and Conditions won’t work in Conversational format.
