A visitor who reaches your quote form has already done the hard part. They found the site, understood the offer and decided to ask. If the form then feels long, confusing or broken on a phone, that intent is lost. If it is too thin, the enquiry arrives without the details the team needs, and the first call is spent collecting them.
This guide covers the choices that make the difference: what to ask, in what order, how the form behaves on a phone, and what happens after someone presses send. It applies to coach hire, building work, professional services and most businesses that quote before they sell.
Ask only what the reply needs
Start from the reply, not the form. What does your team need to know to send a useful first response? For a coach operator, it is the journey, the date and the number of passengers. For a building company, it is the type of work and the property postcode. Everything else can usually wait for the conversation.
Each extra field makes the form feel longer, and some questions stop people outright. "What is your budget?" can halt someone who has no idea yet. "Company registration number" adds nothing at the enquiry stage. If a question is useful but not essential, make it optional, and offer "not sure yet" where people genuinely may not know.
Order the questions so the form builds momentum
Begin with easy, factual questions about the job. People are more willing to share contact details once they have described what they need, so name, email and phone usually belong near the end. A longer form can be split into steps: the job, then the options, then the contact details.
Ecobuild's project request is a good example. It starts with only the type of work and the postcode, either on the homepage or a dedicated quote page, and then continues as a three-step form with no obligation. A separate contact form handles general questions, so a supplier or a casual question does not have to pretend to be a quote request. You can see the structure in the Ecobuild case study.
- Show progress, such as "Step 2 of 3", so the end is visible.
- Keep each step to one topic.
- Let people go back without losing what they typed.
- Make the first step the shortest.
Design for the phone first
Many enquiries start on a phone, often between other tasks. Use a single column, labels that stay visible above each field, and text large enough to read without zooming. Match the keyboard to the field: an email keyboard for email, a number pad for phone numbers. Make buttons large enough to tap and keep the submit button easy to find.
Accessibility and mobile design overlap. Every field needs a real label, not just placeholder text that disappears as someone types. The whole form should work with a keyboard, and errors should not rely on colour alone. These details help everyone, including people filling the form in a hurry. Why the defaults matter is explained in web accessibility in 2026.
Handle errors kindly
Tell people about a problem as soon as they leave the field, not after they press send. Say what is wrong and how to fix it: "Please enter a UK postcode, for example B35 7BT" is far more useful than "Invalid input". Accept reasonable variations, such as phone numbers with or without spaces and postcodes in lower case. Never block pasting into a field.
Spam protection should not punish real customers. A hidden honeypot field and sensible rate limits stop much of the automated spam without asking every visitor to solve a puzzle. Use a visible challenge only when it is genuinely needed.
What happens after send is part of the form
The confirmation page should repeat what was requested, say when and how the business will respond, and give a phone number for anything urgent. The same information should arrive by email within seconds. Without it, many people assume the form failed and either send it again or try a competitor.
Then the enquiry has to reach the people who act on it. On the Ecobuild project, enquiries join a coordinator workspace where the team works through calls to make now, follow-ups and overdue quotations. A job is marked as qualified only after the coordinator has recorded the answers that matter. A form connected to a working queue beats a perfect form that empties into an unread inbox.
Measure, then change one thing at a time
Look at how many people start the form and how many finish it, on phones and on desktops. If phones lag well behind, there is usually a layout or keyboard problem. Read recent enquiries too: completion rate means little if the team still cannot quote from what arrives. Change one thing, such as removing a field or splitting the form into steps, and compare the results over a few weeks before changing the next.
For transport businesses, the specific choices on a coach hire quote form are covered in how to build a coach hire website that turns visitors into quotes.
Getting help with your form
Web Works Rise is a UK-led team in Birmingham, with a development hub in Tunisia that adds delivery capacity. We design and build quote journeys as part of web development and UI and UX design work, for sectors from coach hire to construction, and connect them to the systems that handle what comes next. If your form gets visits but not useful enquiries, talk to the team and we will look at it with you.