Website contact forms: how to get better enquiries?

A good website contact form asks only for the information needed to start a conversation, explains what happens next and makes errors easy to correct. It also needs to work on a phone, confirm that the message was accepted and protect the receiving inbox from spam. Removing fields alone will not help if a visitor cannot see why they should enquire or what will happen after they press the button.

A service business may want to maximise the number of initial conversations. A supplier quoting complex projects may deliberately ask a few qualifying questions. There is no single layout that fits every website. The useful balance is between an easy first step and enough context to provide a relevant reply.

A good form starts before the first field

Give a prospective client a reason to share their details. The copy next to the form should briefly explain:

• what they can ask about,
• which details will help you respond,
• who will answer the message,
• when they can realistically expect a reply,
• whether phone or direct email is also available.

“Contact us” answers none of those questions. A clearer prompt relates to the decision, for example: “Tell me what you need the website to do. I will reply with the questions required to define the scope and next steps.” The stated response time must be realistic. Promising a reply within an hour weakens trust if the business normally responds the next day.

How many fields should a website contact form have?

There is no universal number. A sensible starting point for a straightforward enquiry is:

• name,
• email address or phone number,
• message.

If the business needs more context to route the enquiry, add a short choice such as the type of service. A budget or deadline question is useful only when the answer materially affects the scope, availability or quoting process.

Do not require a surname, company name, job title, phone number and email address merely because the CRM has columns for them. The EU General Data Protection Regulation includes the principle of data minimisation: personal data should be adequate, relevant and limited to what is necessary for its purpose.

When an extra question helps

A qualifying field can improve the conversation when it:

• separates website, online store and support enquiries,
• identifies a request the business does not provide,
• gives the supplier enough context for a useful first reply,
• saves the prospect from sending another email with basic details.

When an extra question gets in the way

A field is unnecessary when its answer does not change the next step. A long project brief before any human contact can put off someone who is still exploring options. In that situation, collect the essentials and discuss detail after responding.

Use visible labels, not placeholders alone

Placeholder text disappears when a person starts typing, so it should not replace a label. The user should always know whether a field expects an email address, phone number or project description.

The current W3C forms tutorial, reviewed on 14 September 2026, recommends associated labels, instructions where they are needed, logical grouping and clear notifications about errors and successful completion.

In practical terms, the form should provide:

• a visible label for every field,
• a clear indication of optional or required fields,
• a format example only where the expected answer may be unclear,
• the appropriate input type for email addresses and phone numbers,
• browser autocomplete support,
• a keyboard focus order that follows the visual layout.

On mobile, a user should not need to zoom into a field. Buttons, checkboxes and the privacy link need enough space to be selected without hitting a neighbouring control.

Validation should help people finish

“Invalid data” does not explain what needs fixing. An error should identify the affected field and provide a direct instruction, such as “Enter an email address in the format name@example.com”.

The GOV.UK pattern for recovering from validation errors recommends retaining the values already entered, showing an error summary and placing a message beside each affected field. The user can correct the problem without completing the entire form again.

Browser validation can improve the experience, but it does not secure the submission. OWASP input validation guidance states that every input must also be checked on the server because JavaScript-only controls can be bypassed.

The button and confirmation must describe what is happening

“Send enquiry” is usually clearer than a generic “Submit”. Once selected, the button should show a sending state and prevent accidental duplicate submissions.

After the server accepts the data, the visitor needs an unmistakable confirmation. A useful success message covers:

• confirmation that the message arrived,
• the expected response time,
• an alternative channel for an urgent matter,
• whether an email receipt or copy has been sent.

Failure needs equal attention. If the mail service does not accept the message, the website must not display success. It should preserve what the user wrote and offer a retry or a direct email address.

Stop spam without punishing the prospect

A public form will eventually be tested by bots. Protection should use several layers while remaining as unobtrusive as possible:

• a honeypot field,
• submission rate limits,
• request origin checks,
• reasonable input length limits,
• server-side validation,
• safe encoding when content is placed in an email or dashboard,
• error logging that avoids unnecessary personal data.

An intrusive CAPTCHA should not be the default. It can reduce accessibility, delay the page and block legitimate users. If quieter controls are insufficient, consider applying an additional challenge only to suspicious requests.

Privacy is more than one checkbox

The form needs to identify the data controller and explain the purpose, lawful basis, retention period or the criteria used to set it, recipients and the person's rights. A concise notice can link to a readable privacy policy, but the destination should not be hidden behind vague wording.

Consent is not automatically the correct lawful basis for every response to a normal enquiry. The basis depends on the purpose and circumstances. If the business wants separate permission for future marketing, that option should be voluntary, specific and unticked by default. The final wording and basis should be reviewed by the person responsible for data protection instead of being copied from an unrelated website.

Measure accepted enquiries, not button clicks

A click does not prove that the message arrived. Record the conversion only after a successful server response or a confirmation page that is available following an accepted submission.

Useful measurement can distinguish between:

• starting the form,
• an accepted enquiry,
• validation failures,
• a delivery or server error,
• the visit source and campaign.

Google's official guide to website conversion measurement explains how actions completed on a website can be configured as conversions. The form and its success state should be ready before advertising starts. The article on choosing a landing page or website for Google Ads covers the destination decision.

What to include in the supplier's scope

Do not approve a contact form based on appearance alone. The project scope should define:

1. each field, its purpose and whether it is required or optional,
2. behaviour on mobile and desktop,
3. labels, keyboard order and error messages,
4. browser and server-side validation,
5. anti-spam controls,
6. the receiving address and a correct reply-to value for the prospect,
7. success messaging and failure handling,
8. a link to the current privacy policy,
9. measurement of accepted enquiries,
10. an end-to-end test using a real message.

Treat the form as part of the website project from the start, alongside content preparation and technical SEO. Test it again after every major release or website redesign.

In the AMCompany service scope, the contact form is designed as part of the complete route from the offer to an enquiry. You can also review selected website projects. If an existing form is broken, attracts mostly spam or asks prospects to complete a long questionnaire, send the website address. It will then be easier to determine whether the form alone needs changing or whether the problem begins earlier in the offer and page structure.