Forms That Convert: What to Ask (and What to Leave Out)

Every field you add to a contact form is a small tax on the person filling it out. Most of them pay it without thinking twice. Some of them close the tab.

The question isn't whether extra fields cost you leads. They do. The real question is which fields earn their spot and which ones you're asking out of habit, because a template shipped with them or someone wanted "more data" without saying what they'd do with it. Here's a field-by-field breakdown of what belongs on a small business contact form, what to cut, and how to structure it so people actually finish it. If your form is fine but nobody's finding it at all, that's a different problem — see our post on why small business websites don't generate leads first.

The real cost of one more field

Picture someone standing in their kitchen, water pooling around a busted dishwasher. They found your site and they're ready to reach out, but your form asks for name, email, phone, address, service type, preferred date, preferred time, budget range, and "how did you hear about us." That's nine fields between them and a submitted form. Most will bail by field five.

This isn't a guess. Nielsen Norman Group's form usability research found that forms built to their best-practice checklist saw a 78% first-try, error-free submission rate, versus just 42% for forms that ignored those guidelines — nearly double. And the direction of the field-count relationship is one of the most repeated findings in form research: add fields, lose people. HubSpot's own research notes that "almost all historical research has shown that increasing the number of form fields has an inverse effect on conversion rates," even as the average web form has crept toward five fields.

Here's roughly what that tends to look like, based on typical completion-rate ranges reported across form-optimization research. Treat these as illustrative benchmarks, not a promise for your form — your numbers depend on your traffic and how much trust you've already earned.

The steepest drop isn't from 3 to 5 fields, it's what happens once a form crosses into "this feels like an application" territory. Baymard Institute's checkout research found 26% of users have abandoned a purchase specifically because the flow felt too long, and that the average checkout has shrunk from nearly 15 fields toward 13 as sites got more disciplined about what they ask for. A contact form is lower-stakes than a checkout, but the psychology is identical: length reads as effort, and effort reads as friction.

What every local service form actually needs

Strip a form down to what you'd genuinely need to call someone back and quote a job, and you land on four fields:

• Name. One line, nothing fancy — just something to call them and log in your CRM.
• One contact method, required. Phone or email, based on how you actually follow up (more below). Make the other optional.
• What they need. A short dropdown or checkboxes: "Water heater," "Leak," "Something else." The one field that actually helps you prep before calling back.
• A message field. Open text, clearly optional. Some people want to add context. Some just want to submit. Let both happen.

That's it. Four fields, one optional. Everything past that needs to justify itself. A lean form is just one piece of the bigger conversion picture — see 5 things your website is missing that are costing you customers for the rest of it.

The fields that quietly kill conversions

These show up constantly, usually copied from a template or added because "more information is always good." It isn't.

Requiring both phone AND email

The most common mistake on local business sites. Forcing both as required filters out the person who only wants to give a phone number, and the person who only wants to give an email — you lose both groups for nothing. Pick whichever method you actually follow up with first, and make the other optional.

"How did you hear about us?"

This field serves your marketing dashboard, not the customer standing in front of a leaking pipe. It adds friction at the exact moment you want none, and the data is usually junk anyway — most people click "Google" out of habit. Get attribution from UTM parameters instead. Don't make the customer do your analytics.

Budget range dropdowns

"What's your budget: under $500 / $500-$1,500 / $1,500-$5,000?" This scares off exactly the leads you want. Someone calling a plumber or electrician for the first time usually doesn't know what a job costs — they'll either lowball themselves out of the right service or abandon the form under the spotlight. Have that conversation on the phone, where you can explain the price.

Address as a required field, up front

Service area matters, but a full street address before you've talked to anyone is a lot to ask a stranger on their phone. A city or ZIP field confirms coverage without asking for a home address before you've earned any trust.

CAPTCHA overkill

Spam is real, but the old "type these distorted letters" puzzle costs you real leads for a problem a honeypot field or basic rate limiting usually solves for free. Save the aggressive stuff for forms that are genuinely getting hammered.

