Decide whether a phone number must be required on an enquiry form
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A visitor can describe a product question and receive a useful answer by email, but your form will not submit without a phone number. They must share an unnecessary detail, abandon the form, or enter a placeholder. The required field has turned the business’s contact preference into a condition of asking a question.
Require a phone number when it is necessary to fulfil the selected request through the service route actually offered. If email supports the enquiry, let email satisfy the requirement. If either method works, require one usable method rather than both.
The practical task is to connect each required field to a real service dependency. The worked example below turns that decision into a reusable table, implementation rules, and acceptance tests.
1. Separate service needs from business preferences
Start with the request, not the existing form. Ask the person handling enquiries: What cannot be completed without a phone number, and why? Distinguish three reasons:
- Inherent necessity: the requested activity itself requires telephone contact, such as a telephone conversation.
- Selected callback: the visitor has chosen a call rather than another available route. The number is necessary for that choice, even if the underlying question could be answered in writing.
- Operational limitation: the business currently offers a particular service only by phone. The requirement follows from the service offered, not necessarily from the subject of the enquiry.
For example, a hypothetical supplier might offer configuration consultations only by telephone while answering general product questions by email. It should disclose that consultations are currently telephone-only, rather than imply that configuration questions are inherently impossible to discuss in writing.
Then classify the phone field:
- Essential: the selected route cannot work without it.
- Optional: another required method already supports the enquiry, but the number has a stated supplementary use.
- Replaceable: phone or another contact method can independently satisfy the requirement.
- Unnecessary: there is no defined use for the number, so omit it.
Optional and replaceable are not interchangeable. In an email enquiry, an optional phone number supplements the required email address; it does not replace it. In an either-method enquiry, a phone number can satisfy the requirement by itself. Staff preferring to call does not establish necessity, and a completed field does not prove ownership or reachability.
2. Use this filled contact-method decision table
Fictional worked example: a hypothetical equipment supplier answers product questions by email and accepts telephone callback requests. For general product questions, either route can work. The supplier has no defined use for collecting a second contact method and does not offer anonymous individual follow-up.
The table is a reusable, filled specification, not customer evidence or a description of existing software controls. Replace its service choices with those your team actually supports.
| Scenario | Required contact method | Phone status | Explanation on the form | Refusal or recovery path |
|---|---|---|---|---|
| A. Phone-only request: visitor selects a callback | Phone number; omit email. | Essential for the selected callback. | Phone number — required for the callback you selected. | Offer the supported email enquiry route, preserving the question. Switching creates an email enquiry, not a callback. |
| B. Email-capable enquiry: visitor selects email | Email address; omit phone. | Unnecessary for this route. | Email address — required for your email enquiry. No phone number is needed. | No phone-refusal handling is necessary. If email is unavailable, offer the supported callback route. |
| C. No contact preference: either route is acceptable | One usable method: email or phone. Let the visitor choose which to supply. | Replaceable by email; not required alongside it. | Provide one contact method: email address or phone number. Either is enough. | If neither is supplied, ask the visitor to select and enter one method. Do not invite a second method without a defined use. |
| D. Visitor begins a callback but refuses to provide a number | Email after the visitor chooses to switch routes. | No longer required after switching. | A callback needs a phone number. You can send this product question as an email enquiry instead. | Preserve the question and change the request type. If both methods are declined, explain that individual follow-up requires a contact route. |
Record C separates willingness from data collection: a visitor can accept either route while supplying only one method. Record the absence of a preference without treating an unprovided second method as missing information.
A supplementary optional number would require a different specification. For example, a hypothetical email-based service might offer an optional call to clarify an ambiguous equipment reference. The form would need to explain that limited purpose while keeping email required. That is not this supplier’s workflow, so its form should not collect the extra number.
Offer a route change only where the alternative service exists and can handle the request. For a genuinely phone-only service, disclose the limitation and explain that it cannot proceed without a number. Do not invent an email service merely to make the form appear flexible.
3. Choose the simplest form arrangement that fits
A preference selector is useful only when the choice changes the required information or staff handling. If every enquiry uses email, a straightforward email form is simpler than a selector with no operational effect.
For the hypothetical supplier, a mixed form could first establish whether the visitor wants email, a callback, or has no preference. For the last choice, let the visitor select which single contact method to provide. Keep that selection distinct from a preference for how the business responds.
Do not ask a preference that the form ignores. An email choice followed by a mandatory phone field is contradictory. So is an either-method choice that requires both fields.
Conditional forms require consistent instructions, required-field indicators, submission checks, and stored request types. If the team cannot maintain those conditions reliably, separate, clearly named email and callback forms may be easier to operate.
Preserve the question when the visitor changes routes. Review previously entered contact details explicitly rather than silently carrying unnecessary details into the final submission. The final selection should govern the requirement and the request type staff receive.
4. Place accessible instructions beside the controls
Put the table’s field explanations where visitors enter their details, not only in introductory text. Display an either-method rule before the contact choice. Make required and optional status visible without relying on colour alone.
Use persistent labels rather than placeholder text as the only identifier. W3C guidance on form labels describes how labels identify controls and should be associated with them programmatically. Ask the implementer to confirm that each explicit label reference matches its input ID, including fields revealed after a route change.
Place errors where people can connect them to the affected control or contact-method group. Ensure instructions and errors remain available when navigating by keyboard or assistive technology. Hiding an irrelevant field should not leave an unexplained requirement behind.
This decision concerns capture requirements. Permission for later communications, contact cadence, and response commitments require separate decisions.
5. Pair validation rules with acceptance tests
Clear wording will not fix submission logic that still enforces an old requirement. Use these acceptance tests to check both browser-side behaviour and server-side enforcement. The examples below are hypothetical test cases, not production results.
- Callback requires phone, not email. Submit a callback with phone only: it should pass the contact requirement. Remove phone: submission should be blocked with a callback-specific explanation.
- Email requires email, not phone. Submit an email enquiry with email only. It should pass without a hidden phone requirement.
- Either method can satisfy the requirement. On the no-preference route, test email only and phone only. Both should pass. Selecting no method, or leaving the selected method empty, should produce a clear correction.
- Unnecessary second details are not requested. Check that the no-preference route does not invite both methods. If changing selections leaves a previously entered value in form state, confirm that the final submission follows the declared collection rule.
- Switching changes the requirement. Start a callback, enter a question, then switch to email. The question should remain, email should become required, and missing phone should not block submission.
- Errors preserve useful input. Trigger a missing-contact error. The question and current service choice should remain available for correction.
- Handling matches selection. Inspect received test records. Request type, supplied contact method, and expressed preference should match the final choices.
W3C validation guidance recommends understandable, accessible errors and accommodating varied input formats. Browser-side checks do not remove the need to validate submissions on the server.
For phone input, avoid rejecting ordinary spaces, brackets, or country prefixes merely because they differ from a preferred display format. A format check cannot establish ownership or reachability. Also test that changing a route removes obsolete errors, rather than leaving visitors blocked by a field they can no longer see.
6. Prevent staff handling from undoing the decision
Give the enquiry owner the same decision table used by the implementer. Otherwise, a form can accept the right details while downstream handling still treats every empty phone field as a defect.
Look for distinctive handling failures: an email enquiry sent to a missing-number queue; a no-preference record treated as a request to collect both methods; or a route change that creates duplicate callback and email tasks. Correct the request classification rather than asking the visitor to repair a valid submission.
Do not recommend placeholder numbers as a workaround. They make a field look complete without supporting its purpose. If placeholders already appear, inspect the affected request types before tightening format rules. Stricter validation may change the placeholder without removing the unnecessary requirement.
If contact details later prove unusable, distinguish that from a missing required field. Record the observed problem accurately. Neither an unusual-looking number nor a staff preference for another channel establishes that the visitor submitted an incomplete enquiry.
7. Review usable enquiries, not filled phone fields
A fuller phone column is not proof of a better process. During an agreed review period, examine submissions by request type, contact-field errors, route changes, suspected placeholders requiring review, and requests staff cannot handle because an essential contact method is missing.
If reliable form-start data exists, compare starts and completions as well. Interpret changes cautiously: traffic sources and enquiry mix may also change. Completion changes alone do not establish their cause. Staff review adds a different check: whether each submission contains enough information for its selected service.
Next action: adapt the filled table for one live form. Have the service owner confirm the dependencies, the implementer run the acceptance tests, and an enquiry handler inspect the resulting records. Set a review date and identify what evidence would justify changing the requirement again.
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