A contact form most often loses to its own length, not to the competition. Someone arrives with a specific question, sees seven fields—including company name and tax ID—and leaves. Good form design is mainly an exercise in subtraction: every field must justify its existence through something it genuinely changes in the handling process.
How many fields do you really need?
The rule is simple and inconvenient: ask only for information without which you cannot reply. Everything else can be established in your response. A ‘how did you hear about us?’ field may be valuable to marketing and costly to conversion—if it must remain, make it optional. The same rule applies in a chat window, where every field delays the first message; see our guide to pre-chat form questions.
Scroll the table sideways to see all columns.
| Field | When it is justified | When it hurts |
|---|---|---|
| First name | Almost always—it lets you reply like a human | When you also require a surname for no reason |
| When you reply by email | When you also require a phone number | |
| Phone number | When you genuinely call back | When it is required ‘just in case’ |
| Message | Always—it is the point of the form | When you impose a minimum length |
| Company name, tax ID | For priced B2B proposals | During first contact with an unknown person |
| Budget, company size | For large implementations after qualification | As a filter before the first conversation |
If nobody on the team uses a field to make a decision within the first day, remove it or make it optional.
If the form is used to book specific appointments rather than ask questions, consider another contact method. We explain the selection criteria and pitfalls in our guide to online booking systems.
A separate question is how much of this information you need to assess an inquiry's value. We draw the line between sensible qualification and interrogation in our article on qualifying leads on your website.
When booking a visit for an entire school class, use the guide: School museum visits: book the group and account for chaperones.
Microcopy: the words beside your fields
Those few words next to the fields achieve more than most visual changes. Their job is to answer three questions customers ask themselves without saying them aloud: why do you need this information, what happens after I submit, and when will I receive a response?
- A label instead of a placeholderText that disappears after a click leaves users without context when they review the form.
- A reason beside a sensitive field‘Phone number—we will call only about this inquiry’ works better than the word ‘phone’ alone.
- A stated response timeOne sentence saying when you will respond reduces duplicate messages.
- An error with guidanceUse ‘Enter an email address in the format name@example.com’ instead of ‘Invalid value.’
If there are fewer optional fields than required ones, label the optional fields instead. An asterisk beside every field but one makes the form look like an interrogation. Reversing that convention changes how the form feels without changing its contents.
Labels and error messages serve another purpose: they determine whether the form can be completed without a mouse and whether a screen reader can explain what went wrong. We describe a ten-minute test in our guide to accessible contact paths.
When a form rejects input without a clear explanation, use the guide: Website error messages: give customers a usable next step.
Consent that does not kill conversion
The most common mistake is combining everything into one checkbox: handling the inquiry, subscribing to a newsletter, and future marketing activity in a single three-line sentence. This is both legally weaker and worse for sales, because some people leave at the sight of it.
- Separate handling the inquiry from marketing consent—they are two different matters.
- Do not preselect any consent checkbox.
- Place a short sentence beside the form and link to the full policy.
- State who controls the data and how to contact them.
- Decide how long you retain tickets and who can access them.
- Check that you can find and delete one person's tickets on request.
The broader set of data decisions—categories, controller and processor roles, and retention—is shared by forms, chat, and phone contact. We have collected them in our article on live chat and the GDPR.
Stopping spam without punishing users
A form with no protection fills your inbox with junk, but overzealous protection costs real inquiries. Difficult image puzzles and repeated verification attempts primarily drive away people using screen readers, older browsers, and weak connections—not the bots you wanted to block.
Scroll the table sideways to see all columns.
| Method | Cost to the user | Notes |
|---|---|---|
| Hidden honeypot field | None | Stops the simplest bots and is always worth having |
| Time and rate limits | None in normal use | Effective against bulk submissions |
| Invisible verification | Low | A sensible default for most websites |
| Image challenge | High, especially on mobile | A last resort for a genuine, serious problem |
| Required login | Very high | Blocks first contact; do not use it here |
Start with the first two rows and assess the result for two weeks. You can always tighten protection later, but you can never recover inquiries lost to an overly aggressive filter because you will never know they existed. We show how to check that your protection is not rejecting genuine messages in our guide to contact form spam.
What should happen after submission
The moment after someone clicks ‘send’ determines whether they wait calmly or immediately send the same message through three other channels. A simple ‘thank you’ is better than nothing, but it does not answer the only question on their mind: what happens next?
- On-screen confirmation.Restate what the message concerned and when the customer can expect a response.
- Email confirmation.A copy of the ticket gives the customer proof that the message exists.
- Reference number.It makes subsequent contact easier and helps the team organize its work.
- A clearly assigned owner.A ticket assigned to nobody goes unanswered surprisingly often.
- A visible fallback.Offer phone or chat for urgent situations so nobody waits unnecessarily.
If form submissions currently scatter across several people's inboxes, read our guide to ticketing systems in customer service. We also explain how to measure response time without distorting the report in our article on first response time in live chat.
‘We respond within one business day’ works only when it is true. A broken promise does more harm than no promise at all.
An offline message creates a ticket with a reference number, status, and owner. Explore contact channels.
The form itself is only one element of the page where the customer lands. We explain how to arrange everything else—channels, business hours, and company details—in our guide to the contact page.
Contact form checklist
- Every required field is justified by a real step in the handling process.
- Labels remain visible after someone enters content.
- Error messages say what to correct, not merely that something is wrong.
- Entered data does not disappear after a failed submission attempt.
- The form works with a keyboard and a screen reader.
- Consent options are separate and not selected by default.
- After submission, the customer sees a confirmation with the expected response time.
- The ticket goes to a specific person or queue, not an ownerless shared inbox.
- Spam protection begins with methods invisible to the user.
- Once a quarter, someone submits a test inquiry and checks the entire path.
The final point looks trivial and catches the most failures. A changed email address, an expired integration, or a company-side spam filter can stop inquiries for weeks before anyone notices that there seem to have been fewer of them lately.
The form is only one of the places where inquiries get lost. We cover the rest—from channel visibility to missed messages—in our article on where you lose inquiries.
