Enquiry and booking forms: small changes that get more completed forms

I treat an enquiry form as the start of a conversation, not an opportunity to collect everything a business might eventually need. A visitor is deciding whether to trust you with their details and their time. Each question should earn its place.

Small changes can remove obstacles to completion, but I would not promise a particular increase without measuring it. My first goal is simpler: make the form understandable, make it work on a phone and make the next step clear.

Choose between an enquiry and a booking

An enquiry form asks someone to start a discussion. A booking form asks them to choose a specific appointment or service. I would decide which action fits the way you actually work before changing fields or button colours.

If you need to assess suitability before offering a time, say that. Do not label the button as a confirmed booking when it only sends a request for review. The visitor should know whether a slot is reserved or whether someone will reply later.

For a genuine booking, explain the appointment type, duration, time zone and any relevant payment or cancellation conditions before the visitor commits. Only include conditions that accurately reflect your process, and make important details easy to find.

Give every required field a reason

I would list the current fields and write down what decision each answer supports. If you cannot explain why information is needed before the first reply, consider asking for it later.

A phone number might be necessary for a call request but unnecessary for an email enquiry. A full postal address might matter for a site visit but not for an initial discussion. The right form depends on the service rather than a universal ideal field count.

Mark optional fields clearly. Do not make a question look optional and then block submission because it is empty. If a required answer may feel intrusive, add a brief explanation beside the field.

Ask questions people can answer

Internal language often creeps into forms. I would replace unfamiliar service codes and technical categories with terms buyers use. If someone does not know which service they need, give them a truthful way to say so.

A broad message box can be useful, but a little direction helps. A prompt such as asking what they need help with and any relevant deadline gives the visitor a starting point without demanding a full written brief.

If you ask about budget, explain what the answer helps you assess. Avoid forcing a precise figure from someone who is contacting you to understand the likely scope. Where appropriate, an undecided option can keep the answer honest.

Make the mobile version comfortable

I would test the real form on a phone, not just shrink a desktop browser window. Tap every field, move between them and check whether the keyboard suits the information requested. An email field should behave like an email field.

Use visible labels that remain available after typing begins. Placeholder text alone is not a reliable label because it disappears when someone enters an answer. Instructions should be readable without zooming and associated with the relevant field.

Check the order of fields and the size of buttons. Also try navigating with a keyboard. A form should not depend on precise tapping, a mouse or a visual cue that some visitors cannot perceive.

Make errors easy to recover from

An error should explain what happened and how to fix it. I would prefer a message beside the relevant field over a vague warning at the top that says only that something went wrong.

Do not clear the visitor's answers after a failed submission. Repeating a carefully written message is an avoidable frustration. Ask the person responsible for the form to test invalid addresses, missing answers and a temporary sending failure.

Keep security checks understandable too. Protection against spam matters, but a challenge that blocks legitimate visitors needs attention. Provide a practical alternative contact route for someone who cannot complete the form, without implying they must send sensitive information by email.

Explain what happens after submission

I would put a short expectation near the submit button: who reviews the message and when a reply is normally possible. Only promise a response window your business can reliably meet.

The confirmation should distinguish a successful enquiry from a confirmed appointment. If someone still needs to approve the booking, say so. For time based bookings, show the agreed date, time and time zone clearly.

Test delivery as well as the screen message. A form that announces success but never reaches the right inbox is not working. Check notifications, spam folders and the process for handling an enquiry when the usual recipient is away.

What to do this week

• Decide whether the form creates an enquiry or a booking.
• Remove or defer fields you do not need for the next step.
• Rewrite unclear labels and mark optional answers.
• Submit the form on a phone and using a keyboard.
• Trigger an error and check that your answers remain.
• Confirm that the message reaches the person handling enquiries.

I would record the changes and review genuine completed enquiries afterward, without collecting unnecessary personal information. If the form is still difficult to use because the page loads badly, investigate website speed from an owner's perspective. The useful measure is whether people can complete the task and your team can respond, not whether the form looks shorter in a screenshot.