How Many Fields Should Your Enquiry Form Actually Have?
Every business with a form has, at some point, been told two contradictory things: "cut your form down, friction kills conversions" and "you need to qualify leads properly or you'll waste time on tyre-kickers." Both are right, which is exactly why this question doesn't have a one-size answer. 💖 The businesses that get this wrong usually aren't being lazy about it — they're just optimising for the wrong thing, either chasing raw enquiry numbers or over-correcting into a form that feels like an interrogation.
What most businesses get wrong
The most common mistake is treating the enquiry form as a place to collect everything you'll eventually need, rather than the minimum needed to start a conversation. Every extra field is a small tax on the visitor's patience, and it compounds — a form that feels reasonable at four fields can feel like a chore at ten. The opposite mistake, going down to name and email only, can flood you with vague or unqualified enquiries that all need a back-and-forth just to find out what the person actually wants, which shifts the friction from the form onto your inbox instead of removing it.
List every field currently on your form, then ask this about each one:
- "What would I do differently if I had this answer versus not having it?" If the honest answer is "nothing," cut the field.
- "Could I ask this later, once they've already committed to enquiring?" If yes, move it to a follow-up email or call instead of the first form.
- "Is this field mainly for my convenience or theirs?" Fields that exist purely to save your team a phone call are worth keeping only if they don't cost you the enquiry entirely.
A workable default structure for most enquiry forms:
- Name
- Email (and/or phone — pick the one you'll actually respond via fastest)
- What they need (a short dropdown or one-line text field, not an essay box)
- One qualifying detail specific to your business (timeframe, budget range, location, or similar — whatever actually changes how you'd respond)
- Optional: a free-text "anything else" field, clearly marked optional
How to actually implement this
Treat your form like any other page element you'd test and refine, not a set-and-forget piece of the site:
- Audit your current form using the justification test above and remove anything that fails it.
- Mark genuinely optional fields as optional in the label, rather than leaving people to guess.
- Use dropdowns or short-choice fields instead of open text boxes wherever the answer is predictable.
- Check your form on mobile — one that looks reasonable on desktop can feel much longer on a phone keyboard.
- If unsure, start leaner than feels comfortable and add a field back only if you genuinely can't act on enquiries without it.
- Don't add a field "just in case it's useful" — every field should earn its place by changing what you'd do next.
- Don't strip a form down purely to chase submission numbers if it means drowning in unqualified enquiries afterwards.
- Don't make optional fields look mandatory (or vice versa) — be explicit, people won't guess correctly.
- Don't ignore what happens after submission — a lean form still needs a fast, human follow-up.
- Don't assume one form length fits every service — a quick question and a full project enquiry may need different forms.
Frequently asked questions
Do shorter forms always get more enquiries?
Generally yes, fewer fields reduce effort and tend to increase completions — but "more enquiries" and "more useful enquiries" aren't the same thing. A very short form can shift the qualifying work from the form onto your team's time later, so the trade-off depends on how much spare capacity you have to chase up vague enquiries.
Should phone number be a required field?
It depends how you actually respond — if your team calls people back, make it required and say why. If you reply by email as standard, making phone optional removes friction without losing anything you'd use.
Is a multi-step form better than a single long form?
Often yes for forms with five-plus fields, since breaking it into stages reduces the feeling of a long task. It's not a fix for having too many fields, though — use the field-justification test first, then decide on layout.
What if I need a lot of detail before I can even quote?
That's a legitimate reason for a longer form, but consider whether all of that detail truly needs gathering before the first contact. Often a shorter initial enquiry form plus a more detailed follow-up sent only to genuinely interested people works better than asking casual browsers to do the work upfront.
Keep reading 🤍
I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.
Work with me ✦