Website forms · 10 Nov 2026 · 5 min read
Website contact forms: best practices for getting more completed enquiries
A contact form is often the last step before an enquiry. Every unnecessary field, unclear error or silent failure sends a would-be customer away, so small improvements here pay back directly.
The short answer
A good contact form asks only for what you need, labels every field clearly, explains errors in plain words, works with a keyboard and on a phone, and confirms that the message was sent. Add light spam protection, a privacy notice, and test delivery regularly so enquiries never vanish unnoticed.
Decide what the form is for
Start with the job. A general "get in touch" form, a quote request, a booking and a support form are different, and one form rarely does all of them well. Ask what you need to do with the message. If a person on your team needs to reply, you need a name and a way to reply. If you need to price a job, you need a few details about the job.
Consider offering the form beside other routes: a phone number, an email address and, if it fits, a booking link. Some people will always prefer to call. Put the options where visitors expect them, usually on a contact page and in the footer. The footer guide has more on placement.
Ask for less
Each field is a small cost to the visitor. Keep the ones that you cannot work without and make the rest optional or remove them. A phone number field is a useful test: if you will never ring, do not ask.
| Field | Keep it when | Tip |
|---|---|---|
| Name | Always, to address the reply | One field is often enough |
| Always, it is how you reply | Check the format, and accept unusual but valid addresses | |
| Phone | You will actually call | Make it optional if email works |
| Subject or topic | It routes the message | Use a short list, not free text |
| Message | Always | Add a hint on what helps you reply |
| Company | You sell to businesses | Optional |
Do not make people create an account just to ask a question.
Labels, hints and errors
Put a visible label above each field and link it to the field in the code, so screen readers announce it and a tap on the label focuses the box. Do not rely on grey placeholder text inside the box as the label: it disappears while typing and is often hard to read.
- Mark required fields clearly, in words as well as with a symbol.
- Use the right input type for email and phone so phones show a suitable keyboard.
- Turn on autofill attributes where suitable, to save typing. Check the HTML documentation for the right values.
- Check entries after the person finishes a field or on submit, and keep what they typed if there is an error.
- Write error messages that say what to do: "Enter an email address like name@example.com" is better than "Invalid input".
- Show errors beside the field and in a summary, and do not use colour alone.
These habits overlap with website accessibility, and they also lift completion for everyone.
Layout on phones
Most forms are filled in on a phone at some point. Use a single column, large tap targets and enough spacing between fields to avoid mis-taps. Put the submit button directly under the last field and give it a specific label such as "Send message" or "Request a quote". Test with the on-screen keyboard open, as it can hide the button. The principles in responsive web design apply here too.
Spam protection that does not block people
Forms attract spam, but a heavy puzzle in front of every visitor can lose genuine enquiries. Start with invisible checks: a hidden trap field, server-side validation, rate limits and a spam filter. Add a challenge only if needed. Log rejected messages for a while so you can spot false positives. Our dedicated guide to spam protection and CAPTCHA alternatives goes through the options.
Privacy and consent
A contact form collects personal information, so say what you will do with it. A line near the button, such as "We use your details only to reply to your enquiry", with a link to your privacy policy, is a good habit. If you also want to add people to a mailing list, use a separate, unticked option rather than bundling it with the enquiry. Rules about marketing consent differ between countries, so ask a qualified lawyer how they apply to you.
Confirmation and follow-up
After sending, show a clear confirmation on a dedicated page or in a visible message, saying what happens next and roughly when to expect a reply. A page of its own also lets you measure submissions as conversions; see what to put on a thank-you page. Send an automatic acknowledgement email only if it will reliably arrive and does not look like spam.
Then reply. A form that works perfectly but is answered slowly still loses customers. Decide who watches the inbox, how quickly you will respond and what happens when that person is away.
Test it like a customer
- Send a test message and check that it reaches the right inbox, not spam.
- Test with missing and wrong entries and read the messages.
- Use only the keyboard to complete and send the form.
- Test on a phone and a tablet.
- Check it still works after plugin, theme or hosting changes.
- Add the test to your regular maintenance.
Many forms fail quietly for weeks because email delivery was changed and nobody noticed. Keep a copy of submissions in the site or a spreadsheet as well as the email, so nothing depends on one route.
Think about where messages go. A single shared inbox that several people can see is safer than one person's address. If you offer topics, route each topic to the right team. Set up a simple internal rule for who replies and how fast, and mention your usual reply time on the form page so visitors know what to expect.
Review the enquiries now and then. Which questions come up again and again? They may belong on the page above the form, in an FAQ page, or in a short answer shown beside the form, which cuts unnecessary messages and makes the useful ones easier to handle.
Related guides
- Website development
- Website Accessibility Basics: WCAG for Business Owners
- Website Privacy Policy: What It Should Cover
- How to check and improve website speed
- Website forms how to get more submissions
- Wordpress website vs custom website
Questions and answers
How many fields should a contact form have?
As few as you can work with. Name, email and message cover many cases. Add others only if you will really use them, and make them optional where possible.
Should I use placeholder text instead of labels?
No. Visible labels stay on screen while typing and work better with screen readers. Use placeholder text only for short examples, if at all.
How do I stop spam without annoying visitors?
Use invisible checks such as a hidden trap field, server-side validation and rate limits first, and add a challenge only if spam continues. Log rejected messages to catch false positives.
Do I need a privacy notice on a contact form?
It is good practice to say how you will use the details, with a link to your privacy policy. Requirements differ by country, so ask a qualified lawyer what applies to you.
Why are my form messages not arriving?
Common causes are changed email settings, messages caught by spam filters, or a form plugin that has stopped working. Test regularly and keep submissions stored in more than one place.
Should the form redirect to a thank-you page?
Often yes. A clear confirmation reassures the visitor, and a separate page makes it simple to track submissions as conversions in your analytics.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.