Lead Forms: The Fields That Kill Conversions

The fields that kill lead form conversions are the ones that make a visitor stop and think: a long list of boxes, "how did you hear about us," a required phone number when you plan to email, a captcha puzzle, and a vague "Submit" button. Cut your form to name, one way to reach them, and one question about the job. Everything else can wait for the follow up.
We audit a lot of small business websites. When I open the contact page, I count the fields. Anything over four is usually a form built by someone who wanted data, not someone who wanted customers. Every box you add is a reason for a stranger on a phone to leave.
Key points
- Ask only for what you need to reply: name, phone or email, and what they need.
- Required fields that you do not use are conversion killers.
- Captchas and puzzles add friction. Use invisible spam checks instead.
- Label every field. Placeholder text that disappears when you type is not a label.
- The button should say what happens next, not "Submit."
- Test the form on a real phone. Most leads for local services come from phones.
The Cost Of Each Field
I will not quote a percentage that changes by industry. What is consistent is the direction: every extra field lowers the number of people who finish. Form tool vendors and CRO studies report this repeatedly, and so does our own experience. The cost is not the typing. It is the decision. Each box asks "do I trust them with this?"
For a local service, the visitor is often in a hurry, on a phone, with a problem. A long form feels like paperwork. A short one feels like help.
The Fields To Cut, Worst First
| Field | Problem | What to do |
|---|---|---|
| Captcha with images or puzzles | Stops real people, annoys on phones | Use honeypot fields and invisible bot checks |
| "How did you hear about us" required | You do not need it to reply | Make it optional, or track source in your software |
| Full address | Feels intrusive early | Ask zip code only, or ask later |
| Company name for consumers | Irrelevant | Remove |
| Phone required AND email required | Two paths when one will do | Require one, make the other optional |
| Budget | Asking too early feels like a trap | Move it to the call |
| Long dropdowns | Hard on a phone | Use a few buttons or free text |
| Message box required | Many people cannot say it in words | Make it optional, with a prompt |
| Date and time pickers | Fiddly on small screens | Ask "when works for you?" in text |
| Password or account creation | Almost no one wants it | Never require it |
If you are not using a field in the first reply, it should not be in the first form.
What A Good Local Service Form Looks Like
For a repair, a trade, or a local service, I would use:
- Name (first name is enough)
- Phone (with a note that you will text)
- What is going on? (free text, optional or short dropdown)
- A button that says "Text Me A Price" or "Get My Quote."
That is it. Four things. For a mobile mechanic, the three things we need to quote are the car, the problem and a phone number. Anything beyond that, we can ask in the first reply.
Fix The Small Things
These small mistakes cost more than people think.
- Placeholder only labels. When the text disappears as you type, people forget what the box was. Put the label above the field.
- Wrong keyboard. Phone fields should bring up the number pad. Email fields should bring up the email keyboard. Use the right input types.
- No autofill. Add proper autocomplete attributes, so a phone can fill name and number in one tap.
- Tiny tap targets. Buttons and fields should be easy to hit with a thumb. WCAG 2.2 sets a minimum target size, and a larger one is better.
- Error messages that blame. "Invalid input" helps nobody. Say what is wrong in plain words and keep what they typed.
- Form resets after an error. Never do this. It makes people quit.
- Hidden submit button. On phones, the keyboard can cover the button. Test it.
This ties into basic accessibility too: labels, big tap targets and the right keyboard help everyone.
Handle Spam Without Punishing Customers
Spam is the reason owners add captchas. There are better options.
- Honeypot field: a hidden field that humans do not fill and bots do. If it has a value, discard the submission.
- Time check: a form filled in under two seconds is a bot.
- Server side checks: basic filters for links and known spam words.
- Invisible challenge services: some run in the background without a puzzle.
- Rate limits: block repeats from the same source.
You will still get some spam. Filtering it later is cheaper than losing a customer at the door.
The Button And The Promise
"Submit" says nothing. The button is the last thing a visitor reads before they decide. Use words that say what they get:
- "Text me a price"
- "Check my availability"
- "Send my request"
- "Get my free estimate" (only if it is true)
Under the button, add one line about what happens next: "We reply by text, usually within 15 minutes during business hours." Do not promise something you cannot deliver. If you promise a fast reply, have a way to deliver it.
Texting Consent, Done Right
If you collect phone numbers and plan to send texts, add clear consent next to the button. It should name your business, say what kind of messages they will get, mention that message and data rates may apply, and tell them they can reply STOP to opt out. Do not pre check a box. Keep a record. Your messaging provider will have rules that must be followed.
Privacy wording and cookies are a separate topic. I covered it in cookie notices and privacy pages for small business websites.
What Happens After The Click
A good form with no follow up is a waste. Check:
- Does the visitor see a clear thank you page or message?
- Does it say when they will hear from you?
- Do you get an alert right away, on your phone, not only in an inbox?
- Do you reply in minutes, not hours?
- Can you track which page and ad produced the lead?
Fast response beats pretty forms. A lead you answer in five minutes is worth more than ten you answer tomorrow.
A 15 Minute Form Audit
- Open your form on a real phone and try to fill it with one thumb.
- Count the fields. Cut anything you do not use in the first reply.
- Make only the essentials required.
- Replace puzzles with invisible spam checks.
- Rename the button.
- Add a line under it about what happens next.
- Submit a test and time how long until you see it.
Want a second set of eyes on your site? Book a strategy call, or see how our designs handle forms.
Questions
How many fields should a lead form have?
For a local service, three to four is a good target: name, phone or email, and what they need. Add more only when you truly need the answer to give a first reply.
Should I make the phone number required?
Only if you plan to call or text. If you reply by email, require email and leave phone optional. Requiring both means two chances to lose someone.
Are captchas bad for conversions?
Puzzle captchas add friction, especially on phones, and can lock out real customers. Honeypot fields, time checks and invisible bot detection catch most spam without bothering people.
Is a multi step form better than a long form?
It can be, when you truly need many answers, because it feels lighter. For simple local service leads, a short single step form is usually best.