← Back to blog

How Many Fields Should Your Enquiry Form Actually Have?

14 September 2026·6 min read
Quick answer: For most enquiry forms, somewhere between three and six fields is the sweet spot — enough to know who's contacting you and why, not so much that people give up halfway through. The right number depends on how "considered" your offer is: quick, low-commitment enquiries want fewer fields, higher-value or bookable services can justify a few more. Fewer fields almost always means more submissions, but not always better-quality ones. 📈

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.

The Field-by-Field Justification Test

List every field currently on your form, then ask this about each one:

  1. "What would I do differently if I had this answer versus not having it?" If the honest answer is "nothing," cut the field.
  2. "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.
  3. "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
The booking business with a 12-field form and high drop-off: A booking-based business had a form asking for full contact details, preferred dates, budget, how they heard about the business, and several other fields upfront, before the visitor had even had a reply. Analytics showed a large share of people starting the form and abandoning partway through. Trimming it down to name, contact detail, service needed, and preferred general timeframe — with everything else asked in the confirmation call — brought completions up noticeably, and the team still got what they needed to prep for that first conversation.
The B2B firm needing enough detail to qualify leads: A B2B business had gone the opposite direction after reading "shorter forms convert better," stripping their form down to just name and email. Enquiry volume looked great on paper, but a large portion were early-browsers or a poor fit, and the sales team was spending real time on discovery calls that a single extra field could've handled upfront. Adding one dropdown asking roughly what the enquiry was about, and one asking company size, cut down on unqualified calls without adding meaningful friction to the form itself.
The local service business testing 2-field vs 6-field forms: A local business ran both versions of their enquiry form side by side for a period — a bare-bones 2-field version and a fuller 6-field version. The 2-field version got more raw submissions, but a meaningful number needed a follow-up message just to find out what the person actually wanted. The 6-field version got fewer submissions overall, but a higher share converted into an actual booking without extra back-and-forth. Neither result was "wrong" — it came down to which mattered more to that business: enquiry volume or enquiry quality.

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.
💡 Split the form into steps if you truly need more fields. A form needing six-plus fields to qualify a lead properly feels far less daunting split into two short steps with a visible "step 1 of 2," even though the total field count hasn't changed.
  • 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 🤍

Share
Written by
Kate, founder of Chronically Online

I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.

Work with me ✦