Ask your own questions at booking with custom fields

The standard booking form asks for what every property needs: who is coming, when, and how to reach them. Custom fields are for what your property needs to know on top — the questions you'd otherwise chase by email after every booking.

Some real examples:

• "What time do you expect to arrive?"
• "Vehicle registration" (for parking or an ANPR barrier)
• "Are you bringing a dog? Which breed?"
• "I have read and agree to the site rules" — with the box guests must tick

Custom fields are available on the Growth plan and above (see pricing), under Custom Fields in your dashboard.

Field types

Type	Use it for
Text	Short answers — a vehicle registration, a name
Text area	Longer answers — special requests, access needs
Number	Anything you'll want as a number — arrival hour, number of dogs
Dropdown	A fixed set of choices you define — "EHU required: yes / no"
Checkbox	Agreements and confirmations — site rules, no-noise policy

Every field can have a placeholder (example text shown in the empty box) and help text (a short explanation underneath), and can be marked required. A required checkbox means the booking cannot be made until the guest ticks it — which is exactly what you want for a rules agreement.

Where guests see them

Custom fields appear on your website's booking form and in the booking widget on your own site, after the standard details. Guests must answer required fields before the booking goes through.

When you or your team create a booking from the dashboard, the same fields are there too — but required doesn't apply to staff, so a phone booking is never stuck because the caller didn't have their registration plate to hand.

Only asking when it's relevant

By default a field appears for every booking. If a question only makes sense for some of your pitch types — an electric-hookup question is noise for someone booking a cabin — edit the field and limit it to the pitch types it applies to. Everyone else never sees it.

Where the answers go

Answers are saved on the booking and shown on its detail page in your dashboard, labelled with the question as it was asked at the time.

That last part matters more than it sounds: the answer is stored with the question text, so if you reword, retire or delete a field later, the answers already collected keep their original meaning. You can tidy your form without worrying about old bookings.

Reordering, switching off, and deleting

• Drag fields on the Custom Fields page to change the order guests see them in.
• Switch a field off (rather than deleting it) to stop asking a question you might want back — a seasonal question like "Will you arrive after the gate closes?" can come back next winter with one click.
• Delete a field when you're sure — answers already on bookings are unaffected.

Keep the form short. Every extra required question loses a small number of guests at the final step. Ask what you genuinely act on, make the rest optional — or leave it for the arrival chat.