By default, Responsly shows one question per page. That pacing usually improves comfort and completion, especially on mobile and for longer questionnaires.
Sometimes you still want several questions on a single page—for example:
- a contact block (name, e-mail, message) on one screen,
- a matrix-style layout where related items should appear together,
- a short cluster of related follow-ups that feel like one step.
For those cases, add a Group of questions so multiple items render one under another on the same page while the rest of the flow can keep the default one-at-a-time experience.
When a group works best
Question groups fit well when:
- you embed a compact form on a site and want it to feel like a classic contact panel—see Website embedding for context;
- you are recreating a matrix or grid-style block where splitting every row onto its own page would feel heavy;
- you have a small cascade of tightly linked fields (for example “Company size → Role → Team”) that should be answered in one glance.
Flow, logic, and the rest of the survey
Groups affect layout and pacing, not whether you can use logic: you can still combine grouped sections with survey logic and branching elsewhere in the form. If you are new to building flows in Responsly, start with How to create a survey.
FAQ
What is a question group in Responsly?
A question group is a block that displays multiple questions on the same page, stacked vertically, instead of advancing one question per screen for that section.
When should I use a group instead of one question per page?
Use one question per page for long surveys and higher mobile completion. Use a group when several short fields belong together—contact details, compact rating grids, or a small set of follow-ups that read as one task.
What are typical use cases for grouped questions?
Common examples are embedded contact forms, matrix-style layouts, and short cascades of related questions you want respondents to answer in a single view.
