Guide
Contact forms that get filled in: a field-by-field guide
How to design an enquiry form that people actually complete: which fields to keep, what to remove, where to place it, what happens after submit, and the privacy basics.
VAULT 33|27 · Updated 12 November 2026 · Reviewed 12 November 2026 · 3 min read
The principle
Every field is a small cost to the visitor. Ask only for what you need to reply well and book the next step. You can learn the rest in the conversation that follows.
Field by field
| Field | Keep, change or remove? | Why |
|---|---|---|
| Name | Keep, as one field | Two fields for first and last name add effort for little gain |
| Keep | Needed to reply in writing | |
| Phone | Keep, but consider making it optional | Many service clients prefer a call; some refuse to give a number |
| Preferred contact method | Add | Calling someone who wanted email is a poor start |
| Service needed | Keep, as a short list | Routes the enquiry and personalises the reply |
| Postcode or area | Keep if you serve areas | Lets you confirm coverage straight away |
| Message | Keep, optional, with a helpful prompt | "Tell us what you need and when" gets better answers than "Message" |
| Budget | Usually remove | Unless you must filter, it puts people off at the first step |
| Company size, job title, how did you hear about us | Remove | Capture source automatically instead |
| CAPTCHA puzzles | Replace | Use invisible spam protection such as a hidden honeypot field |
Design details that matter
- Labels above fields, always visible. Placeholder text that disappears when you type is not a label.
- The right keyboard on mobile: email fields open the email keyboard, phone fields the number pad.
- Autofill switched on, so browsers can complete name, email and phone.
- Clear errors, next to the field, saying how to fix it, without wiping what was typed.
- A specific button: "Request my quote" or "Book my call", not "Submit".
- Accessible to everyone: labels connected to fields, visible focus, enough contrast and keyboard access, in line with WCAG.
Where to put it
On service pages, place a short form or a clear button near the top and again at the end. On mobile, a tap-to-call or WhatsApp button next to the form often captures people who will never type a message.
What happens after submit matters most
| Moment | Best practice |
|---|---|
| On screen | A confirmation that says what happens next and when |
| Within a minute | An email or message that answers common questions and offers a booking link |
| Within minutes | A person, or an AI assistant clearly labelled as AI, follows up |
| In your systems | The enquiry lands in your CRM with its source, never only in an inbox |
A great form followed by a slow reply still loses the client. See our guide to lead response time.
Privacy basics
Tell people what you will do with their details, link your privacy policy next to the button, and do not pre-tick marketing consent. Under UK and EU data protection law, people have the right to be informed about how their data is used.
Test it every month
Send a test enquiry through every form, on mobile and desktop, and check it arrives in the right place with its source and that the auto-reply works. Broken forms are one of the most common and most expensive website problems we find, and our VAULT Business Audit checks that your enquiry paths exist.
Sources
Open your vault.
A free systems audit of your business: where enquiries leak and exactly what we would build.
Book your free audit