Multi-Screen & Branching
Conversational forms render one screen at a time, with Back and Continue buttons between them. This page covers how to add screens, configure them, and build branch routes that jump to a different screen based on what the visitor answered.
Screens
A conversational form is a sequence of screens. Each screen has:
- A title and optional description (rendered as a heading on the live form)
- One or more fields (drop them onto the screen card in the builder)
- Optional branch routes that change which screen comes next
- An optional Skip behavior
By default, fields advance one per screen. You can put multiple related fields on one screen — e.g. First Name + Last Name + Email together.
Adding & Removing Screens
In the builder canvas:
- Click Add New Screen between any two cards to insert a new screen there.
- Click a screen card to select it. The right panel shows screen-level settings (title, description, button text, branch routes).
- Click the trash icon on a screen card to delete it (with confirmation).
Screen Settings
When a screen is selected:
| Setting | What It Does |
|---|---|
| Title | Heading shown above the screen's fields on the live form |
| Description | Caption beneath the title |
| Button Text | Custom Continue-button label for this screen (defaults to Continue) |
| Skip Enabled | Adds a Skip link letting visitors advance without filling required fields |
| Routes | Branch routes (see below) |
Welcome Screen
The Welcome Screen is the optional first step before any fields. Configure it from the conversational settings panel — toggle Enabled and set:
| Setting | What It Does |
|---|---|
| Title | The big headline (e.g. Tell us about yourself) |
| Description | Subtitle text below the title |
| Button Text | The button label (defaults to Start) |
| Media | Optional image / video / GIF shown on the welcome screen |
When enabled, the form opens on the Welcome Screen. The visitor clicks Start to advance into the first real screen.
Thank You Screen
The opposite end. Always rendered after submit (unless an ending screen's condition matches and overrides it).
| Setting | What It Does |
|---|---|
| Title | Big headline (e.g. Thanks!) |
| Description | Subtitle |
| Redirect URL | Optional — auto-navigate after a brief moment |
The form-level Success Message in Form Settings is the fallback if no Thank You title is set.
Navigation
Between screens, the live form shows:
- Back — go to the previous screen (uses the visitor's actual nav stack, not just
currentIndex - 1, so branch routes don't break going back) - Continue — advance to the next screen (or trigger branch routing if rules match)
- Submit — only on the last screen (replaces Continue)
Validation runs per-screen: the Continue button is disabled if any field on the current screen is invalid. Validation on later screens isn't checked until the visitor reaches them.
Auto-advance for single-choice questions
In conversational settings, Auto-advance single choice is on by default. When a screen has a single-choice field (Radio, Yes/No, Picture Choice without multiSelect, Rating), clicking an option auto-advances — no Continue press needed. Turn off to require explicit Continue.
Keyboard navigation
| Key | Action |
|---|---|
Enter | Advance (Continue) |
Shift + Enter | Insert newline in textareas / submit a multi-line input |
1–9 (or A–Z) | Quick-pick option keys for choice fields (when alphabet key shortcuts is on) |
Branch Routes
A branch route on a screen says: "if this condition matches, jump to that screen instead of the next one."
Each route has:
| Field | What It Does |
|---|---|
| Field | Which field's value to test (typically a field on the current screen) |
| Operator | equals, not_equals, contains, not_contains, is_empty, is_not_empty, greater_than, less_than |
| Value | The reference value to compare against |
| Target Screen | Which screen to jump to when this condition passes |
When the visitor clicks Continue on a screen, routes are evaluated in order. The first matching route wins; the form jumps to that route's target screen. If no routes match, the form falls through to the next screen normally.
Worked Example: Skip Q2 if Q1 is "No"
Goal: A 3-question survey. If Q1 is "No", skip Q2 and go straight to Q3.
Steps:
- Build a 3-screen conversational form, one Yes/No question per screen.
- Click the Q1 screen card to select it.
- In the right panel, find the Routes section.
- Click + Add Route.
- Field: the Q1 Yes/No field.
- Operator: Equals.
- Value:
no - Target Screen: the Q3 screen.
- Save.
When the visitor picks No on Q1 and clicks Continue, the form jumps directly to Q3 — Q2 is skipped. Picking Yes falls through to Q2 normally.
Worked Example: Multi-Path Quiz
Goal: A quiz where the first question routes the visitor to one of three different sub-paths.
Setup: 7 screens total — 1 intro, 3 sub-path screens, 3 outcome screens.
- Screen 1: "What kind of customer are you?" Radio with B2B / B2C / Agency.
- Screens 2, 3, 4: B2B path, B2C path, Agency path (each one tailored)
- Screens 5, 6, 7: outcome screens for each path.
Routes on Screen 1:
| Field | Operator | Value | Target |
|---|---|---|---|
| Q1 | Equals | b2b | Screen 2 (B2B path) |
| Q1 | Equals | b2c | Screen 3 (B2C path) |
| Q1 | Equals | agency | Screen 4 (Agency path) |
Routes on each path's last screen point to the matching outcome screen.
The result: each visitor sees only the screens relevant to their cohort.
Skipping Screens (Skip Enabled)
If a screen has Skip Enabled turned on, a small "Skip" link renders next to Continue. Clicking it advances without validating or storing the screen's field values. Useful for non-essential follow-ups.
Multiple Fields on One Screen
You can place multiple fields on a single screen — drag them onto the same screen card. They render stacked, all visible together, and Continue is enabled only when all the screen's required fields are filled.
This is the "smart" way to group related questions (First/Last/Email together) without forcing the visitor through three nearly-identical screens.
Save & Resume
Conversational forms can optionally save progress between sessions:
| Setting | What It Does |
|---|---|
| Enable Save & Resume | When on, the form persists answers as the visitor progresses. Returning to the URL on the same browser resumes from the last screen they reached. |
Useful for long forms where visitors might bail and come back.
Next Steps
- Hidden Fields & Variables — Quiz scoring, URL-param hidden fields, variable operations
- Ending Screens — Pick a different thank-you based on score / variable conditions
- Conditional Logic — Show/hide individual fields (different from branch routes)
- Form Types — When Conversational makes sense vs Premium