Your contact form needs enough information to reply and understand the enquiry, without asking someone to complete your entire sales process. Start with a name, a usable contact method and a short description of the request. Add other fields only when the answer changes how you handle that first response.
Give every field a job
Open the current form and write down what happens to each answer. “Useful to know” is not a strong reason to make a field compulsory. A field earns its place when someone uses it to route the enquiry, assess suitability or prepare a helpful reply.
Imagine a business asking about a new website. Its existing website address may help the first conversation. Its annual turnover probably will not help enough to justify asking at that point. The right choice depends on your actual process, not on another company’s form.
The GOV.UK Design System’s question guidance recommends understanding why each question is needed. Although its patterns were written for public services, that discipline is useful for commercial enquiry forms too.
Which fields should be required?
Make a field required when you cannot handle the enquiry properly without it. If you respond by email, an email address is essential. A telephone number may be optional unless the service genuinely depends on an immediate call.
Do not force visitors to provide two contact methods just because your CRM has space for both. If you need a telephone number for a particular request, explain the reason beside the field. “We will call to check site access” gives more context than an unexplained asterisk.
Here is an illustrative starting point for a general business enquiry:
- Name: so the reply can address the person.
- Email address: so you can respond.
- What do you need help with?: enough context for a useful first reply.
- Company or website: optional, unless needed to assess the request.
- Telephone number: optional when email is a workable first step.
This is a starting point, not a universal specification. A repair request may need a postcode to check coverage. A training enquiry may need the course name. The test is whether the answer affects what happens next.
Ask questions people can answer
Replace internal labels with ordinary language. Visitors may not know which department owns their problem or which technical service they require. “What are you trying to change?” can work better than a menu of specialist terms.
Where you use a dropdown, include a sensible option for uncertainty. Otherwise people may choose at random simply to continue. That gives you tidy-looking data with very little meaning.
A free-text field can have a short prompt, such as “Tell us what you need and when you would like to start”. Avoid loading it with six separate questions. If those answers are essential, ask them clearly in their own place.
When should you ask about spending or timing?
Ask when the answer meaningfully changes the first response. A broad spending range can help on a complex project, but it can also be difficult for someone who has never bought the service before.
Offer “I need guidance” where that is a legitimate answer. State published starting prices on the relevant service page so the form does not have to reveal basic commercial information for the first time.
For timing, distinguish a preferred date from a fixed deadline. “When would you like to start?” and “Is there an event this must be ready for?” answer different questions. Do not turn a preference into an implied promise in the confirmation message.
Make completing the form feel straightforward
Keep labels visible after someone starts typing. Mark optional fields clearly and show an example where the format is genuinely important. Avoid demanding a particular phone-number format unless the system needs it, and explain it if it does.
Test a mistyped email address, a blank required field and a longer message. The form should explain how to fix the problem and preserve the answers already entered. A failed submission that wipes the message is a particularly effective way to end a conversation before it begins.
Our mobile enquiry testing guide covers practical checks, including what happens after the submit button. The form is only one part of that test.
Review the quality of the response
After the form has been in use, ask the people replying which missing answers cause repeated follow-up questions. Also ask which collected fields they never read. Use both answers to improve the form.
Keep a short change log when you remove or add fields. Compare enquiry quality as well as volume, and avoid declaring a winner from a handful of submissions. Clearer service page content may solve confusion before anyone reaches the form.
For a site where the page, form and response process need to work together, see our website design service.