A website form is a trade. The visitor hands over information, and in exchange they expect a useful reply. Most small-business forms get the trade backward: they ask for everything that would be convenient to know before anyone has a reason to trust the answer will be worth it.
I see the same contact form over and over. Name, email, phone, company, how did you hear about us, budget range, a dropdown of twelve services, and a message box. Nine fields to ask a question that could have been three. The business owner is not being greedy — every one of those fields got added because somebody wanted that information once. But each addition was priced as free, and none of them are.
Every field is a separate chance to quit
A form is not read the way a page is read. It is worked through, one input at a time, and each one is a small decision: do I know this, do I want to tell you this, is this still worth my time. Most people who abandon a form do not decide to abandon it. They stall on one field and drift away.
Which fields stall people is more predictable than it looks. HubSpot looked at more than 40,000 landing pages and found that adding single-line text fields barely moved conversion rates, while multiple text areas and multiple dropdown menus were strongly associated with lower ones. The count matters less than the kind. Three short text inputs cost you almost nothing. Two open-ended essay boxes and a pair of long select menus cost you real inquiries.
The takeaway is not “make every form tiny.” It is that the expensive fields are the ones that require thinking, and you should be able to name what you gain from each one.
Which fields actually earn their place
For a service business taking inquiries, the honest minimum is three: a name, a way to reach them, and room to say what they want. Everything past that has to justify itself against a simple test — would a missing answer here change what you do next, or does it just save you a question in your reply?
- Name and email. Required. These are the form.
- Message. Required, and give it a real prompt. “Tell us about your project” gets you a paragraph. An unlabeled box gets you “call me.”
- Phone. Optional. Always optional. More on this below.
- Which service or location. Worth it only if the answer routes the message to a different person or inbox. If every submission lands in the same place, this field is doing nothing but adding a decision.
- Budget range. Useful for qualifying, costly in submissions, and routinely answered wrong by people who genuinely do not know yet. Keep it optional if you keep it at all.
- “How did you hear about us?” Cut it. Your analytics already answer this better than a dropdown will, and the guesses people type in are not data you can act on.
The phone field deserves its own note because it is the one people argue about most. Making it required reads as a condition: before I answer your question, you have to let me call you. Plenty of prospects will do that. A meaningful share will not, and you never hear from them, so the cost is invisible while the benefit — a phone number on every lead — is sitting right there in your inbox. Mark it optional and label it as such. The people who want a call will fill it in.
Route the form instead of lengthening it
Sometimes the reason a form has grown to nine fields is that it is carrying work it should not be carrying. One form is trying to serve four different audiences, and the extra fields exist to sort them out after the fact.
The better fix is usually more forms, each shorter. When I built the website for St. Elizabeth Shelter and Supportive Housing in Santa Fe, the organization had genuinely distinct inquiries arriving at once — someone seeking shelter, someone wanting to volunteer, someone making a donation, someone from the press. Those are not variations on one message, and a single long form with a “reason for contacting us” menu would have served all four badly. The site routes them instead: short, purpose-specific forms that land with the right staff member. Each one asks less than the combined version would have.
You can apply the same thinking at a smaller scale. A contact form, a quote request, and a careers inquiry are three different conversations. Let them be three short forms rather than one long one with branching logic.
Labels, errors, and the floor you cannot go below
A short form still fails if people cannot work it. Three things matter more than anything cosmetic.
Use visible labels above the fields. Not placeholder text inside them. Placeholder-only labels disappear the moment someone starts typing, which strands anyone who gets interrupted, and they are a known failure in usability testing — the Baymard Institute has documented the problem repeatedly. WCAG, the accessibility standard most compliance claims are measured against, requires labels or instructions for inputs under success criterion 3.3.2. Placeholder text does not satisfy it.
Make errors specific and attached to the field. “Please check your entries” sends someone hunting. “Email address is missing an @” tells them what to fix. WCAG 3.3.1 and 3.3.3 cover identifying the error in text and suggesting a correction where one is known.
Do not ask twice. WCAG 2.2 added success criterion 3.3.7, Redundant Entry, which says people should not have to re-enter information they already gave in the same session. Confirm-your-email fields are the common offender, and modern browsers autofill well enough that they no longer earn the friction.
One more thing worth saying plainly: spam is not a reason to add fields. A honeypot field hidden from humans, plus a server-side check and rate limiting, stops the overwhelming majority of automated submissions without asking a real visitor to do anything. Puzzle-based challenges push work onto exactly the people you want to hear from, and they are an accessibility risk on top of it.
How many fields should a contact form have?
Three to five for a general small-business contact form: name, email, message, and optionally a phone number and one routing choice. Go above five only when a specific field changes what happens to the submission — a required file upload for a print job, a service area for a business that cannot travel, an appointment window for a booking request. If a field only saves you from asking a question in your reply, ask it in the reply. You will get more inquiries to answer.
A fifteen-minute audit
Open your own contact form on your phone. Fill it in as a stranger would, and count the fields you had to stop and think about. Then check the last twenty submissions and ask which fields you actually used when you replied. Most people find at least two fields that nobody reads and one that is quietly required when it should not be.
Patrick Iverson is a brand strategist and custom WordPress developer in Santa Fe, New Mexico, who has run an independent practice here since 2001. If you are not sure whether your forms are helping or filtering, that is usually a question worth asking alongside the rest of your web design — send a note and I will take a look at what you have.
