bookings
The Booking Form Is Where Most of Them Leave
Every required field costs you bookings. Here is how to tell which ones are earning their place, and which are there because somebody once asked.
A booking form is a negotiation in which the business asks for things and the customer decides, field by field, whether this is still worth doing.
Most forms are written from one side of that negotiation. Somebody lists what the office would like to know, marks nearly all of it required, and the form ships. The cost is invisible, because the people who abandon it do not send an email explaining why.
What each field actually costs
Every required field is a small probability of losing the booking. Fields are not equal, and the expensive ones are predictable.
Phone number is cheap for a service visit, because the customer expects to be called about it. It is expensive on a first enquiry where they were expecting to be emailed.
Address is cheap when the service happens at an address and expensive when it does not obviously need to, because the customer starts wondering what you want it for.
Free-text "tell us about your project" is expensive and usually low value. People stall on it, because they do not know how much to write, and what comes back is "need a quote" nine times in ten.
Anything about budget is the most expensive field on most forms. It converts a booking into a negotiation before any trust exists.
A dropdown with twenty options is expensive in a way people underestimate: it asks the customer to classify themselves correctly using your internal vocabulary, and the ones who are not sure which to pick leave.
The test for a required field
One question, asked honestly: if this were blank, would we refuse the booking?
If the answer is no, the field is not required. It may still be worth asking optionally, and the honest version of "we would like to know but will proceed without it" is an optional field, not a required one with a workaround the office knows about.
Run that test down an existing form and most of them shed a third of their required fields in ten minutes.
The second question is: could we ask this later, when they are already committed? Almost everything can. The time to ask for gate codes, pet details and parking instructions is in the confirmation, not in the thing standing between a stranger and a booking.
Ask in the order that builds commitment
The sequence matters as much as the content. People who have started are far more likely to finish, so the cheap questions go first and the expensive ones last.
A form that opens with name and email and ends with a date is harder to finish than one that opens with picking a date and ends with an email address, even though the fields are identical. The first asks for identity before offering value. The second lets the customer get something concrete, a slot, before paying anything for it.
The slot picker is part of the form
Most booking abandonment happens at the calendar, not at the fields.
Three common failures.
Showing every slot. A grid with forty availabilities is a decision problem. Three or four suggestions with a "see more times" link converts better and is faster to use.
Showing no honest availability. Any picker where the real answer is "we will call you to confirm" has made the customer do work for a result they do not get. Either the calendar is real or it is a contact form, and dressing the second as the first is the version that produces complaints.
Ambiguous times. A slot that says "2pm" without saying whose 2pm is fine when everybody is local and a silent defect the first time somebody books from another time zone. Show the zone.
Accessibility is conversion
A form that is hard for assistive technology is also, almost always, a form that is hard for everybody, and the fixes are the same fixes.
Every input needs a real label, associated with it, not a placeholder standing in for one. Placeholders vanish when typing starts, so a form labelled only by placeholders is a memory test and fails outright for a screen reader. Errors need to say what is wrong and how to fix it, next to the field, not as a summary at the top. The whole form needs to work from the keyboard.
The W3C's forms tutorial is the practical guide, and WCAG 2.2 is the standard underneath it. Both are more readable than their reputations.
Confirm immediately, and in writing
The last step is the one most often skipped. When the form is submitted, the customer should see a confirmation that restates what they booked, and get the same thing in writing within a minute.
Not for politeness. The immediate restatement is what catches the mistake while the person is still there to fix it, and the written copy is what prevents the "I thought it was Tuesday" conversation.
If the confirmation takes ten minutes to arrive, a meaningful share of people will have booked somewhere else by the time it lands, because silence after submitting a form reads as failure. That is a queue latency problem wearing the costume of a conversion problem, and it is worth measuring as such.