One question at a time, on its own screen. Long forms stop looking like paperwork and start feeling like a conversation — and people finish them.
Step 2 of 5
What kind of project is this?
Pick the one that fits best — the next questions adapt to your answer.
Show someone eighteen inputs at once and they do the maths: this will take a while. Most of them close the tab. The fields didn’t change — the presentation did all the damage.
A QueryCue form asks one question per screen. The visitor reads a single, clear question, answers it, and moves on. A progress bar tells them exactly where they are: Step 2 of 5, not a bottomless scroll. Questions that need to travel together — first name, last name, email — can share a screen as a group step, so you’re never forced into artificial ceremony.
And because every form is built on the visual flow canvas, the questions someone sees depend on the answers they gave. Nobody scrolls past a section that doesn’t apply to them.
Each question node on the canvas becomes one screen. Need several fields together? Use a group node — they render on a single step.
Conditions on the connections decide what comes next. Two visitors can walk two entirely different routes through the same form.
The step counter and progress bar recalculate as the path branches, so the number a visitor sees reflects the route they’re actually on.
Each step validates before it lets the visitor continue. Errors appear inline, on the field, in plain language — never as a list of failures after a long submit.
A single question reads as a moment’s work. The same twenty fields, shown all at once, read as a chore.
Each answered step is a small commitment. People who start step one are far likelier to reach the end.
Branching keeps the form short for everyone — irrelevant questions are never asked, not merely hidden.
It works the way people expect a form to work. Each new step puts the cursor in the field, so you just start typing. Enter moves on, Back returns to the previous answer without losing it, and the whole thing is built for touch, so a thumb on a phone is a first-class input — not an afterthought. Screen readers hear each step announced as it arrives, along with progress, errors and required fields. Turn on “reduce motion” in your system settings and the form obliges.
Multi-step comes alive when the path adapts and the form has a home of its own:
Multi-step is included free. Build one form, publish it, and watch where people actually stop.