UX Design Principles That Improve Enquiry Conversion

Before we change an enquiry form, we look at the page that leads to it. Can a visitor explain who the service is for, which problem it addresses and what will happen after they get in touch? If those answers are missing, a more prominent contact button still leaves them guessing about whether a conversation is worthwhile.

Match the action to the conversation your business can offer. Someone comparing service options may need to discuss scope; someone with a prepared brief may be ready to request a quotation. If you need a consultation before you can price the work, explain that beside the action. “Request a quotation” should not leave the visitor expecting an instant price.

For each required field, ask the person handling enquiries: “What will you do differently because you have this answer?” Name, contact details and a project description may be enough to start a conversation. Budget, technology or target-market questions can help when they change the next response, but should be optional unless essential to that step.

For example, an early-stage buyer may be able to describe what customers struggle to do on their website without knowing which technology they need. A project-description prompt such as “What should people be able to do, and where are they getting stuck?” gives them a useful place to start. Requiring a technical specification at this point asks them to solve part of the problem before asking for help.

The W3C’s form-labelling guidance explains the importance of identifying controls and associating labels with them. Use clear visible labels, meaningful instructions and a logical order. Placeholder text should not carry information that disappears when someone starts typing.

Ask someone unfamiliar with the site to find the relevant service and make a test enquiry. Give them a goal, then watch: where do they stop, what do they reread and what do they expect after submitting? If they ask what a button means, let them describe their interpretation before explaining it. Guiding them through each step hides the very uncertainty you need to find.

Include keyboard use and mobile layouts in the review. Check focus visibility, labels, error identification and whether the sticky header obscures content. Automated accessibility tools can help identify some issues, but they do not replace manual task review.

Consider an illustrative service business whose page offers both an exploratory consultation and a quotation. Its form asks every visitor for a detailed specification. A lower completion count could reflect friction, unsuitable traffic or the fact that early-stage buyers cannot yet provide that detail. The number alone does not identify the problem.

Write two tasks for review: a buyer with a prepared brief wants a price discussion; a buyer comparing approaches wants to understand what information to gather. Ask participants to explain the next action they expect from the page. Observe where they hesitate without coaching them toward the form.

Keep the observation separate from your explanation. “The reviewer left the specification field blank and asked what to write” describes what happened. “The form is too long” is only one possible explanation. In this example, the buyer may understand the offer but lack the information the field demands.

Try a change that addresses that specific difficulty: let the exploratory route ask for the problem the buyer wants to solve, while the quotation route invites them to share their prepared brief. Then repeat both tasks. Check whether buyers can choose the appropriate route and whether the person responding still has enough context. If people cannot distinguish the two conversations at all, work on the page explanation and action labels first.

Review the difficult states too. An invalid address should lead to a useful correction, while a delivery problem should not erase the entire message or claim receipt that has not been confirmed. The sales owner checks whether the revised form still captures enough information for a relevant response.

The example gives you a specific question to test: does the form ask each buyer for information they can reasonably provide at that stage? It does not predict a conversion uplift. After changing it, review the task again and look at the suitability of the enquiries received. Fewer irrelevant submissions can be useful even when the total falls.