How many fields should an enquiry form have?
Use the fields the receiving team needs to take the next useful step.
AI-assisted practical guide · Editorial approach
The useful starting point
Use the fields the receiving team needs to take the next useful step. Explain why sensitive or potentially intrusive information is requested and make optional questions clearly optional. There is no universal field count that guarantees more or better enquiries.
Understand the decision
Map each field to a receiving action. If nobody uses a question, remove or postpone it. Distinguish contact details from qualification questions and avoid a large blank message box as the only way to express intent. Check labels, instructions, validation and errors with a keyboard and on a phone. Give visitors a usable route when submission is temporarily unavailable.
A practical approach
Choose one visitor task and walk through it on a phone. Read the page without using knowledge of the business: can you explain the offer, its limits and the next action? Then test the complete action with synthetic details in a test environment. Include missing fields, invalid inputs, slow responses, interruptions and retries. A click is a sign of interest; it becomes an enquiry only when the receiving system confirms durable acceptance.
- Identify the decision each field supports.
- Mark optional questions visibly.
- Provide useful examples without replacing labels.
- Test invalid input and server failures.
Illustrative example
A hotel event enquiry might need contact details, a broad event type and preferred timing, while a general branding enquiry may need only a short objective. Neither should request an entire procurement brief before explaining how the information will be reviewed.
A mistake to avoid
Do not reduce fields merely to maximise submission volume if it makes the next conversation unhelpful. Evaluate the complete customer and receiving-team journey.
What to review
Compare accepted enquiries, missing information and follow-up effort. Measure completion attempts separately from confirmed receipt and qualification.
Turn the guide into a working brief
Create a short acceptance checklist covering content ownership, keyboard access, error messages, receipt behaviour and the receiving team. Give every unresolved item an owner. Keep the next action proportional to the visitor’s readiness: a practical guide or price explanation may suit someone who is not ready for a sales call. Inspect a few conversations alongside analytics so that a technical event is not mistaken for a useful commercial outcome.
Common questions
What should I prepare before asking for help?
Start with this checklist: Identify the decision each field supports. Mark optional questions visibly. Provide useful examples without replacing labels. Test invalid input and server failures. Add your business context, existing materials and the decision you need to make. A useful initial brief can include uncertainty; you do not need to invent answers before discussing scope.
How should I judge whether the work helped?
Compare accepted enquiries, missing information and follow-up effort. Measure completion attempts separately from confirmed receipt and qualification. Keep the observation period and definitions visible. Use the responsible team's evidence alongside the website journey; do not attribute every change in results to one asset or article.
Sources & scope
AI-assisted practical guide. Examples are illustrative; business-specific facts and sector claims need the responsible owner’s approval.
- W3C WAI: Forms Tutorial
Reference for accessible labels, instructions and feedback. Original business examples are illustrative, not research findings or verified client results.
Use this guide to start your brief.
Share your business context, existing materials and what is still unclear. The guide title will be included so the conversation starts with the right problem.
Prefer email? Send a brief with this guide’s context.Related guides
What should a service page include to generate useful enquiries?
A service page should explain the problem it solves, who it suits, what is included, what needs confirmation and the next action.
Read the guide →Contact page design for customers who are not ready for a call
A contact page should offer a clear, low-pressure way to describe a need and understand the next step.
Read the guide →Designing form error messages that help people finish
A useful form error identifies the field, explains the problem and tells the visitor how to correct it.
Read the guide →