Blog
Contact forms that don't scare customers away
October 26, 2026 · 6 min · Neil Black
- lead forms
- conversion
- small business
It's Halloween week, which makes it a good time to walk through the scariest room on a lot of small-business websites: the contact form. Nobody screams at it. They just quietly close the tab. A customer who wanted a quote, a booking, or a callback gets a long list of boxes, a mystery error message, or a button that seems to do nothing, and the lead vanishes like a ghost.
The good news is that the fixes are not expensive or complicated. Most of them come straight from public guidance by Google's web.dev (opens in a new tab) team and the W3C's Forms Tutorial (opens in a new tab), and a web designer can usually make them in an afternoon. Here's the checklist I'd run on any local business form.
1. Ask for less
The W3C tutorial puts it plainly: users usually prefer simple, short forms, so only ask for what's needed to finish the task. Ask for more and people are more likely to abandon the form. Google's sign-up form guide (opens in a new tab) says the same thing in different words: ask for as little as possible, and collect extra details only when you need them and the customer can see why.
For most service businesses, that means a name, one way to reach the person (phone or email), and a box for "What can we help with?" That's often enough to start the conversation. Do you really need their street address, their budget, and how they heard about you before you've even called them back? You can ask those things on the phone.
There's a second reason to keep it short. The Federal Trade Commission's guide to protecting personal information (opens in a new tab) tells businesses to "scale down": if you don't have a legitimate business need for sensitive information, don't collect it. Every field you remove is one less thing to protect later.
2. Use one box for the name
Google's address form guidance (opens in a new tab) recommends a single name field unless you have a good reason to split it up. One box is quicker to fill in, works with copy and paste, and makes the browser's autofill simpler. The same guide warns against blocking letters outside the basic Latin alphabet, so a customer named Françoise or Jörg isn't told their name is "invalid."
3. Label every field, and don't rely on the gray hint text
That faint example text inside a box (called a placeholder) disappears as soon as someone starts typing. Google's guide cautions against using placeholders instead of labels, because it's easy to forget what the box was for, especially on a phone or when someone is distracted. Put a real, visible label above or beside each field.
The W3C tutorial explains why this matters for everyone: labels help people using screen readers and speech input, and a label that's connected to its field gives people with limited dexterity a bigger area to tap. If you read our accessibility basics post, this is the same rule from the form's side.
4. Bring up the right keyboard on a phone
Plenty of customers will fill in your form on their phone, maybe standing in a costume aisle or waiting in a pumpkin patch line. Small details make that easier. Google's guide recommends marking the email field as an email field and the phone field as a phone field (type="email" and type="tel" in the code), so the phone shows the right keyboard and the browser can do basic checks on its own.
It also recommends the autocomplete setting on fields like name, email, and phone, so the browser can fill them in with one tap. If your form makes someone type their phone number into three separate little boxes, that's worth changing too: the guide recommends a single box for phone numbers.
5. Write errors that help instead of haunt
"Invalid input" is the haunted-house voice of web forms. It tells people something went wrong but not what. The W3C's Error Identification (opens in a new tab) guidance says an error should be identified and described in text, and its example, "Email is not valid," names the field and the problem. Better still, say how to fix it, which is what Error Suggestion (opens in a new tab) asks for.
Google's guide adds a few practical points:
- Check what people type as they go, not only after they press Send.
- Don't leave the Send button grayed out while something is missing. People will keep tapping it and assume it's broken. Let them press it, then explain what to fix.
- Do disable the button for a moment right after it's pressed, so an impatient double-tap doesn't send two copies.
- Mark required fields with an asterisk in the label, and explain what the asterisk means at the top of the form.
6. Make the button say what happens next
"Submit" is a word for a form, not for a customer. Google's guide suggests giving buttons a label that says what they do. On a contact form that could be "Send my question," "Request a quote," or "Book my visit." It's a small change, and it tells the customer exactly what they're about to do.
7. Say thank you, clearly
The W3C tutorial lists user notifications as part of a good form: tell people when they've succeeded, not just when they've made a mistake. After someone presses Send, show a clear message on the page: their request arrived, and when they can expect to hear back. "Thanks! We'll call you by the end of the next business day" beats a blank screen or a page that just reloads. A short confirmation email with a copy of their message is a nice extra.
Then make sure the message actually reaches you. Send yourself a test from your own site every so often, from your phone, and check that it lands in an inbox someone reads. A form that sends leads into a forgotten mailbox is the real horror story.
8. Count the leads you get
If you use Google Analytics 4, Google lists a recommended event called generate_lead (opens in a new tab) for exactly this: measuring when a lead comes in, for example through a form. Recording it when the thank-you message appears lets you see how many inquiries your site produces each month and which pages they came from.
Google's form guides also suggest watching where people drop off and testing on real phones and browsers, not just on your office computer. You don't need a big analytics setup to start. One counted event and a monthly look at the number is enough to notice if something breaks.
A five-minute form checkup
Pull up your own contact page on your phone and try it:
Only the fields you truly need
One name box, real labels above each field
Phone and email bring up the right keyboard
Errors say what's wrong and how to fix it
The button says what it does
A clear thank-you, and the message reaches a real inbox
Each lead is countedIf any of those trip you up, your customers are probably tripping over them too. The fixes are treats, not tricks: small, cheap, and they help every visitor who wants to reach you. And if a fast page matters to you as much as a friendly form, our post on why page speed matters covers the other half of getting a customer to that Send button.
Want a second pair of eyes on your form? Send us the link and we'll take a look.
Sources
- W3C Web Accessibility Initiative, Forms Tutorial (opens in a new tab), Error Identification (opens in a new tab), and Error Suggestion (opens in a new tab).
- web.dev, Payment and address form best practices (opens in a new tab) and Sign-up form best practices (opens in a new tab).
- Federal Trade Commission, Protecting Personal Information: A Guide for Business (opens in a new tab).
- Google Analytics, Recommended events (opens in a new tab).