Webvelopment
Ideas & practical guidance

Design insights

Can a customer understand your offer, send a useful enquiry and know what happens next? Use our design guidance to review that whole task, from the service page to the team receiving the request.

Let’s talk

Decisions worth making clearly

A customer needs to understand your offer before they can ask a useful question about it. Our design guides look at how page content, form behaviour and accessibility support that decision—and whether the enquiry gives your team enough context to respond.

Start with a task you care about, such as requesting a quotation. That gives a design discussion something concrete to test: can someone work out what information to prepare and what response to expect?

In this collection

Put the guidance to work

Choose one enquiry route to review. Bring the service page, the form and its confirmation message, along with the questions your team needs answered before it can help. If customers regularly misunderstand part of the offer, include that wording too. These details help us work out whether the issue sits in the explanation, the interaction or the follow-up.

Explore the related service or discuss your brief with the customer task you want to improve and who handles the resulting requests.

Read the enquiry guide as a customer-task review

Read the UX article with one service or product in mind. Follow the information before the form, the questions on it and the response after submission. A change to a button or field is easier to judge when you know what the person is trying to accomplish.

For example, a visitor comparing approaches may be ready to discuss options but unable to provide a detailed specification. If the page invites an exploratory conversation and the form requires a finished brief, the two parts ask for different levels of preparation. Review whether the page needs a clearer explanation or the form can gather that detail later.

Include whoever writes the service content and whoever answers enquiries. Together, they can check that the wording describes a service the business can provide and a next step it has arranged.

Review an enquiry as a complete task

Give a reviewer a goal, such as finding out whether a service suits a prepared brief, without telling them which button to press. Ask them to explain the offer in their own words, complete the form with a keyboard and recover from an error. Note where they pause or ask for help.

Then follow the test enquiry through to the receiving team. Does it contain enough information to answer? Does the confirmation describe what actually happens next? A success message alone cannot tell you whether the request reached the people who need it.

Read the enquiry UX guide · Explore UX design · Discuss a journey to review.

Design-reading FAQs

A few useful answers before you decide.

Do we need a redesign to improve enquiry quality?
Not always. Start by finding where the task breaks down: understanding the service, answering a field, recovering from an error or getting the request to the right team. A clearer explanation or a small form change may address the observed problem. A wider redesign needs its own reasons; enquiry quality alone does not tell you which change to make.
What should we watch during a user review?
Watch whether the person can find the relevant offer, explain what it includes and choose a next action. Note the words they misunderstand and the questions they ask. Let them try before offering help, and distinguish steps they completed alone from steps that needed a demonstration. That makes the review more useful when you decide what to change.
Can we improve conversion by removing form fields?
Sometimes, but ask the receiving team how each answer changes its next action. A question needed to route a request may earn its place; detail that can wait for a conversation may be optional. Check the quality of the enquiries afterwards as well as the submission count. Removing questions can make a form easier while leaving your team with more follow-up work.
How does accessibility relate to the enquiry task?
People need to identify each field, see where keyboard focus is and understand how to correct a mistake. Test those steps as part of the enquiry task, including the error and confirmation messages. Automated checks can help find issues, but someone still needs to try the task and read the information the customer encounters.
What if design feedback is mostly subjective?
Ask what each suggestion helps the customer do. “The next step is unclear” can be checked by asking a reviewer what response they expect; a colour preference needs a different discussion. Keep brand requirements and factual corrections visible, and agree who makes the final choice when preferences differ.
How should we judge the implemented result?
Try the agreed task at the relevant device sizes, trigger an error and confirm that a test enquiry reaches the receiving team. Compare the page’s promise with the response after submission. Then review whether the resulting conversations are useful. A faithful mockup implementation and a higher submission count each tell you only part of the story.
Explore

Read the guides

Design insights

UX Design Principles That Improve Enquiry Conversion

Make an enquiry journey easier to understand with clear offers, relevant proof, accessible forms, useful errors and accountable follow-up.

Keep exploring

Keep the right things connected.

Websites

UX Design

Review a customer or staff task through UX design, content structure, prototypes and usability questions, with an explicit research scope and design handover.

Let’s move things forward

Start a conversation

Tell us what you are working towards. We’ll help you find a practical next step.

Let’s talk