The mobile gap should worry you most. Local service traffic skews mobile — someone searching for a plumber at 9 PM is on their phone. A form that's merely annoying on a laptop becomes an ordeal on a cramped keyboard: the same form that loses roughly a third of desktop visitors to length can lose well over half of mobile visitors. Fix mobile first.

Single-step vs. multi-step: when it actually helps

Multi-step forms get pitched as a universal fix for long forms. Sometimes that's true. Often it just adds a click.

For four fields or fewer, don't bother. A single step is faster with no perceived-effort problem to solve. Multi-step earns its keep past six or seven fields, or when the form branches (different questions for "repair" vs. "new installation"). There, two or three short screens with a visible progress indicator reduce the "wall of fields" feeling that makes people close the tab before starting. What doesn't work: splitting a genuinely short form into steps just to make each screen "feel" easier. That's an extra tap for no benefit.

Mobile form UX: the details that actually matter

This is where sites get it wrong even with the field count right.

• Correct input type per field. Phone fields need type="tel" for the numeric keypad; email fields need type="email" for the @ shortcut. Small detail, big difference in typing speed.
• Turn on autocomplete. Proper autocomplete attributes (name, tel, email) let the browser fill fields from saved data. It's also part of the WCAG guidance on autocomplete — an accessibility requirement, not just convenience.
• Keep labels visible, not placeholder text that vanishes once someone starts typing. Labels above the field, always visible, are the pattern the W3C's forms accessibility guidance consistently recommends.
• Make the submit button impossible to miss — the most visually obvious thing on the form, not a low-contrast afterthought.
• Show errors inline, next to the field, not as a banner at the top of a long scrolling page.

None of this needs deep form expertise — mostly HTML attributes and a CSS pass. See our breakdown of what breaks on real contractor sites once you open them on a phone for more of the mobile-specific damage.

What happens after submit matters too

A short, well-built form still loses trust if the confirmation is a blank page. Say what happens next in specific terms: "We'll call within one business hour" beats "Someone will be in touch." If you genuinely call back fast, say so — it lowers the anxiety of "did that actually go anywhere?" Trust actually starts earlier than the form itself; our post on about page copy that makes customers call you covers the groundwork that makes someone willing to submit a form in the first place. This connects to a decision a lot of owners never settle: form or phone number as the primary CTA. We cover that tradeoff in our piece on contact forms vs. phone numbers — the short version is both have a job, and a well-built four-field form is what makes the form side worth having.

Smaller leaks worth fixing anyway

Trimming to four clean fields fixes the biggest problem, but a few habits still leak leads:

• Burying the form below three screens of scrolling instead of near the top of the page.
• No visual confirmation on submit — people re-click, sometimes double-submitting, sometimes giving up.
• A form that looks bolted-on and worse than the rest of the site — often a sign the whole template needs a look; see custom vs. template sites for small businesses.
• Making the message field required when it should be the one truly optional one.
• Sending submissions to an inbox nobody checks for two days.

"Too many fields" beats every other abandonment reason by a wide margin. Distrust and bad mobile UX matter, but length is still the biggest lever you control. Cut the form before you touch anything else.

Frequently asked questions

How many fields should a contact form have?

Four is the sweet spot for most local service businesses: name, one required contact method, service needed, and an optional message. Add more only if a field genuinely changes how you handle the lead, not because it "might be useful someday."

Should I require both phone and email on my contact form?

No. Require whichever one you actually use to follow up first, and leave the other optional. Requiring both filters out real leads for no real benefit.

Do multi-step forms convert better than single-step forms?

Only past roughly six or seven fields, or when the form genuinely branches. For a short four-field form, a single step is faster — don't split it just to make it "feel" easier.

Should I use a CAPTCHA on my contact form?

Only if spam is an actual problem. A honeypot field or basic rate limiting stops most bots for free. Save visible CAPTCHA challenges for forms genuinely getting hit hard.

What's the difference between a contact form and a phone number for conversions?

They serve different moments — a form works for people who aren't ready to talk yet or are searching after hours, a phone number wins for anyone who wants an answer right now. Our form-vs-phone breakdown covers when each should be the primary call to action.