What will this answer change?

Imagine two customers giving different answers. Would you send the request to someone different, prepare a different reply or make a different decision?

If the answer changes nothing about how you handle the enquiry, consider leaving it out. “It might be useful someday” is a weak reason to make someone type it today.

An enquiry-type dropdown can earn its place when order questions and wholesale applications go to different people. A “How did you hear about us?” question on an urgent support form is harder to justify. You can ask that in a context where the customer has time and a reason to answer.

Can everyone answer it?

An order number is helpful when you are investigating a purchase. It is impossible to provide when someone is checking whether a product will fit before buying it.

Read every required field through the eyes of a new customer, an existing customer and someone with an unusual request. If one of them has to invent an answer to continue, the requirement is doing the wrong job.

You have a few choices: make the field optional, create a separate form for a specific request, or explain who should use the form. For a general contact form, an optional order reference is a straightforward starting point.

The same check applies to dropdowns. “Physical shop” and “Online shop” miss retailers who do both. Leave room for the business you have not thought of yet.

Do you need it before the first reply?

Think of the form as the first conversation. A wholesale application may need a business name, website, region and reply address so you can decide whether to talk further. The full delivery address and detailed opening order may be more useful after that decision.

For a custom project, a brief, quantity and requested date might let you assess the enquiry. Final production files can follow once the requirements are agreed. Asking for them upfront could force the customer to do work before either side knows whether the project is a fit.

Write down the decision you need to make next. Collect what that decision needs. Put the later questions in the later conversation.

Is the field suited to the answer?

A field can be necessary and still be difficult to use. The right shape helps the person give you an answer you can work with.

  • Order and business references: use short text. Identifiers can contain letters, symbols and leading zeros.
  • Quantities: a number field makes the expected answer clear.
  • A small, known set of options: a dropdown can keep answers consistent. Include a useful way to handle exceptions.
  • A problem in the customer’s own words: give them a long text field and enough space to explain.
  • Something easier to show: consider a file upload, with a label that says what the file should contain.

Use labels for the question and help text for the explanation. A placeholder that disappears as someone types should not be the only place you explain what you need.

What do the follow-up messages tell you?

After launch, review a small set of real conversations. For each one, note the extra questions your team had to ask before it could help.

Repeated requests for the same missing detail are a reason to consider a new field. Answers nobody uses are a reason to remove one. Blank optional fields can mean several things: the question may be irrelevant, unclear or difficult to answer. Read the surrounding message before deciding.

Keep a simple note of what you changed and why. Try one change at a time where practical, then look at whether the next conversations are easier to handle. A shorter form is not automatically better; a question that saves a necessary round of email can be worth the effort.

In Perfect Forms, you can edit the fields visually and check the layout on desktop and mobile. Start by auditing one existing form. You may find that the most useful improvement is a clearer label.