Quick answer
A good booking page asks for the information needed to schedule and prepare: name, email, meeting mode, optional context, and an address only when the meeting is in person.
Every extra field should have a clear reason. If the host will not use it before the meeting, it probably does not belong on the booking page.
The core required fields
Name and email are the baseline. The name makes the calendar event readable, and the email lets the guest receive the invite and any follow-up.
Meeting mode should also be explicit when the host supports more than one format. A call and an in-person meeting require different details.
Optional context can be useful
A short message field helps the host understand why the guest is booking. This is useful for discovery calls, partnership conversations, consulting sessions, and hiring chats.
Keep the prompt open and lightweight. Guests should not feel like they are completing an application before booking a simple call.
Ask for an address only when needed
Physical meetings need a location. If the guest chooses an in-person mode, the address should become required and should be sent into the calendar event as the location.
If the meeting is a call, asking for an address is pure friction.
Fields to avoid by default
Avoid fields that are better handled after the meeting is scheduled.
- Long qualification surveys.
- Multiple phone number fields.
- Internal segmentation questions.
- Required company details for a casual meeting.
- Anything the host will not read before the meeting.
Create a booking link that stays quiet
rdv.coffee keeps calendar scheduling minimal, readable, and safe by default.