There is no universally correct number of fields for a business enquiry form. A customer requesting a routine appointment may need to provide very little information. Someone asking for a complex installation may need to explain the site, the intended work and a practical constraint before your team can respond usefully. The right question is what information the business needs at this point in the conversation.
Adding fields can increase effort, but removing them can move that effort into repeated emails and telephone calls. A useful form balances the visitor's task with the team's next action. To find that balance, review each question individually and test the whole journey, including what happens after submission.
Define the response the form should enable
Write down what the team will do with a new enquiry. Will they arrange an initial conversation, check whether the work falls within the service area, provide a simple estimate or prepare a detailed quotation? These actions require different information. A form intended to arrange a call does not need to collect every detail required for a final proposal.
Consider a small accountancy practice offering an introductory meeting. It might need a name, a way to reply and a brief indication of the service required. A company delivering equipment to a specific site may also need the location before it can assess availability. Neither example establishes a universal field count; each connects a question to a decision.
Agree the intended response with the people handling enquiries. If the website asks for information that staff never use, the form creates avoidable work. If staff repeatedly request the same missing detail before doing anything useful, that detail may belong on the form or in an immediate follow-up.
Give every field a reason to exist
Create a simple question register. For each field, record why you need it, who uses it, what happens if it is missing and whether it could be obtained later. Include the questions hidden within dropdowns, checkboxes and uploads. One visible field can still require several decisions from the visitor.
Use a question protocol to establish why each requested item is needed and how it will be used. Apply that discipline to commercial enquiries, with an arrangement that suits the actual task. A pattern from another service is not a blanket rule for every form. Our accessible form planning guide provides the related checks.
Review the register with an actual recent enquiry. Did the postcode determine whether you could help? Did the company name make the response more useful? Did the requested website address allow the team to investigate the issue? Where the answer is unclear, identify the operating decision before keeping the field by default.
Choose a contact route that suits the conversation
A form needs a reliable way to respond, but that does not always mean requiring both a telephone number and an email address. Consider how the service works and what visitors reasonably expect. If the next step is to send written information, email may be sufficient. If arranging an urgent visit requires a call, explain why a number is needed.
Where practical, let visitors indicate their preferred contact method. Make the choice operationally meaningful: staff should be able to see it and respect it. Offering a preference that the business ignores can undermine trust more than using a straightforward form with an honest explanation of the response process.
Ask for availability only when it changes the next action. A useful prompt might invite a suitable time for a call, with room for someone to say that their availability varies. Avoid making visitors negotiate a detailed appointment before your team has confirmed that it can help.
Separate useful qualification from premature interrogation
Qualification questions can help a business respond appropriately, but they should match what a prospective customer knows. Someone planning their first website may not know the technical platform, the exact number of pages or the terminology for an integration. Requiring these answers can make the form difficult for the very people who need advice.
Use plain prompts linked to outcomes. Asking what the website should help customers do can produce more useful context than asking for a detailed feature specification. Offer examples where they help, while leaving room for an answer outside the suggested categories.
Budget and timing can matter, but uncertainty is a legitimate answer. If you ask about them, provide a clear way to say that advice is needed or that the deadline is flexible. An invented budget band supplied merely to pass a required field does little to improve the quality of your enquiry data.
Use optional fields deliberately
An optional question should genuinely be optional. Explain what additional information would help, and ensure that leaving it blank does not prevent submission. Staff also need to understand how to handle an enquiry without it. Otherwise, the website promises a choice that the operating process immediately takes away.
For a project enquiry, an optional description can give confident visitors room to explain their plans without forcing everyone to write a brief. A short hint can suggest mentioning the goal, current difficulty and any important deadline. Keep the hint helpful rather than presenting a long list that feels like another compulsory task.
Remove optional questions that have no clear use. Marking a field optional reduces pressure but does not eliminate visual clutter or decision effort. The best form is not simply the existing long form with fewer asterisks.
Ask additional questions only when they apply
If the business handles several distinct services, a service choice may help show relevant follow-up questions. A repair enquiry might need a product reference, while a new installation enquiry might need the intended location. Asking everyone both sets of questions creates confusion and adds unnecessary effort.
Conditional questions need careful handling. When a visitor changes their service choice, make sure the form does not submit stale answers from a previously visible section. Check that the selected service and its answers reach the same record and are clear to the receiving team.
Use multiple steps when they help people understand the task, not merely to disguise the length. Explain progress and allow people to return to earlier answers. Test whether the split makes the form easier to use on a phone and whether important context remains visible when visitors need it.
Treat uploads as a separate decision
A photograph, drawing or specification can be valuable, but uploading it introduces another task. Visitors may not have the file on their current device. They may also be unsure what is appropriate to share. Ask for an upload only when it has a defined purpose, and explain the accepted formats and practical limits.
If the file can arrive later, offer that route clearly. A visitor should understand whether submitting without it still starts the enquiry. Where a file is essential, explain why and how the person can get help if they cannot provide it through the form.
Check the receiving process as well. Staff need access to the attachment, a clear association with the enquiry and suitable handling arrangements. A form that accepts a file but leaves the team searching separate storage locations has transferred the problem.
Measure completed journeys and useful responses
Review form starts, submissions and the enquiries that lead to a useful next step where your measurement setup permits. Define those events consistently. A higher submission count may reflect spam or incomplete information, while a lower count could reflect a traffic change rather than the form itself.
Combine recorded behaviour with observation. Ask a few representative users to complete a realistic task and explain where they hesitate. Include mobile use, keyboard navigation and the experience of correcting an error. A confusing label can create more difficulty than an additional well-explained question.
Check what customers receive afterwards. The confirmation should explain that the enquiry arrived and what happens next. The receiving team should have the information needed to fulfil that promise. Field decisions are easier to judge when you inspect both sides of the conversation.
Make changes you can evaluate
Prioritise questions with weak justification or clear evidence of difficulty. Record what you changed, why and what improvement you expect. Avoid removing several essential questions at once and then discovering that the team cannot respond without lengthy follow-ups.
Giraffe Digital's website design service can help connect enquiry forms to the wider customer journey. The aim is a form that asks understandable questions at an appropriate moment and enables a useful response. That is a stronger foundation than copying a field count from a different business.
Frequently asked questions
How should we define the response the form should enable?
Write down what the team will do with a new enquiry. Will they arrange an initial conversation, check whether the work falls within the service area, provide a simple estimate or prepare a detailed quotation? These actions require different information. A form intended to arrange a call does not need to collect every detail required for a final proposal. Consider a small accountancy practice offering an introductory meeting. It might need a name, a way to reply and a brief indication of the service required. A company delivering equipment to a specific site may also need the location before it can assess availability. Neither example establishes a universal field count; each connects a question to a decision.
How should we choose a contact route that suits the conversation?
A form needs a reliable way to respond, but that does not always mean requiring both a telephone number and an email address. Consider how the service works and what visitors reasonably expect. If the next step is to send written information, email may be sufficient. If arranging an urgent visit requires a call, explain why a number is needed. Where practical, let visitors indicate their preferred contact method. Make the choice operationally meaningful: staff should be able to see it and respect it. Offering a preference that the business ignores can undermine trust more than using a straightforward form with an honest explanation of the response process. Ask for availability only when it changes the next action.
How should we use optional fields deliberately?
An optional question should genuinely be optional. Explain what additional information would help, and ensure that leaving it blank does not prevent submission. Staff also need to understand how to handle an enquiry without it. Otherwise, the website promises a choice that the operating process immediately takes away. For a project enquiry, an optional description can give confident visitors room to explain their plans without forcing everyone to write a brief. A short hint can suggest mentioning the goal, current difficulty and any important deadline. Keep the hint helpful rather than presenting a long list that feels like another compulsory task. Remove optional questions that have no clear use. Marking a field optional reduces pressure but does not eliminate visual clutter or decision effort.
How should we treat uploads as a separate decision?
A photograph, drawing or specification can be valuable, but uploading it introduces another task. Visitors may not have the file on their current device. They may also be unsure what is appropriate to share. Ask for an upload only when it has a defined purpose, and explain the accepted formats and practical limits. If the file can arrive later, offer that route clearly. A visitor should understand whether submitting without it still starts the enquiry. Where a file is essential, explain why and how the person can get help if they cannot provide it through the form. Check the receiving process as well. Staff need access to the attachment, a clear association with the enquiry and suitable handling arrangements.
How should we make changes you can evaluate?
Prioritise questions with weak justification or clear evidence of difficulty. Record what you changed, why and what improvement you expect. Avoid removing several essential questions at once and then discovering that the team cannot respond without lengthy follow-ups. Giraffe Digital's website design service can help connect enquiry forms to the wider customer journey. The aim is a form that asks understandable questions at an appropriate moment and enables a useful response. That is a stronger foundation than copying a field count from a different business.


