The Form That Loses Customers One Field at a Time

A financial services firm's mobile contact form asked for a phone number, but tapping into that field brought up the standard full alphanumeric keyboard instead of a numeric keypad — a small thing, technically still usable, but it meant every visitor filling out the form on a phone had to manually hunt for numbers among rows of letters, rather than getting a keypad built for exactly that input. Multiply that kind of small friction across every field in a longer form, and what looks like a minor technical detail becomes a meaningful source of drop-off, invisible unless someone actually fills out the form on a phone themselves and pays attention to how it feels.

Mobile typing is fundamentally harder than desktop typing

On a desktop, typing into a form field is fast and low-effort regardless of field type — a full keyboard is always available and errors are easy to spot and correct. On a phone, every keystroke is a small deliberate tap on a cramped virtual keyboard, autocorrect sometimes interferes, and switching keyboard modes mid-form (letters to numbers to symbols) adds friction each time it happens. A form designed without this difference in mind — treating mobile as just a smaller version of desktop — routinely underperforms, not because the information being asked for is unreasonable, but because supplying it is more physically effortful than it needs to be.

Getting the keyboard type to match the field

• A phone number field should trigger a numeric keypad, not the full alphabet keyboard
• An email field should trigger a keyboard with an easily accessible @ symbol and a '.com' shortcut where supported
• A field asking for a numeric quantity or a zip/postal code should similarly default to a numeric input mode
• A date field benefits from a native date picker rather than expecting a visitor to type a date manually in a specific format
• These input types are set with standard HTML form attributes and typically require no complex development work to add correctly

Field count matters as much as field type

Every additional field on a form is another small decision point and another small chance for a visitor to hesitate, get distracted, or simply decide the effort isn't worth it. A form asking for name, phone, email, preferred contact time, budget range, and a detailed message will convert fewer completions than a shorter form asking only for name and phone, even when the longer form's extra fields would genuinely be useful information for the business. The tradeoff is real: more fields can mean better-qualified leads, but also fewer total leads, and the right balance depends on the business's actual priorities — high volume of rougher leads versus fewer, better-qualified ones.

1. List every field currently on a form and ask whether it's truly necessary to start the conversation, or could be gathered in a follow-up call or email instead
2. Mark optional fields clearly as optional rather than leaving visitors to guess whether something is required
3. Consider a shorter initial form with a note that more details can be discussed on the call or in a follow-up message
4. Test actual completion rates before and after trimming a form, rather than assuming shorter is always better without checking

Every field beyond what's genuinely necessary to start the conversation is a small bet against completion, made in exchange for slightly more upfront information.

Autofill support saves real effort

Browsers and mobile operating systems can automatically fill in a visitor's name, address, email, and phone number if a form's fields are marked up in a way the browser recognizes — using standard field names and autocomplete attributes. A form that doesn't support this forces every visitor to type all of that information manually, even though their device may already have it saved and ready to insert with a single tap. This is one of the highest-value, lowest-effort fixes available, since it requires no visual redesign — only correcting the underlying field attributes.

Error messages that don't punish the visitor for a small mistake

A visitor who mistypes an email address or leaves a required field blank should get a clear, specific, immediately visible message about exactly what needs fixing — not a vague 'something went wrong' after the whole form gets wiped and has to be filled out again from scratch. Losing already-entered information because of one field's error is one of the more reliable ways to lose a visitor who was otherwise ready to submit.

Testing the whole thing end to end

The only reliable way to catch these problems is to actually fill out the form on a real phone, field by field, paying attention to which keyboard appears, whether autofill works, and how errors are communicated. This kind of hands-on testing catches problems that reviewing a form's code or design mockup alone would miss. Form and conversion design is part of what's reviewed in a free audit.

← Back to all articles