Enquiry forms that work on a small screen, where most people are

6 days ago
3 min read

Updated: 3 days ago

Introduction

Most enquiries now begin on a phone, frequently one-handed, in the evening, on a patchy connection. Most enquiry forms are designed on a large screen with a keyboard, tested in the same conditions, and never attempted in the situation where they will actually be used.

The mismatch produces losses that are entirely invisible from the business side. Nobody reports that the keyboard covered the submit button, that the date picker would not work, or that the page reloaded and cleared everything. They simply give up, and the business concludes that fewer people are enquiring.

1. Enquiry forms that work on a small screen have to be tested on one

The starting requirement.

Not a narrowed browser window. An actual phone, on mobile data, held in one hand. The problems that appear are different from anything a desktop preview shows. Do it monthly, and do it on both an older and a newer handset if you can, because behaviour differs.

2. Keep the number of fields very low

Where it matters most.

Typing on a phone is slow and error-prone, and every field is disproportionately expensive. A form that is tolerable on a desktop can be abandoned on a phone. Three fields is a reasonable target and four is usually the practical maximum.

3. Use the right keyboard for each field

The small technical detail.

Number fields should bring up a numeric keypad and email fields an email keyboard. Getting this wrong makes entry noticeably harder and it is a one-line fix. Most form builders expose this setting and most people leave it on the default.

4. Make the buttons large and clearly separated

The physical constraint.

Small or closely spaced controls are hard to hit accurately, and a mis-tap that clears a form is where people stop. Generous spacing is not decorative here. Check it with a thumb rather than an index finger, which is how phones are actually used.

5. Avoid date pickers and complex controls

The common failure.

Fiddly calendars, sliders and multi-level dropdowns are difficult on a small screen. A plain text field asking when they need it works better and irritates nobody. Free text is also more informative, because people explain rather than selecting the nearest option.

6. Never lose what they typed

The unforgivable error.

A validation failure, a back button or a reload that clears the form ends the enquiry outright. Preserving entered content through errors is the highest-value fix on this list. Nobody retypes a paragraph they already wrote once.

7. Show errors clearly and next to the field

The recovery detail.

A message at the top of a long form is off-screen on a phone. Errors have to appear where the problem is, in plain language, saying what to do. Scroll the field into view automatically if you can.

8. Confirm submission visibly

The reassurance.

On a poor connection people are unsure whether it sent. A clear confirmation prevents duplicate submissions and the assumption that it failed.

9. Offer a phone number and a message option beside it

The escape route.

Some people will abandon the form regardless. A tappable number and a messaging option beside it catches them rather than losing them.

Be careful about consent banners and overlays on small screens, where they occupy a much larger share of the display. A necessary notice that covers the entire form is a compliance requirement implemented in a way that prevents the enquiry.

Conclusion

Test on an actual phone, because that is where the enquiry is being made.

Keep the number of fields very low since typing is slow, set the correct keyboard type for each field, make buttons large and well separated, avoid date pickers and complex controls, never clear what somebody has typed, show errors beside the relevant field in plain language, confirm submission visibly, and put a tappable phone number and a messaging option beside the form.