A new customer leaves the optional account-reference field empty. Staff ask them to find a reference they have never had. The visitor has to explain why the question does not apply before the team can handle the request.
Optional WordPress form answers need meaning beyond empty or filled. Distinguish unanswered, unknown and not applicable when that difference changes staff follow-up. Start with the field that keeps producing an irrelevant question.
Decide what each answer means
Unanswered means the visitor supplied no answer. Unknown means they explicitly said they do not know. Not applicable means their stated situation or an established form rule makes the question irrelevant. A blank alone does not establish either of those last two states.
| State | Evidence | Next step |
|---|---|---|
| Unanswered | No answer supplied | Check whether it matters |
| Unknown | Visitor says they do not know | Help find the detail |
| Not applicable | Stated situation or agreed form rule | Skip irrelevant follow-up |
An existing customer may not know their account reference. A new customer may have no account. A blank tells staff neither. Ask the existing form owner which details apply to each request type before changing the form.
Ask only where the distinction helps
Do not add a three-choice selector beside every optional field. Start with one that repeatedly causes unnecessary questions. A choice such as “Existing customer” or “New customer” can establish when an account-reference question applies.
When a detail applies but is not yet known, provide a visible “I do not know yet” option if the business can accept that state. Keep the actual answer separate from its status. Avoid putting placeholder text into a real answer field. W3C’s form instructions guidance supports visible explanations of required inputs and formats.
Use conditional form logic for a known rule, such as showing the account-reference field only for existing customers. Use the saved customer-type choice to check applicability. Test both paths, including changing the choice before submitting. A blank reference cannot prove which question was shown. If the saved record lacks enough context, leave applicability unresolved.
Keep stated answers separate from assumptions
Put the stated answer and its status into the staff brief. A visitor who selected existing customer and unknown reference has described a specific problem staff can help resolve.
Account reference unknown. Visitor selected existing customer. Staff need another way to identify the account.
The same care applies to numeric fields. Zero is a supplied value; an empty field is not zero. The quantity and units guide covers numeric meaning. Here the decision is whether a detail was unanswered, unknown or irrelevant to the request.
Preserve the original submission wherever staff use a summary or export. If the destination cannot represent these states separately, put the visitor’s stated status in the ordinary working note. Leave the missing working or export value unset. Do not alter the source answer to fill a column.
Give review actions the relevance rule
Sentient Forms Missing Information Review can prepare follow-up questions after submission. Configure the review around details that actually matter to the selected request. Tell it how to treat explicit unknown and not-applicable answers.
For an existing customer with an unknown reference, staff might review this question before sending it: “What name or company should we use to find your existing account?” A new customer does not need that question. Compare the proposed follow-up with the original answers.
Use Entry Summary to make the submitted situation easier to scan. Neither action creates the missing fact or establishes that a not-applicable answer is correct. A reviewer handles exceptions through the normal business process.
Sentient Forms supports Gravity Forms, Contact Form 7, WPForms, and Elementor Pro Forms. For after-submission review with Contact Form 7, WPForms, and Elementor Pro Forms, enable the Sentient Forms Submission Ledger. Native entry features vary by builder. Check the current plugin listing before planning where staff will review results.
Test every state through the form
Use fictional details to submit each state and pair it with an expected review:
- New customer: no demand for an existing account reference.
- Existing customer with an unknown reference: one useful identifying question.
- Unanswered customer type and reference: applicability remains unresolved.
- Switch from existing to new customer before submitting: review follows the saved choice, without treating any stale hidden value as confirmed.
Also submit a completed reference and an explicit not-applicable answer. Inspect the original submission, notification, export and review aid your workflow uses. No destination should turn unknown into zero or silently drop the stated status.
Also try a not-applicable answer on a request where the detail is needed. Staff should see a question to resolve, rather than treat the selection as permission to proceed. The field-change checklist helps identify the destinations to retest.
Count unnecessary follow-up questions
For a fixed period, review submissions where staff interpret this field. Count how many needed an irrelevant follow-up despite an explicit not-applicable answer. Record the total reviewed submissions too. Keep that definition and denominator when comparing a later period.
Track staff corrections of invented facts and visitor questions about the added control separately. If people struggle with the choices or staff rarely use the distinction, simplify the field. Keep the smallest change your own queue supports.
Frequently asked questions
No. Add one only when that state changes how staff handle the request. A conditional question or a clearer label may be sufficient. Test the resulting submission and the places that read it.
No. An empty field supplies no answer. Unknown is an explicit statement that the visitor does not know. Preserve that statement rather than infer it from a blank.
It needs supplied context, such as the saved request type or an explicit unknown answer. A blank alone does not establish the reason. Staff check the original submission and review the proposed follow-up rather than accept an invented state.
Choose one account or reference field that causes irrelevant follow-up. Agree on its relevance rule, test the answer states and use a review action only if staff still need help choosing the right question.
