The short answer
Before changing a form, decide what you need to know to reply well, who should receive each message, how spam will be blocked and what the visitor sees after sending. Keep fields to the minimum useful. After the change, test with a real submission, confirm the email arrives, and watch enquiry numbers for a few weeks.
Start with the job the form does
A form exists to start a conversation you can act on. Write down, in one sentence, what you need in the first message to reply properly. For a plumber it might be name, phone, postcode and what is wrong. For a consultancy it might be name, work email and a short description of the problem. Anything beyond that is a cost to the visitor.
Every field is a small decision the visitor has to make, and some will simply leave. There is no universal best number of fields, and we do not claim one. The honest approach is to ask only for what you will use, and to test changes rather than assume.
Fields: what to keep, what to drop, what to add
| Field | Keep or drop | Why |
|---|---|---|
| Name | Keep | You need it to reply politely |
| Keep | The channel your reply goes to; validate the format | |
| Phone | Optional unless you phone back | Required phone fields put people off if you will only email |
| Message | Keep | Shows intent and lets you prepare |
| Company, job title | Add only if you qualify leads | Useful for B2B, a barrier for consumers |
| Budget or timeline | Add with care | Helps sorting, but some people will abandon rather than answer |
| "How did you hear about us?" | Optional | Useful for marketing, harmless if not required |
Mark which fields are required, and label every field clearly. A label should stay visible while the person types, not vanish into a placeholder.
Make the form easy to complete
Small technical details change how easy the form is. The HTML autocomplete attribute lets browsers fill in known details such as name and email, saving the visitor from retyping. web.dev explains that browsers store a field's value and offer it on other sites, and that developers help by setting the right autocomplete value. Using proper field types (email, telephone) also gives mobile users the right keyboard.
On a phone, check that fields are large enough to tap, that the keyboard does not hide the submit button, and that error messages say exactly what is wrong. Test it on a real phone, not only on a resized desktop window.
Routing: who gets the message
Routing means where a submission goes. The simplest setup sends everything to one inbox. As a business grows you might send sales enquiries to one person and support questions to another, based on a dropdown the visitor picks. Decide this carefully, because a message that goes to someone who has left the company is a lost lead.
Use a shared address such as hello@ or enquiries@ rather than one person's inbox, so leave and holidays do not break it. Tell us the exact addresses, spelled out. If messages stop arriving after a change, see forms not sending emails. Many problems come from email delivery settings rather than the form itself.
Spam protection without scaring off real people
Public forms attract automated spam, and most protection is invisible to real visitors. A honeypot is a hidden field that people never see but bots fill in, so any submission with it filled is rejected. web.dev mentions honeypot fields as a case where autofill is turned off for that field, so browsers do not accidentally fill it for real users. Many sites also use a bot check such as Cloudflare Turnstile or similar, and a spam filtering service.
Avoid puzzles that make real people work, such as distorted letters. Each extra step may cost real enquiries. If you suddenly get a flood of junk, tell us which form and roughly when it started. If real messages are being caught as spam, tell us that too, because over-aggressive filters are a quiet source of lost leads.
Confirmation message and what happens next
After someone sends a form, they should know it worked. A good confirmation says what happens next in plain words: "Thanks, we have your message and someone will reply to you by email." Do not promise a specific response time you cannot keep. A separate thank-you page also helps you measure form submissions in GA4, because each submission leads to a distinct page you can count. See track calls and forms.
Consider an automatic email to the visitor with a copy of what they sent. It reassures them and gives you a record, but make sure it does not land in their spam folder, which depends on your email settings.
Testing the form after a change
- 1Submit a real test through the live form on the preview or site, using an email address you can check.
- 2Confirm the message arrives at every intended address, with all fields included, and that replying goes to the visitor.
- 3Check spam folders and any notification tools connected to the form, such as a CRM or chat alert.
- 4Submit it incorrectly: leave required fields empty, enter a bad email, and make sure the errors are clear.
- 5Test on a phone, in a private window and with your browser's autofill.
- 6After it goes live, check that submissions are still being counted in your analytics.
Example: Cutting a form from eight fields to four
An accounting firm's form asks for name, email, phone, company, role, number of employees, budget and message, all required. The owner wonders why so few people finish it. Together we decide they only need name, email, company and message, and that phone becomes optional. The old fields are kept for the first call. We change the form, route messages to a shared enquiries address, and test it. The owner watches submissions for the next six weeks and compares them with the six weeks before. Whether it helped is judged from those counts, not guessed.
When to ask us
Send a request through the support form listing the fields you want (and which are required), the exact email addresses for each type of message, the confirmation text, and whether you want a thank-you page. Tell us if spam is the reason for the change. Never send email passwords, and we do not need them. For general guidance on describing changes, see request a website update.
