Website enquiry forms: fix the journey before buying more traffic

Your website enquiry form sits at the point where curiosity becomes intent. Visitors have found you, read your service page, and decided to reach out. Then they hit a form that demands too much, hides its labels, or breaks on mobile. They leave. You buy more traffic to compensate, and the cycle repeats.

Match the promise to the form

Review your highest-traffic entry points. For example, a landscaping business running Google Ads for "instant garden design quotes" should examine whether their form respects that promise. If the ad implies speed, the form should deliver it.

Ask only what progresses the enquiry

Forms accumulate fields over time. Someone suggests adding a "company size" dropdown. Marketing wants to know acquisition channel. The result is a form that interrogates rather than invites.

Identify the minimum viable information needed to respond meaningfully. For a service business, this typically means: what they need, when they need it, and how to reach them.

Label every field visibly

Placeholder text inside form fields disappears the moment visitors begin typing. This creates two problems: users forget what field they are completing, and they cannot verify their entry against the original prompt. The form design guidance recommends visible labels; placeholders should not replace them.

Position labels above or beside fields in clear, legible typography. For "Email address," "Phone number," and "Describe your project," the label remains visible throughout entry and review.

Enable suitable mobile keyboards

Test your form on actual devices, not just browser emulators. A field that works perfectly on desktop may present a full QWERTY keyboard for phone numbers on mobile, adding friction with every character. Date inputs require particular attention. Free-text date fields invite formatting errors. Structured inputs or pickers reduce this risk, though the specific approach should match your actual data requirements rather than applying universal prescriptions.

Handle errors accessibly

Error messaging separates functional forms from frustrating ones. When validation fails, indicate the problem clearly and preserve everything the visitor entered correctly. Nothing provokes abandonment like retyping a lengthy description because one digit in the phone number was wrong.

Colour alone cannot carry error communication. Red outlines help sighted users, but screen reader users and those with colour vision differences need explicit text. Associate error messages with their specific fields, explain the correction needed in plain language, and ensure entered values remain populated. Accessibility guidance emphasises that associated labels make field purpose available to assistive technologies, and testing across devices and navigation methods helps identify barriers (form accessibility guidance).

Confirm submission properly

A successful form submission requires two distinct confirmations: one for the visitor, one for you. The visitor needs immediate on-screen confirmation, ideally with expected response time.

Your confirmation is equally important. The form backend must successfully deliver the enquiry to an appropriate authorised recipient. A successful UI message does not prove owner delivery. Email routing failures, spam folder misdirection, and notification gaps all occur silently after the visitor sees confirmation.

Test delivery with sample data

Before declaring any form live, submit test enquiries using safe sample data. Check that enquiries arrive in the intended inbox, not spam. Verify that any attachments transmit intact. Confirm auto-reply functionality if configured. Test routing rules if enquiries distribute to multiple team members based on content.

Distinguish clicks from completions

Analytics configuration varies widely. Some setups count button clicks as conversion events. Others track only successful form submissions. This distinction matters enormously for diagnosis.

Review your analytics configuration to understand what you are actually measuring. If clicks and completions are conflated, you cannot identify where prospects abandon. Separate these events to reveal true completion rates and the specific points where journeys fail.

Checklist for your developer

When briefing form rebuilds or audits, ensure your developer addresses:

• Proper HTML input types for each field
• Visible, persistent labels associated with inputs for screen reader compatibility
• Client-side validation before submission
• Server-side validation
• Error messages that preserve entered values
• Keyboard-only navigation testing
• Submission alerts to appropriate authorised recipients
• Test enquiry procedure with documented results

Frequently asked questions

Should we use multi-step forms?

Multi-step forms can reduce perceived complexity when field grouping is logical. Contact details in step one, project specifics in step two, timeline in step three. Each step must display clear progress indication and allow easy backward navigation. Abandonment between steps is informative data. Single-step forms suit simpler enquiries. The choice depends on your actual field requirements and visitor expectations, not conversion optimisation mythology.

What if we need information that seems to create friction?

Some businesses genuinely require specific data to respond usefully. A bespoke manufacturing enquiry needs technical specifications. A wedding venue needs guest numbers and preferred dates. The principle is proportionality, not minimalism at all costs. When additional fields are necessary, explain why. "We need approximate guest numbers to check availability and provide accurate pricing" transforms an imposition into a service. Consider whether some fields can be optional, with clear indication of which information is required versus helpful.

A smooth enquiry process respects the effort visitors made to find you. Before increasing your traffic investment, audit the journey from arrival to submission. If your form needs technical refinement, our web development team can help diagnose friction points and rebuild for completion.