Skip to content
All articles
Form Design6 min read

More fields, fewer enquiries: How to simplify your contact form

Ask the right questions at the right time. From required fields to error messages, design a form that makes the first conversation easier.

A paper form with three fields and a red paper plane on a lilac background
Conceptual cover image · Created with AI assistance.

Don’t turn the first message into a project brief.

A visitor has explored your services, looked at a few projects and decided to get in touch. Then the contact form asks for company size, budget, phone number, deadline and a detailed list of requirements. Before you’ve even met, they’re expected to describe the entire project. The problem isn’t just the form’s length. It’s when those questions are being asked.

The purpose of first contact is to start the next meaningful conversation. Preparing a proposal, exploring requirements and defining scope can follow. Before designing the form, answer this question: What will we do first when this message arrives? If the answer is to reply by email, it becomes easier to see which details you really need at the start.

Fewer fields won’t always lead to better results. Technical support requests, job applications and new project enquiries need different forms. An order number may help a support team find the right record, but asking for the same level of detail from someone exploring a new website may be unnecessary. Simplification should follow the purpose of the form.

Give every field a clear role.

List the questions in your current form. Beside each one, note who will use the information and which decision it will influence. “We might need it later” isn’t enough on its own to make a field required at the first step. If your team doesn’t use some of the data, reconsider why you’re still collecting it.

Example field review for a new project enquiry form
InformationRole at first contactPossible approach
Name and emailAddress the person and replyAsk at the start
Brief description of the needUnderstand what the conversation is aboutAsk with a helpful example
Phone numberSpeak by phoneMake it optional or ask later if email is enough
Budget and target dateAssess scope and fitAsk if essential to the first response; allow uncertainty
How did you hear about us?Understand how they found youKeep it optional

This table is an example to support decisions, not a fixed template. A visitor without a confirmed budget can still start a valuable conversation. If your business needs to ask about budget, allow an honest answer such as “Not yet decided”. Forcing people to choose an arbitrary range can reduce the quality of the information you collect.

Use conditional fields only where there’s a meaningful dependency. Showing a website link field after someone confirms they have an existing product makes sense. Splitting a handful of simple questions into multiple steps can add unnecessary navigation.

Tell people what you need from them.

A blank text box can feel daunting, especially for someone using your services for the first time. Instead of simply labelling it “Your message”, add a short explanation of what would be useful to know. This helps people start without feeling they need to write a complete brief.

An unclear request

Project details

A broad label with no guidance. People must decide for themselves how much to write.

A helpful prompt

What do you need?

Thinking about a new website or improving an existing product? A few sentences are enough to get started.

These copy examples are illustrative.

People should still understand a field’s purpose after they start typing. That’s why placeholder text alone isn’t always enough. W3C’s guide to labelling form controls explains the importance of descriptive labels associated with their controls. Even if a label is visually hidden, its accessible name must remain, and the field’s purpose should be clear from the context on screen.

Give the submit button an equally clear label. “Send message” and “Get a quote” create different expectations. If submitting the form won’t produce an immediate price, the button shouldn’t imply that it will. If you promise a response time, use one your team can reliably meet.

The design doesn’t end at the send button.

An empty form can look flawless. The real experience emerges when someone enters an invalid email, the connection slows down or submission fails. Design the states that explain what happened and how to continue from the outset.

Use a message that shows how to fix the problem, such as “Check your email address uses the format name@example.com”, instead of “Invalid entry”. Don’t communicate an error through a red border alone. W3C’s guide to form notifications covers explaining errors in text and identifying the relevant field. Feedback must also be available to assistive technologies.

Four form states to design
StateWhat the user needs to know
Missing or invalid informationWhich field has a problem, and how can it be fixed?
SendingThe request is being processed; there’s no need to press again.
Couldn’t sendIs the information saved, and how can they try again?
Message receivedSubmission is complete. What happens next?

Show a success message only after the server confirms success. Saying “Your message has been sent” as soon as someone presses the button can conceal a failed submission. Keeping their text and re-enabling the button for another attempt are also part of the flow.

Try the form on a real mobile device. Does the email field open the appropriate keyboard? Can people find the error message while the keyboard is open? Is there enough space to write a longer message? Then use only the keyboard to check focus order and visible focus indicators. A desktop screenshot can’t answer these questions.

Look beyond the number of messages received.

Receiving more messages after simplifying the form isn’t enough to judge its success. Consider enquiries that lead to conversations, irrelevant messages and the time your team spends filling in missing details. The aim is to make contact easier while creating a useful starting point.

If you can measure it, distinguish visitors who see the form, start filling it in and successfully submit it. If traffic sources or campaigns changed during the same period, don’t attribute every difference to the form design. With low traffic, a task-based usability study with a few people may be more revealing than a single percentage.

Before you publish

  • Is every required field essential to the first response?
  • Can the form be submitted with optional fields left empty?
  • Is each field’s purpose clear after text has been entered?
  • Does the helper text make it easy to start with a short answer?
  • Does each error message explain the problem and how to fix it?
  • Is the user’s text preserved if submission fails?
  • Does the success message reflect a confirmed submission?
  • Have mobile and keyboard interactions been checked?

A good contact form makes it easier for visitors to start a conversation and helps your team begin in the right place. Ask for enough information at the first step, then work out the details together as the conversation develops.