The contact form is the single highest-impact element on most service-business websites. It's also the single most over-engineered. Every audit we run, the contact form has three to five fields that the business doesn't actually use, two fields that are required for no reason, and one field that's silently breaking on mobile. Combined, those issues are pushing form completion rates well below 50% on sites where they should be 70%+.

The opinion up front: every required field above six on a service-business contact form is costing you leads. If you can't articulate exactly why a field is required for you to follow up, delete it. The data on this is overwhelming and it's been overwhelming for fifteen years. The business case for keeping bloated forms is always "we want to qualify the lead" — which is also the business case for not getting the lead at all.

The nuance: there are forms where a longer field count is appropriate. Mortgage applications, complex B2B enterprise enquiries, anything that has to gather regulated information. We'll cover when more fields is the right call. It's almost never on a generic "Contact Us" form for a service business.

What the data actually shows

We pulled the numbers from Zuko's 2025 form analytics report, which tracks 93 million form sessions. The average completion rate across all forms is 51.7%. Half the people who start a form leave without finishing. That's the headline number.

The drivers of abandonment, in rough order of impact:

Field count. Each field above six reduces completion by 5-10%. Forms with more than 10 fields abandon 85% of mobile users. The often-cited Imagescape case study went from 11 fields to 4 and saw a 120% conversion lift. HubSpot's testing reduced fields from 4 to 3 and saw a 50% lift. The number of fields is the single biggest lever.

Required vs optional. Required fields hurt more than optional ones, especially when the requirement isn't obvious. A required "phone number" on a form where the user wants to email-only correspondence is one of the most common drop-off triggers we see in Hotjar recordings.

Validation timing. Errors that appear only on submit — versus inline as the user types — cause about 30% higher abandonment. A user who fills in 8 fields, hits submit, and sees red errors on three of them is far more likely to leave than one who got inline corrections as they typed.

Field types that fight mobile. Tiny dropdowns that need a long-press on iOS, date pickers that don't trigger the native picker, phone fields that don't trigger the numeric keyboard. Each one adds friction that compounds.

Forms hidden behind a "Get a Quote" page. A homepage CTA that opens a dedicated form page is fine in principle but the click costs you about 15-20% of would-be form fillers who don't make the second click.

The 73% number in the headline of this post isn't fictional. We've seen worse. Sites with 12-field "Contact Us" forms behind two clicks routinely abandon 80%+ of visitors who started. The business owner is reporting 12 leads a month and assuming traffic is the problem. The leak is the form.

The three fields you can probably delete

Across the audits we've run, three fields show up over and over as required when they don't need to be. Here's each one and the reasoning.

"Phone number" as a required field

The argument for: "we want to follow up by phone." The argument against: a meaningful share of your visitors specifically don't want to be called. They want to email. Forcing them to surrender a phone number causes them to enter a fake one (so the field passes validation), causes them to abandon, or causes them to feel friction that lowers downstream response rates.

The fix: make phone optional, or capture it on the follow-up rather than the first contact. If your follow-up workflow is "call within an hour," ask for phone. If your follow-up workflow is "email with a quote," skip it. Match the form to the workflow you actually run.

"How did you hear about us"

The most common low-value required field. It satisfies a marketing curiosity at the cost of conversion. The data quality is poor — users select "Google" or "other" most of the time regardless of source. The same information is available in your analytics tool for free.

The fix: delete it. If you really want it, make it optional and last. Better still, ask the question on the follow-up email after the lead is captured.

"Tell us about your project" with a 200-character minimum

Required long-text fields are a conversion killer. They demand the user formulate a coherent description of their problem before they've had any conversation with you. Many visitors don't know what to write and abandon.

The fix: make the message field optional, or replace it with a short multiple-choice question — "What can we help with? [Service A / Service B / Service C / Other]." Lets the user select rather than write. Reduces cognitive load. Captures the same routing information.

Honourable mentions

Other fields that often appear required and shouldn't:

Company name for B2C services
Job title for any non-enterprise B2B service
Address when you only need a suburb or post code
Best time to call when you can ask in the email response
Marketing consent as a separate checkbox (combine with the privacy notice)

If your form has any of these as required, audit them. Each one is costing measurable completions.

The minimum-viable service contact form

For a typical Australian service business — accountant, lawyer, tradesperson, consultant, agency, clinic — the form that converts best looks something like this:

Name (required, single field — don't split first and last)
Email (required)
Phone (optional)
What can we help with? (optional dropdown with 4-6 options)
Anything we should know? (optional textarea)

Five fields. Two required. About 70% of visitors who start will finish, depending on your audience and trust signals.

You'll notice no "subject line," no "preferred contact method," no "are you the decision maker." All of that can be inferred from the follow-up or asked on the second touch. The first touch's job is to capture enough that you can respond intelligently. Everything else is the second touch's job.

When more fields are appropriate

There are genuine cases for longer forms. Three patterns we've seen work:

The pre-qualification form. When your sales process can't handle low-quality leads — say, you're a high-end consultancy charging $50K+ engagements and every wasted hour with a hobbyist is real cost — a longer form is justified. The form is the qualifier. You're trading raw volume for lead quality. Expect 70%+ abandonment and accept it.

The instant quote form. When the visitor's outcome is a price they get immediately, more fields are tolerated because they're directly producing value for the visitor. Removalists, web hosting, insurance quotes. The visitor accepts the friction because it's leading somewhere useful.

The booking form. When the visitor is booking a specific slot — a 15-minute consult, a dental appointment, a callback at 3pm Thursday — they tolerate more fields because the form represents a definite outcome rather than a vague follow-up. Booking-system forms like Cal.com or Calendly embedded on the page outperform generic contact forms for this reason.

If you're not in one of those three cases, the minimum-viable form will outperform anything longer.

The mobile form problem nobody tests

Most Australian SMB owners audit their contact form on desktop. They never fill it out on their own phone. The form that works fine on a 1440-pixel screen breaks on a 375-pixel screen in specific ways:

The textarea is too small — three lines visible, no way to expand. Users can't see what they've written. Many give up.

The dropdown is unusable — long-tap behaviour, accidentally scrolls the page, hard to dismiss.

The submit button is below the visible viewport — user fills in all fields, looks for the submit button, can't find it without scrolling. About 8% give up here.

The field doesn't trigger the right keyboard — phone number field opens the QWERTY keyboard instead of the numeric one. Email field opens QWERTY instead of an email-optimised keyboard with the @ symbol.

Autocomplete fights the form — Safari's autofill suggests an old phone number; the user can't see what was filled. Or worse, the form javascript rejects autofilled values and the user has to retype.

The fix is to actually fill out your own form on your own phone, ideally on a 3-year-old mid-range Android over a 4G connection, and to fix whatever breaks. Most owners have never done this. Spend 10 minutes doing it.

The validation pattern that works

Inline validation as the user types is more forgiving than on-submit validation. The user gets immediate feedback when something is wrong instead of finishing the form and getting a wall of red.

The pattern:

Don't validate the field until the user has tabbed out of it (otherwise you yell at them while they're still typing)
Show success states for fields that pass validation (a green checkmark, not just no error)
Show errors immediately below the field, in plain language ("That doesn't look like a valid email")
Don't disable the submit button — let them submit and show errors on the offending fields. Disabled buttons confuse users who don't know what they did wrong

WCAG 2.2's error handling criteria require errors to be clearly identified and the path to correction made obvious. Inline validation done well satisfies both the accessibility requirement and the conversion goal.

How to actually measure your form's performance

If you've read this far and want to know what your real numbers look like, three tools will tell you in less than an hour of setup.

Hotjar or Mouseflow — install one. Record sessions on the contact page. Watch ten of them. You'll see exactly which field people stop on. The behaviour is usually obvious after a handful of recordings.

Google Analytics 4 — set up an event on form start (any interaction with a field) and an event on form complete (successful submission). The ratio is your completion rate. Most sites have not set this up. Most sites should.

Manual test on a real phone — borrow a friend's phone if you don't have one in your age range. Fill out the form from scratch. Note what's slow, what's confusing, what doesn't work. This is the single most informative 15 minutes you'll spend on your website all year.

Where to start

If your form has more than six fields, more than three required, no inline validation, no mobile testing, and you've never watched a session recording — your form is leaking leads. The fix isn't subtle.

The lift from a sensible form rebuild is usually 30-60% in completion rate, which translates directly to lead volume. On a site getting 5,000 visitors a month at a 1.8% submission rate, that's the difference between 90 leads and 130 leads. At any reasonable lead value, the rebuild pays for itself fast.

If you'd like us to audit your form specifically — count the fields, watch the recordings, test on mobile, and tell you exactly which fields to delete and which to keep — book a free audit. We'll be specific about what to change. Not "improve the user experience." Specific changes with expected impact.

Contact Form Abandonment: 3 Fields to Delete (2026)