Decide when an enquiry form should use conditional questions
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A customer selects “General question”, but the form still asks for a product, quantity and previous submission reference. Hiding those fields seems an obvious improvement—until someone changes their enquiry type and an old product answer remains attached to the submission.
Use conditional questions when an earlier answer makes a later question genuinely relevant or irrelevant. Keep a field visible and optional when it is useful across enquiry types but not essential. Keep essential shared information outside conditional sections. Most importantly, define what happens to answers when a section disappears before you build the branching rules.
The practical task is not simply to make the form shorter. It is to ensure that every reachable state produces a complete, internally consistent enquiry. The fictional worked example below provides a branch map, hidden-answer rules and test cases you can adapt.
1. Separate irrelevant questions from optional information
Start with a list of the questions on the current form. For each one, ask: “What answer would make this question unnecessary?” If there is no clear answer, conditional display may be the wrong tool.
- Shared and essential: show the field for every enquiry and require it. In the worked example, a reply email belongs here.
- Shared but nonessential: leave the field visible and label it optional. An organisation name may help provide context without determining whether the enquiry can be understood.
- Relevant only to a defined situation: put the field in a conditional section. A previous submission reference makes sense for an existing-submission request, not a new product question.
- Useful only to the business, with no clear capture purpose: consider removing it rather than finding a branch for it.
A visible optional field is often the simpler choice when everyone understands it and it occupies little space. Conditional display earns its complexity when it prevents a meaningful group of people from facing irrelevant questions or conflicting requirements.
Do not hide a question merely because it is difficult to answer. If a product enquirer might not know which product they need, offer an explicit uncertainty choice. Otherwise, the form may collect a guess where it should collect uncertainty.
2. Write the submission rules before the display rules
Display rules describe what appears. Submission rules describe what counts as a valid enquiry. Write both, but begin with the second.
For the hypothetical form in this article, the shared rules are:
- Every submission has one current enquiry type: product enquiry, general question or existing submission.
- Every submission includes a reply email and a message.
- Organisation name is visible and optional for all enquiry types.
- Only answers belonging to the current branch can enter the accepted enquiry record.
- A required field in an inactive branch cannot block submission.
- A missing or unrecognised enquiry type cannot silently fall through to a default branch.
These rules expose problems that a visual review can miss. A hidden field may still be marked required. A page may display the right section while sending values from another section. A saved draft may contain a choice that the current form no longer recognises.
Keep essential shared fields outside the branches. This reduces duplication and avoids having several versions of “reply email” with different validation or wording. Branch-specific requirements should add context, not replace the basic information needed to understand the enquiry.
3. Use this filled hypothetical branch map
Fictional worked example: a supplier uses one enquiry form for product questions, general questions and requests about an earlier submission. All field names, choices and rules below are hypothetical recommendations, not descriptions of a particular product’s controls.
Shared section: always visible
- Enquiry type: required; no preselected answer. Choices: Product enquiry, General question, Existing submission.
- Reply email: required.
- Organisation name: optional.
- Message: required, with the fixed label “What would you like us to know?” Keep this answer when the enquiry type changes because it is a shared field.
Branch P: Product enquiry
- Entry condition: enquiry type is Product enquiry.
- Product interest: required. Choices: Product Alpha, Product Beta, Not sure yet.
- Estimated quantity: optional; accept a positive whole number when supplied.
- Help choosing: visible and required only when Product interest is Not sure yet. Prompt: “Describe what you need the product to do.”
- Complete path P-A: shared required fields plus Product Alpha; quantity may be blank.
- Complete path P-B: shared required fields plus Product Beta; quantity may be blank.
- Complete path P-U: shared required fields plus Not sure yet and Help choosing.
- Exit handling: leaving Product enquiry clears Product interest, Estimated quantity and Help choosing.
Branch G: General question
- Entry condition: enquiry type is General question.
- Additional fields: none. The shared message provides the question.
- Complete path G: enquiry type, reply email and message are present.
- Excluded answers: no product or existing-submission answers enter the accepted record.
Branch E: Existing submission
- Entry condition: enquiry type is Existing submission.
- Reference available: required. Choices: Yes, No.
- Submission reference: visible and required only when Reference available is Yes.
- Approximate submission date: visible and optional only when Reference available is No.
- Earlier submission summary: visible and required only when Reference available is No. Prompt: “Briefly describe what you submitted earlier.”
- Complete path E-Y: shared required fields plus Yes and Submission reference.
- Complete path E-N: shared required fields plus No and Earlier submission summary; approximate date may be blank.
- Exit handling: leaving Existing submission clears all four branch-specific answers.
The reference is information supplied by the enquirer, not proof of entitlement to view or change an existing record. If the form also offers record access, that requires separate authorisation checks: OWASP’s object-level authorisation guidance explains why possession of an identifier alone is insufficient. This branch map only covers capturing the request.
4. Define hidden-answer handling explicitly
“Hide the section” is not a complete rule. A hidden answer may remain in browser state, a saved draft or the submitted data. Decide separately what happens on screen and what the receiving system accepts.
For this hypothetical map, use a clear-on-exit policy:
- When the enquiry type changes, identify which branch is becoming inactive.
- Clear its values and remove its active validation requirements.
- Show the new section and apply its requirements.
- At submission, accept only shared fields and fields allowed by the current branch and sub-branch.
Apply the same policy inside branches. Changing Product interest from Not sure yet to Product Alpha clears Help choosing. Changing Reference available from Yes to No clears Submission reference. Changing it back clears Approximate submission date and Earlier submission summary.
This avoids contradictory records, but it has a cost: someone who explores another option can lose typing. Make that consequence clear near the controlling choice. If a populated section will be erased, a confirmation before the switch is a reasonable design option; cancelling it must preserve the old selection and its answers.
Temporary retention is another valid design, especially for lengthy forms. If you choose it, inactive answers must remain excluded from submission, and returning to a branch should visibly restore them for review. Do not mix policies unpredictably. A form that sometimes restores hidden answers and sometimes deletes them is difficult for both visitors and testers to understand.
5. Resolve contradictions instead of choosing a convenient answer
A conditional form needs a policy for impossible combinations, not just missing fields. Here are filled hypothetical cases for the branch map:
- General question plus Product Alpha and quantity: exclude the inactive product answers. If the accepted record still contains them, the branch filter has failed.
- Product Alpha plus a stale Help choosing answer: exclude Help choosing because its condition is false. Keep Product Alpha and any valid quantity.
- Existing submission, Reference available = No, plus a stale reference: exclude the reference and require Earlier submission summary. A stale reference must not satisfy the active requirement.
- Existing submission, Reference available = Yes, with no reference: block submission and explain which visible field needs completion. Do not substitute an old summary.
- Enquiry type has an unrecognised value: require a fresh selection rather than treating it as General question.
Not every contradiction can be detected through field logic. Someone may choose General question and write a message about an earlier submission. Keep the selected branch as entered and preserve the message; do not infer a hidden reference or manufacture missing answers. Clear labels and a review step can help the person correct the selection.
When submission is blocked, retain valid active answers. Show an error summary and identify the relevant visible field. A validation failure should not make the enquirer start again or send them searching for an invisible requirement.
6. Test every reachable path and the changes between paths
The hypothetical map has six terminal paths: P-A, P-B, P-U, G, E-Y and E-N. Test each with the minimum valid information. For paths containing optional fields, also test a populated version so invalid optional values cannot slip through unnoticed.
A practical test sheet should record the starting state, action, expected visible fields, expected errors and expected accepted data. Checking the screen alone is insufficient: inspect the resulting captured record or an authorised test submission output too.
- Six direct completions: start from a blank form and submit each terminal path. Confirm active required fields are enforced and inactive fields are absent.
- Top-level changes: test every ordered change between Product enquiry, General question and Existing submission. Populate the starting branch before changing it.
- Product sub-branch changes: move from Not sure yet to each named product and back. Confirm Help choosing clears when hidden and becomes required when shown again.
- Reference changes: test Yes to No and No to Yes with populated answers. Verify both clearing and newly active requirements.
- Backtracking: leave a completed branch, return to it and check that the chosen retention policy is followed.
- Contradictory data: use the cases above to verify receiving-side validation, through an authorised testing method.
- Error recovery: submit with missing active answers, correct them and submit again. Confirm unrelated valid answers survive.
- Non-pointer use: navigate with a keyboard and check that newly revealed questions and validation errors are discoverable without relying on colour alone.
If draft saving or browser-back restoration is supported, add those states to the sheet. Reopening a draft must recalculate visibility and requirements from current controlling answers, rather than trusting an old display state.
7. Keep the branch map maintainable
Every additional controlling question increases the combinations that need review. Before adding another nested section, ask whether a visible optional field would capture the same information with less ambiguity.
Give each field one owner condition and one clearing rule. If several unrelated rules can show or hide it, document which rule takes precedence—or simplify the design. A reviewer should be able to work out the accepted fields from the current answers without reconstructing the visitor’s entire click history.
Keep the branch map alongside the form specification. When a choice is renamed, removed or added, update its valid paths, hidden-answer policy and tests together. If the form platform cannot enforce a branch-specific requirement or exclude inactive values, simplify the form rather than relying on visibility as a substitute for validation.
These are recommended operating practices, not proof that a particular form builder supports them. Check the available controls and receiving-side behaviour before committing to the design.
8. Make the next review measurable
Take one existing enquiry form and classify every field as shared required, shared optional, conditional or removable. Then fill a branch map using actual field names and run a test submission through every terminal path.
Record three concrete results: how many valid paths passed, how many inactive answers appeared in accepted records, and how many active required fields could be bypassed. For this hypothetical design, acceptance means all six terminal paths pass, with no inactive answers accepted and no missing active requirements permitted.
After changes go live, review enquiries for missing branch-specific context and reports of lost answers. Those observations help determine whether a question should remain conditional, become visibly optional or be rewritten. The decision should rest on the completeness and clarity of captured enquiries—not on how few fields the initial screen displays.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications