A contact form should gather enough information to start a useful conversation. It does not have to collect every detail needed for the whole project. Separating an initial enquiry from a detailed questionnaire makes both tasks easier to understand.
Ask only what the first conversation needs
Start with a name, a reply address, the service of interest, and a message. A company field is useful for business enquiries, but decide whether every visitor will have a company name before making it required.
For a web studio, a subject list can distinguish a new website, redesign, landing page, SEO, ongoing care, and a general inquiry. Include an option for people who are not sure. A forced choice should not prevent a relevant enquiry.
Use labels that stay visible
Give each field a visible label and make required fields clear. A placeholder can show an example, but it should not be the only explanation of what belongs in the field. Once someone starts typing, the label should still be available.
Place instructions near the field they explain. If a website address is optional, say so at that field. If a questionnaire asks for a budget range, explain that it helps scope the work and provide a way to say the budget is undecided.
Make errors actionable
An error message should say which value needs attention and what the visitor can do next. “Please enter an email address we can reply to” is more useful than “Invalid input.” Keep previously entered values where the form system supports it.
After a successful submission, confirm what happened. Do not promise a response time unless the business actually follows that commitment. Offer a public email address as an alternative path when it is appropriate.
Test the delivery, not only the appearance
Submit a clearly labelled test message from desktop and mobile, then check the destination inbox and any spam folder. A success message in the browser does not by itself prove that the email reached the intended recipient.
Also test missing fields, an unusually long company name, and a longer message. Check keyboard navigation and whether labels are associated with their fields. Review the form again after changing a mail setting or a form plugin.
Contact form design checklist
- Initial enquiry and detailed questionnaire are separate
- Visible labels remain after typing
- Optional fields are identified
- Errors explain how to recover
- A test message reached the intended inbox
Further reading
Review the form as part of the full journey using our mobile website checklist. If your existing enquiry path needs a wider update, explore our website redesign service.
