Contact Forms That Get Filled In

An enquiry form is the point where all your marketing spend either turns into a conversation or does not. It is also, on most sites, the least examined thing on the page — installed once, styled to match the brand, and never looked at again.

The problems are rarely mysterious. Someone arrived interested, started filling it in, and hit something that made stopping easier than continuing.

Every field has a cost, so make it earn its place

The standard advice is “fewer fields”. That is roughly right but too blunt, because it ignores what happens after submission. A form with only an email box produces more submissions and worse conversations, because you now need three exchanges to establish what someone wants.

The better test is per-field: does this answer change what I do next, and can the person answer it without effort?

By that test, name, contact method and a free-text description of the problem usually earn their place. Company name often does not. “How did you hear about us?” is a question you are asking for your benefit, positioned at the exact moment you should be reducing effort — move it into the follow-up conversation or infer it from your analytics.

Optional fields deserve particular scrutiny. Marking something optional does not remove its cost; people still read it, still consider it, and still slow down. If a field is genuinely optional and rarely useful, delete it.

Two specific offenders. Dropdowns with twenty entries are worse than a text field, because the person has to read all twenty to check none of them fit. And any field asking for something people do not have to hand — a reference number, an exact budget, a postcode they are not currently near — will lose you people who intended to come back and did not.

Labels, errors and the small mechanics

Use a visible label above each field, not a placeholder standing in for one. Placeholders disappear the moment typing begins, which means anyone interrupted mid-form has to clear the box to remember what it wanted. They also tend to be low-contrast by default.

Validate at the right moment. Validating a field the instant someone starts typing produces an error message before they have finished the first word, which reads as nagging. Validate on blur, when they leave the field, and re-validate on submit.

Write error messages that say what to do. “Invalid input” is useless. “Please include an @ in the email address” is actionable. Put the message next to the field it concerns, not in a summary block at the top that scrolls out of view, and make sure the field itself is visually marked so the two connect.

Be tolerant about formatting. A phone number typed with spaces, brackets or a leading +44 is a valid phone number. Strip the characters server-side rather than rejecting the person. Nobody has ever abandoned a form because it was too forgiving.

The spam problem, solved proportionately

Every public form attracts automated submissions. The usual response is to bolt on a visual challenge, which taxes every genuine enquirer to stop a bot.

Start with the cheap defences. A honeypot field — a form input hidden from human users that bots tend to fill in — catches a meaningful share of naive automation and costs your visitors nothing. A simple timing check helps too: a form completed in under two seconds was not completed by a person. Server-side rate limiting by IP address handles volume attacks.

If those are not enough, use an invisible or low-friction challenge rather than a puzzle. Making someone identify traffic lights is a real cost, and it falls hardest on people with visual impairments or slow connections.

Whatever you use, confirm that legitimate submissions still arrive. Aggressive filtering that silently discards enquiries is worse than the spam it prevents, because you never learn what you lost.

What happens in the next five minutes

Submission is the middle of the process, not the end, and this is where most sites stop caring.

Confirm clearly. Replacing the form with a single line of small green text is not enough. Say what happened, what you will do, and when. A dedicated thank-you page is also easier to track as a conversion than an inline message.

Send an acknowledgement email. It reassures the person that the message was received and gives them your details in their inbox. Make sure it is not the only thing they get.

Route it properly. Enquiries that arrive at an unmonitored mailbox, or land in a shared inbox nobody owns, are lost as surely as if the form were broken. Assign a person.

Reply faster than feels necessary. For most service businesses, response speed decides who wins the job more often than anything on the website does. Someone filling in your form is very often filling in two others.

And test the whole path quarterly. Forms break silently — an expired API key, a changed mailbox rule, a plugin update, a DNS change that stops outbound mail authenticating. The failure mode is total and invisible. Submit a real test enquiry every few months and confirm it lands.

Measuring it honestly

Count starts, not just completions. If your analytics records a form interaction event and a submission event, the ratio between them tells you whether people are bouncing off the form or never reaching it. Those are opposite problems with opposite fixes.

Field-level tracking, where you record which field was last touched before someone gave up, is worth setting up if the form is long. It usually indicts one specific question.

Session recordings can help, but treat them carefully: they capture what people typed, so exclude form inputs from recording and be clear in your privacy notice about what you collect.

Then close the loop against actual outcomes. A form change that increases submissions while producing fewer real jobs has made things worse. The metric is qualified enquiries, not raw volume, and only your sales records know the difference.

Give people another route

Not everyone wants to fill in a form. Some want to phone, some want to email an address they can save, some want to message on WhatsApp. Publishing a real email address and a real phone number alongside the form costs you nothing and removes a barrier for the people who dislike forms — frequently the ones with the most urgent problem.

If you want your enquiry path looked at end to end, that combines website development with web analytics. You can also just get started and tell us what is going wrong.