Which booking form fields do you actually need? In theory, a name, a contact channel and a time slot. In practice, a car wash needs to know whether a hatchback or an SUV is coming, a hairdresser how long the client's hair is, and a rental shop how many people will turn up. This guide goes field by field: what you need before the appointment, what can wait and how to ask without making people stall.
We are not diagnosing drop-off across the whole booking journey or deciding about customer accounts; both have their own guides, linked below. Start from the fields you have today and one question: who on your team uses each answer, and when?
Three questions every field has to pass
List every field, including those in later steps and consent boxes. For each, note who uses the information, before which decision, and what happens if it is missing. If nobody can name a person or a decision, consider removing the field. If the decision is made on site, the field can wait.
Scroll the table sideways to see all columns.
| Field | Require it when | Drop it when |
|---|---|---|
| First name | Reception greets the customer at the door | You add a surname with no specific reason |
| You send confirmations and changes by email | You confirm appointments by phone only | |
| Phone | You call before the visit or about delays | It is required just in case |
| Notes | Never required, optional at most | They become the only place for key details |
The third answer separates essential from convenient. Without a phone number, a service where you always call ahead can go wrong; without a date of birth, a haircut changes nothing. Where customers give up after choosing a slot is covered in the guide to booking form drop-off; here we deal only with what goes into the fields.
Details for preparing the service: car, hair, group size
The most valuable fields change preparation: time, workstation, staff or equipment. The fictional Shine car wash must know whether a car is small or an SUV, because that sets the job length. The fictional salon Strand plans colour differently for short and long hair. A fictional kayak rental needs the group size to prepare boats and life jackets.
Scroll the table sideways to see all columns.
| Fictional business | What the answer changes | Better way to ask |
|---|---|---|
| Shine car wash | Time spent in the bay | Separate offers for small cars, mid-size cars and SUVs |
| Salon Strand | Appointment length and amount of dye | A hair length choice instead of a description |
| Kayak rental | Number of kayaks and life jackets | Number of people or units next to the time slot |
Collect information that changes time or resources as a choice, not as text for reception to read. A choice updates the schedule at once, while a "describe your car" box needs reading, interpreting and often a follow-up. How vehicle size translates into bay time is shown in the guide to car detailing bookings.
What can wait until the appointment or after it
Some details are needed, just not at booking. Invoice details, a detailed questionnaire or product preferences can be collected later: after confirmation, by phone or on site. A customer who already has a slot answers extra questions more willingly than someone checking availability.
- Invoice details are collected after booking unless they are needed to accept it.
- "How did you hear about us?" is optional or saved for the conversation on site.
- Date of birth, home address and ID numbers never appear without a specific purpose.
- A detailed pre-service interview happens in conversation, not in an open text box.
- Marketing consent is separate and is never a condition of booking.
If you are dropping a mandatory customer account, do not replace it with a longer form. Why that only moves the obstacle somewhere else is explained in the guide to booking without a customer account.
Data minimisation and health information
Data minimisation does not cap the number of fields. It requires each one to be adequate for the purpose, which here means handling this booking. Your three answers from the first section therefore double as documentation of why you collect each item.
Article 5(1)(c) of the GDPR (applicable since 25 May 2018) requires personal data to be adequate, relevant and limited to what is necessary; Article 9 generally prohibits processing health data outside the listed exceptions. Regulation 2016/679 on EUR-Lex. It does not list booking form fields. In the UK, the UK GDPR keeps the same principles. This article is not legal advice.
Be especially careful with health. Questions about allergies, contraindications or pregnancy in an open field are rarely needed for the booking itself and create special category data. If the service truly requires them, agree the legal basis and method with whoever handles data protection, collect only contact details in the form, and run the questionnaire separately before the appointment. Other contact channels are covered in live chat and the GDPR.
How to word an optional question
An optional field still has a cost: people wonder whether to fill it in and what to write. Add "optional" to its label instead of putting asterisks on every other field. Say what the answer is for, give an example, and state what not to enter if the box might invite health details or document numbers.
Notes (optional): tell us if your car has a roof box, tinted windows or is very dirty after a trip. Please do not enter document numbers or other people's details here. This example belongs to the fictional Shine car wash.
The GOV.UK Design System advises knowing why you ask every question, asking only for information you really need, and adding "(optional)" to optional field labels rather than marking required fields with asterisks. GOV.UK Design System, question pages. This is guidance for public services, not a study of booking form performance.
More label and error message examples are in the guide to contact forms on your website.
Test completion on a phone and in recordings
Test your field decisions on a phone, ideally someone else's, with nothing saved in the browser.
- Pick the most complex offer.Use the service with the most choices and fields.
- Fill in fields with your thumb.Check that the phone field opens a numeric keypad and the email field gets browser suggestions.
- Make a mistake on purpose.Enter an incomplete number: does the message say what to fix, and does your input stay?
- Note where you hesitated.Ask whether that field's answer is needed before the appointment.
WCAG 2.2 criterion 1.3.5 (level AA) requires that the purpose of fields collecting user information can be programmatically determined, so browsers can autofill them. W3C WAI, Understanding SC 1.3.5. It does not say which fields a booking needs.
Session recordings show what happens around the form: whether customers reach it, return to the offer description, and where they leave. In Meetlead, the embedded booking form is deliberately excluded from recordings, so typed details and movement between fields stay invisible. Check the inside of the form with the test above and booking statuses in the panel. A recording pattern tells you where to look, not what caused it.
Turning your field list into an offer in Meetlead
In Meetlead Bookings, you set customer details per offer: name, email, phone, company, notes and privacy policy acknowledgement can each be required, optional or hidden. The widget guides customers through service, quantity, time slot, contact details and summary. Car size or hair length changes job length, so use separate offers, since duration is set per offer. Variants with their own capacity and price suit cases where the resource changes; group size goes in the quantity step.
Meetlead does not add custom questions to the form. Put a hint like the template above in the offer description so customers know what to add in the notes, and collect anything else after booking. Bookings is an App on the Growth and Scale plans with configurable data retention. Offer prices are for information only: the form takes no payments.
Questions about booking form data
Should the phone number be required? Only if you really call before the appointment or about changes. If confirmations go by email, make it optional and say when you would use it. Requiring both channels is rarely justified for a first appointment.
What if customers type unneeded details into the notes? Say in the offer description what belongs in the notes and what does not. Check whether an offer or variant is missing, since customers often use the notes to describe a choice the form did not give them. Keep such details only as long as the appointment requires.
