Custom Form Block

Use a Custom Form block when one step needs to collect several structured fields inside the quiz flow. It is best for intake questions, preference forms, quote details, event requests, onboarding information, and structured data that should stay together as one response.

Custom Form is different from Lead Capture. Lead Capture is optimized for contact details and lead records. Custom Form is optimized for flexible in-flow data collection when the fields are part of the quiz logic, personalization, or handoff context.

Best used for

When to choose another block

Setup flow

1. Add a Custom Form block from the Question Blocks palette.
2. Write a prompt that explains what the form is collecting.
3. Add fields manually or use Bulk paste fields to create several fields at once.
4. Choose a field type for each field and mark fields required only when needed.
5. Add placeholders for text-style fields or options for dropdown, radio, and checkbox fields.
6. Optionally save the full form response to a variable for later personalization, API Steps, Agent Steps, or completion content.
7. Add Jump Logic when the step should route respondents after the form, or use saved variables when later routing depends on form context.
8. Preview the form on mobile and desktop before publishing.

Field setup reference

Block settings

Field types

Validation rules

• Custom Form blocks need at least one field.
• A Custom Form block can have up to 30 fields.
• Each field needs a label.
• Field labels can be up to 120 characters.
• Dropdown, radio, and checkbox fields need at least one option.
• Consent checkbox fields use the field label and do not need choice options.
• Choice fields can have up to 50 options.
• Choice option labels can be up to 120 characters.
• Submitted text values are trimmed and stored with a maximum length of 2,000 characters per field.

Response behavior

Custom Form answers are stored as one structured object. Checkbox groups store an array of selected options. Consent checkboxes store accepted when selected and an empty value when not selected. Other field types store a text value.

When you save the form response to a variable, QuizFlow Labs stores the full response as one structured value. This is useful for API Steps, Agent Steps, completion personalization, exports, and handoff workflows that need the form values together.

For placeholder rendering, Custom Form responses display as labeled field/value pairs, such as Budget: $5,000; Timeline: August; Services: Design, Build.

Multiple consent and acknowledgement fields

A Custom Form can contain more than one consent field. Use separate fields when each choice has a different purpose or legal basis. For example:

• Service contact: I would like the team to contact me about this request.
• Optional marketing: I would like to receive educational updates and promotions.
• Optional reminder: I would like a reminder closer to my selected date.
• Privacy acknowledgement: I reviewed the Privacy Notice and understand how submitted information may be handled.

Do not combine these into one required checkbox. A respondent may want the requested service without agreeing to unrelated marketing. Mark a field required only when the underlying action truly cannot proceed without that acknowledgement.

UX guidance

• Keep the form focused on one job.
• Split very long forms into multiple steps if each section needs its own explanation or routing.
• Use Lead Capture for contact records and Custom Form for flexible structured quiz data.
• Mark only essential fields as required.
• Use placeholders as hints, not as instructions that should be preserved.
• Use dropdowns for long lists, radio buttons for visible single-select choices, and checkboxes for multi-select choices.
• Use one consent checkbox per affirmative purpose. Keep service contact, marketing, reminders, and privacy acknowledgement separate when respondents need independent choices.
• Preview on mobile when the form has many fields or long choice labels.

Troubleshooting

Tips

• Use Custom Form when several related fields belong together.
• Keep field labels short enough to scan.
• Use bulk paste to create long field or option lists quickly.
• Use one Custom Form per logical form section.
• Test required fields and checkbox behavior before publishing.
• Use Jump Logic after the form when the form step should route to a later destination, and save the response to a variable when later logic or automation needs the form context.