Multi-Page Forms: Long Questionnaires Without the Wall of Text
Multi-Page Forms let you break a long form into as many pages as you need — and route prospects to specific pages based on what they've already entered.
Most form builders default to "one giant page" because writing a flow is hard. Paminga's Form Builder makes multi-page forms easy enough that you'll reach for them naturally — and gives you the conditional logic to route prospects intelligently through them.
Adding Pages
On the "Pages" tab in the left control panel, click Add a Page. That's it. Add as many as you want.
- Reorder by drag-and-drop
- Clone any existing page with the clone icon — useful when most of two pages are the same
- Name your pages internally (the names don't appear in the published form)
Each page uses the same Sections, Rows, Blocks, and Elements model as a single-page form. No new mental model to learn.
TypeForm-Style Forms
TypeForm gained a lot of attention by popularizing one-question-per-page forms.
Paminga does that natively. Just add one Element per page in your multi-page form. Same engagement-friendly pattern. Same backend behavior. Same automation downstream.
Conditional Navigation
This is where multi-page forms get interesting.
By default, navigation is linear: page 1 → page 2 → page 3 → submit. But you can override that, routing prospects to specific pages — or submitting the form from any page — based on conditions you define.
Example:
- Prospect selects "United States" on Page 1 → route them to Page 2 for follow-up questions
- Prospect selects any other country → submit the form immediately
You write the conditions using the same Segment Builder you use everywhere. The Form Builder evaluates them when the prospect clicks Next.
Bonus: Pair with Conditional Actions
While you're at it, configure Conditional Actions on form submission. Different conditions → different paths through the form, and different post-submission Actions. The same form covers three motions.
Validation With Conditional Navigation
A subtle but important detail: Required fields are only required for prospects who actually see the page. If conditional navigation skips a page for a particular prospect, that page's Required fields don't apply to them.
This is the right default. If you skip a page on purpose, you don't want validation errors stopping the submission.
Partial Form Submissions
Long forms get abandoned. Paminga turns that into a feature.
Enable partial form submissions via a checkbox on the Settings tab. With it on:
- When a prospect clicks Next, Paminga creates or updates a Contact using the values submitted on that page
- A partial form submission entry appears in the Form Submissions table
You get the data they already entered, even if they never finish.
Pick Up Where You Left Off
If a prospect returns within 3 weeks (current default — we're open to feedback), the form loads the next page that needs their attention. They resume mid-form instead of starting over.
This is one of those small UX details that compounds — abandonment rates drop because finishing later actually works.
What's Coming
Things we're building on top of partial submissions:
- Triggered emails reminding prospects to return and finish
- Activity Stream entries with the values submitted in each partial submission
Get Started
- Open any new form in the Form Builder
- Open the Pages tab and add the pages you need
- Configure Conditional Navigation if your flow should branch
- Turn on partial form submissions in Settings if your form is long enough to abandon
❌ Don't put 23 fields on one screen and watch the abandonment rate.
✅ Do split into pages, route conditionally, capture partial submissions, and resume mid-form.
Read the Multi-Page Forms docs to dig in.
