A contact form often asks for information that would be convenient to have internally from the outset. For the visitor, however, every field feels like extra work, especially when what happens after sending is still unclear. Choose fields based on the first follow-up action. What information does an employee need to understand the enquiry properly and give an appropriate answer?
Start with the employee who receives the enquiry
Work through a number of recent enquiries together. What information was needed to assign the enquiry? What could be added during the first conversation? Sometimes a short description matters more than an extensive list of options. A visitor may not know internal service names and could therefore select the wrong subject.
Divide the desired information into what is necessary for contact, what is necessary for assessment and what is useful later. Only make the first two groups mandatory when there is a clear reason. Briefly explain why you ask for less obvious fields. A project location may be needed to assess whether services are available in that area, for example.
Make the form fit the customer’s uncertainty
In a fictional example, a design agency asks for an exact budget, a final schedule and a complete technical specification at first contact. The very visitors who need help defining their enquiry cannot yet provide those answers. An option such as “still to be determined” or a free-text explanation makes the form better suited to the actual stage of the conversation.
That does not mean every enquiry is useful without context. If a service is intended only for a clearly defined type of project, the form may help explain that boundary. State the conditions on the page before the form too. Visitors should not discover only after filling it in that their enquiry falls outside the offering.
Design the wording around sending
Give the message field a focused question, such as what situation someone wants to change and what is currently causing difficulty. Clearly present examples as suggestions. A long example inside the field may disappear as soon as someone starts typing; a short explanation beside it is easier to refer to.
Also explain what happens after sending. State a response time only when the team actually follows it. A confirmation needs to show that the enquiry has been received and what the logical next step is. Connect the form with organising customer enquiries, even when it concerns sales rather than support.
Test the form as a complete task
Ask a test participant to make a realistic enquiry on a phone. Check that labels are understandable, required fields are identifiable and error messages help. Then review the contents with the employee receiving them. Can they determine what is needed, or does the form instead produce unclear categories and empty answers?
Assess different situations: a visitor exploring options, someone with a specific project and an existing customer with a question. They may not all need the same form. Record the result in a field list showing the purpose and recipient of each piece of information. When designing the website that provides a better basis than copying a standard form. The right number of fields is the number that enables a meaningful next step.