Establish whether the form works
Before removing fields, trace an authorised test through the whole system. Confirm that submission creates the intended record, reaches the correct staff member and preserves the message. An animated success state does not prove that an email arrived or a CRM record exists.
Repeat with a slow connection, an invalid email address and a long message. Check whether retries produce duplicate enquiries. A failed request should not silently clear the visitor's work.
Give every field a job
| Field | Keep it when | Consider collecting it later when |
|---|---|---|
| Email or phone | The team needs that channel to reply | Another selected channel is sufficient |
| Service required | Routing depends on the service | The page already establishes it |
| Budget range | It changes qualification or recommended scope | The business has no useful ranges to offer |
| Company registration details | Required for the actual transaction | The visitor is only asking an initial question |
Mark optional fields clearly. Explain unusual requests at the point where the person decides whether to provide them. Do not claim that fewer fields always produce better enquiries: qualification requirements differ between a quick repair request and a complex development brief.
The contact-form friction guide provides further context for lead-generation website design.
Check accessibility and mobile entry
Use persistent labels instead of relying entirely on placeholder text. Make errors identify the affected field and describe the correction. Test keyboard access and visible focus, then check that the on-screen keyboard does not hide essential controls. The W3C forms tutorial is a useful reference for accessible labels, instructions and feedback.
Measure completion without mislabelling success
Separate form views, starts, valid submissions and qualified enquiries. Where analytics cannot reliably observe a stage, report that limitation. Count an accepted submission at the point the application confirms receipt, not whenever the submit button is pressed.
For example, if staff receive repeated blank messages, investigate validation and bot submissions before concluding that the offer attracts poor leads. A conversion-tracking review should reconcile website events with the enquiry records the team actually uses.
FAQ
Should we remove the phone-number field?
Make that decision from the follow-up process. If email is sufficient, a phone number may be optional; if a call is necessary, explain the reason.
Is a multi-step form always better?
No. It can help organise a complex brief, but also adds navigation and recovery requirements. Test whether visitors understand the stages and retain their answers.
What is the first check after changing a form?
Submit a controlled test and verify the stored record, confirmation and staff handoff. Also check one invalid submission so the failure path is usable.
If your website's form looks healthy but enquiries seem to disappear, get in touch with the affected route and the missing stage.