A visitor reads three of your pages, decides you are a plausible option, clicks contact, & meets eleven fields including company size, budget range & how they heard about you. They close the tab. You will never know they were there, & your analytics will record it as an ordinary exit.
Forms are where interest becomes enquiry, & they are consistently the least examined element on a website. They tend to be designed once by whoever needed the data, expanded whenever someone requests another field, & never reviewed against the cost of collecting it.
Every field has a price
The framing that fixes most form problems is this: each field is a transaction. You are asking the visitor to spend effort in exchange for a benefit. If the benefit is a phone call they are not certain they want yet, your budget for asking is small.
So audit field by field & ask two questions of each one. Do we genuinely need this before the first conversation? & could we find it out ourselves, or ask it on the call?
Job title, company size, budget range, timeline, how you heard about us: all of these are typically establishable in the first two minutes of a call. Collecting them on the form converts a low-commitment action into a qualification interview, at the exact moment the visitor is least invested.
The correct number of fields is the number you need to make the next contact. For most service businesses that is a name, one contact method, & a sentence about what they need.
Find where people actually stop
Do not guess which field is the problem. Instrument it.
- Field-level analytics record which field was last interacted with before abandonment. This is the single most useful diagnostic & it works at low traffic volumes.
- Session recordings filtered to sessions that reached the form & did not submit. Watch twenty. You will see hesitation, repeated corrections & outright confusion.
- Time-per-field data shows where people struggle even when they eventually complete. Long dwell on a single field usually means the label is unclear or the format expectation is hidden.
- Error frequency by field reveals validation that is fighting your users rather than helping them.
Common findings: a phone field rejecting valid formats, a required field whose purpose is unclear, a dropdown with no option that fits, & a message box that looks obligatory & intimidating.
Design decisions that consistently help
These are not stylistic preferences. Each addresses a documented source of friction.
- Labels above fields, always visible. Placeholder-only labels disappear when typing begins, so users lose track of what they are entering & cannot check their work.
- Single column layout. Two columns create ambiguity about reading order & slow completion.
- Mark optional fields rather than required ones when most are required, & the reverse when most are optional. Whichever is rarer gets the marker.
- Correct input types. A phone field should bring up a numeric keypad on mobile. An email field should bring up the email keyboard. This costs nothing & removes real friction.
- Permissive validation. Accept phone numbers with spaces, dashes & country codes, then normalise them yourself. Rejecting a valid number because of formatting is an unforced error.
- Inline validation on blur, not on keystroke. Telling someone their email is invalid while they are still typing it is hostile.
- Never clear the form on error. This remains distressingly common & it guarantees abandonment.
- Descriptive submit buttons. "Request a call back" outperforms "Submit" because it restates the outcome at the moment of commitment.
Mobile is the default, not the exception
Most enquiry traffic in Nepal arrives on a phone, frequently on a mid-range device over a variable connection. Test your form under those conditions rather than on a desktop browser resized to look narrow.
Specific things to verify on a real device: tap targets are large enough to hit reliably, the keyboard does not obscure the field being edited, the page does not zoom unexpectedly when a field receives focus, dropdowns are usable with a thumb, & the submit button is reachable without excessive scrolling.
Also check what happens on a slow connection. A form that depends on a third-party script to submit will fail silently when that script times out, & you will never see the enquiry that was attempted.
The confirmation step nobody designs
Submission is not the end of the interaction. It is the moment of maximum uncertainty, & most sites answer it with a grey line of text saying thank you.
A good confirmation does three things. It confirms receipt unambiguously. It states what happens next & when, specifically, for example that someone will call within one working day. & it offers something useful in the meantime: relevant work, a guide, or the direct phone number if they would rather not wait.
Send a confirmation email too, from a real address that accepts replies. It reassures, it creates a record the prospect can find later, & it gives them a route to add information they forgot.
Multi-step forms, used correctly
Splitting a long form across steps can help, but only under specific conditions. It works when the first step is genuinely easy & low-commitment, when progress is clearly indicated, & when the number of steps is honest.
It fails when it is used to hide length. A visitor who reaches step four of an undisclosed seven abandons with more frustration than one who saw eleven fields upfront. If you use steps, show the count.
Also consider partial capture: if step one collects name & contact details, you have a usable lead even when the later steps are abandoned. That single design decision often recovers more enquiries than any wording change.
Rebuild, then verify
Work in this order. Remove every field you cannot justify. Fix labels, input types & validation. Test on a real mid-range phone. Rewrite the button & the confirmation. Then instrument the new form & watch twenty more sessions.
Measure completion rate, but also measure enquiry quality downstream. Shortening a form should increase volume without materially degrading quality; if quality collapses, you removed a field that was genuinely doing qualification work & you can reinstate it deliberately.
Forms are a small surface with an outsized effect on revenue. If you want yours reviewed as part of a wider conversion programme, see our CRO service, read more on the blog, or send us a link to your contact page.