VDNX
ESLet’s talk

Web design & development·5 min read

Which fields a contact form actually needs

A contact form should ask for the context needed to respond. Decide field by field, and give equal attention to what happens before and after submission.

Decide what you need to give a first response

Choosing contact form fields starts with defining the conversation you want to open. A sales enquiry, a support issue and a job application need different information. Combining them in one long form may require each person to answer questions that do not apply to them. Before designing the form, write down what your team should be able to do with the message it receives.

For an initial website enquiry, for example, it may be enough to know how to reply, what someone wants to build and how far their idea has developed. The first contact does not need to become a complete project estimate. If a question will only be useful after a conversation, consider asking it then. This gives every field a purpose you can explain.

Give every field a job

Make a list with three columns: the information requested, the decision it supports and whether you need it now. If you cannot fill in the second column, reconsider the field. A name can help you address the person, an email address allows a reply and a message describes the need. A company name can add context, but there may not be a company yet.

A phone number needs its own decision. If the initial reply will be by email, making a number mandatory needs a stronger reason than that it might be useful one day. The same applies to a budget or an exact date. They can help assess a particular request, but it may also be reasonable to let someone say they do not know yet.

  • Required: you cannot process the enquiry offered by this form without the information.
  • Optional: it helps prepare the response, but you can begin without it.
  • For later: it belongs in a subsequent conversation or a different process.

Use fixed options when they change the next step

A selector makes sense when its answer helps organise the work. Choosing between a new website, improving an existing one or another enquiry can help prepare follow-up questions. Keep the options understandable to someone unfamiliar with your internal structure. Provide an alternative when none fits, rather than forcing the visitor into an incorrect category.

Avoid asking for the same information twice. When someone arrives from a service page, you can suggest that service as an initial selection while allowing them to change it. If fields appear conditionally, explain why and check what happens when the previous choice changes. The final message should remain coherent, without hidden answers that no longer apply to the request.

Keep every question visible while someone types

Keep a visible label beside each field. MDN explains that correctly associating it with the control lets assistive technology identify its purpose and increases the area people can tap to activate it. An example inside a field can provide guidance, but it should not be the only way to remember what the question asks.

Field names should describe the information, rather than the system processing it. Email address is clearer than contact identifier. If a particular format is needed, explain it before an error occurs. MDN also documents autocomplete, which indicates to the browser what information is expected and can assist with familiar details such as a name or email address.

Help people write a message without requiring a full brief

An open question benefits from a little guidance. For a website design enquiry, you might suggest explaining what the person needs, whether they already have a site and what they would like to improve. Present these prompts as help, rather than a list of requirements they must understand before being allowed to contact you.

Do not ask for passwords, service keys or sensitive documents in an initial message. If files or access need to be shared later, agree a suitable channel for that task. Set a message limit that leaves room to explain the request, and make it clear when the person approaches it. The aim is to obtain useful context, rather than collect everything possible.

Distinguish an incorrect detail from a failed submission

MDN's form validation guide explains how clear messages help people correct their details and demonstrates aria-live to announce errors to screen readers. In a business enquiry, that could mean a clear instruction to check an email address, instead of a generic warning that leaves the visitor guessing what went wrong. Also prepare an understandable confirmation for when the request has been accepted.

Design separately for the case where details are valid but the service does not respond. Keep the text in the form and provide a next step, without displaying a confirmation you cannot support. OWASP distinguishes checking a value's format from checking whether it makes sense for the operation. Rules should accept legitimate information and apply suitable limits; validation does not replace other security measures.

Review the form as a complete conversation

Try the journey on a small screen, with a keyboard and while correcting a detail. Check what happens when optional fields are empty, a message reaches its limit or sending returns an error. Include the message your team receives in the review: a clear interface is of limited use if the final enquiry loses information needed for a reply.

Before adding another question, look for a specific gap in the enquiries you receive. You may need to change a label or a prompt instead of extending the form. A useful improvement helps both sides understand the next step. It does not need to aim for a fixed number of fields.

  • Does each question support a decision that belongs at this stage?
  • Is required information clearly distinguished from optional details?
  • Can someone correct an error without starting again?
  • Does the final status explain what has actually happened?

Sources and documentation

Content created with AI assistance. Check the sources, date and scope of each guide.

Let’s define the next step for your website.

Tell us what your business needs and where your current website falls short. We can help you define the scope.

Let’s talk about your idea