How to Design Contact Forms People Actually Finish

A few months ago a client asked us why their “Get a Quote” page had plenty of visitors but almost no enquiries. The page looked fine. The copy was decent. Then we opened the form: fourteen fields, a mandatory “Company Turnover” dropdown, a CAPTCHA that failed on mobile about one time in three, and a submit button that said, simply, “Submit.” Nobody was getting to the end of it.

That’s the thing about forms. They’re the moment a visitor stops browsing and starts committing, and they’re also the part of a website most people design last, in a hurry, with whatever plugin defaults came out of the box. If your site depends on enquiries, bookings, or sign-ups, the form deserves as much attention as the homepage.

Start by cutting fields, not adding them

Every field you add is a small question the visitor has to answer: Do I know this? Do I want to share it? Why do they need it? Each one adds friction, and friction compounds.

Before redesigning anything, list every field and write next to it what your team actually does with that information in the first conversation. You’ll usually find a few that nobody uses until much later in the sales process, if at all. Budget ranges, job titles, “How did you hear about us?” and full postal addresses are common culprits on service-business forms.

A practical rule we use: if the field doesn’t change how you respond to the first enquiry, move it out of the form and ask it on the call. For most service businesses, name, email or phone, and a short message box are enough to start a conversation.

Make optional fields obvious, or remove them

If you keep optional fields, label them clearly as “(optional)” rather than marking required fields with a tiny asterisk. Many people don’t know what the asterisk means, and almost nobody reads the “* indicates required” note at the top.

Labels, layout, and the small details that add up

A surprising number of forms still use placeholder text instead of labels — the grey “Your Name” inside the box that vanishes the moment you start typing. It looks tidy in a mockup, but once someone has filled in three fields they can’t see what any of them were for. It also causes problems for screen-reader users and anyone with memory or attention difficulties.

Here’s what tends to work better:

  • Visible labels above each field. Placing them on top, rather than to the left, keeps the layout working on narrow phone screens.
  • A single column. Side-by-side fields make people zig-zag and skip things. One field per row is easier to scan.
  • The right input types. Using type="email" and type="tel" brings up the correct keyboard on mobile, which matters when most of your traffic is on phones.
  • Autocomplete attributes. Adding autocomplete="name", "email", and "tel" lets browsers fill in details in one tap.
  • Touch-friendly sizing. Fields and buttons should be big enough to tap accurately with a thumb, with enough space between them that people don’t hit the wrong one.

Google’s web.dev team has a detailed, well-tested write-up on this in their address and payment form best practices, and most of the advice applies just as well to a simple contact form.

Error messages that help instead of scold

Bad error handling is where a lot of nearly-completed forms get abandoned. The classic version: someone fills in everything, presses send, the page reloads, and a red banner at the top says “There was an error with your submission.” Half their answers are gone, and they have no idea which field caused the problem.

Good error handling does three things. It tells people which field has the issue, it explains how to fix it in plain language (“Please include an @ in the email address” rather than “Invalid input”), and it keeps everything they already typed. Checking a field when someone moves on from it, rather than on every keystroke, avoids shouting at people before they’ve finished typing.

Accessibility matters here too. Errors shouldn’t rely on colour alone, and they need to be connected to the field so assistive technology can announce them. The W3C’s Web Accessibility Initiative forms tutorial covers labelling, grouping, and error notifications in practical detail, and it’s worth handing to whoever builds your site.

Spam protection without punishing real people

Nobody wants an inbox full of junk enquiries, but heavy-handed CAPTCHAs can block genuine customers along with the bots. Before reaching for a puzzle, try lighter options: a hidden “honeypot” field that only bots fill in, a time check that rejects submissions made within a second or two of the page loading, or an invisible challenge service that only steps in when traffic looks suspicious. For most small business sites, a combination of these catches the bulk of spam without the visitor ever noticing.

Quick answers

How many fields should a contact form have?

There’s no magic number, but for a first enquiry, three to five fields is a sensible target. Ask only what you need to reply properly. You can always gather more details once the conversation has started.

Will improving my form guarantee more leads?

No, and nobody can honestly promise that. A better form removes obstacles for people who already want to get in touch. It can’t create demand that isn’t there, and results depend on your traffic, your offer, and your market.

What happens after someone presses send

The button itself deserves some thought. “Submit” says nothing. “Send my enquiry” or “Request a callback” tells people exactly what’s about to happen. A short line beneath it, such as “We usually reply within one working day,” sets expectations and reduces anxiety.

Then make the confirmation clear. A proper thank-you page, rather than a small line of green text that’s easy to miss, reassures the visitor that it worked. It also gives you a clean URL to track as a conversion in Google Analytics 4, so you can actually see whether changes to the form make a difference.

Finally, test the whole thing yourself, on a real phone, every few months. Plugins update, email settings change, and we’ve seen more than one business lose weeks of enquiries because form notifications were quietly landing in a spam folder. Send a test submission, check it arrives, and check the auto-reply (if you use one) reads like it came from a person.

A simple way to start

If you only have an hour, do this: open your main enquiry form on your phone, fill it in as if you were a customer, and note every moment you hesitate or get annoyed. Remove one unnecessary field, rewrite the button text, and confirm the submission actually reaches your inbox. Small fixes, but they’re often the ones that matter most.

If you’d like a second pair of eyes on your forms or the pages around them, our team is happy to take a look and give you honest feedback on what’s worth changing.

Written by the team at Technowave Global Solutions, a web design, development, and SEO agency based in Ludhiana, India, working with clients since 2010. Last updated November 2026.

Leave a Comment

Your email address will not be published. Required fields are marked *