Configuring a location

Registration fields

What you ask somebody when they join the waitlist or make a booking. Every extra field costs you people who give up part-way through, so this page is mostly about deciding what you genuinely need.

Where to set them

Location settingsCustomer details. Fields can be defined once for the whole business and narrowed or overridden for a particular branch.

Needs the permission input_fields.create (create input fields) and input_fields.update (update input fields). Owners and Admins have every permission by default.

The three built-in fields

Name — required, always shown.
Mobile number — required, always shown.
Email address — off by default, and yours to switch on.

Name and mobile number can be relabelled and reordered but not hidden or made optional. Without them there is nobody to call and no way to call them, so the refusal is enforced on the server rather than merely hidden in the interface — the API cannot get round it either.

Email is worth switching on

It is off to begin with because asking for one is your decision, not ours. Once it is on, the join and booking forms collect it and the email channel can reach everybody who joined publicly — and email sends do not count against your messaging allowance, which makes confirmations and follow-ups effectively free.

Adding your own fields

Anything you need to know before serving somebody: a car registration, a membership number, an appointment reference, a dietary requirement. Each field has a label, a type, and whether it is required.

The available types:

Text
Long text
Email address
Phone number
Number
Date
Choose from a list
Tick box

Answers are stored against the visit and shown to your team on the visit's own page.

Asking different things of different flows

A field can appear on the waitlist form, the booking form, or both. This matters more than it sounds: somebody standing in your shop wanting to be seen has very little patience, while somebody booking three weeks ahead will happily fill in four boxes.

A reasonable default

Waitlist — name and mobile number. Nothing else unless you genuinely cannot serve them without it.
Bookings — add email, and whatever detail makes the appointment go smoothly.

Chain-wide fields and branch overrides

Define a field once for the organisation and every branch asks it. A branch that needs different wording, or needs it on one flow only, can override the field — and the override replaces the chain-wide version rather than sitting alongside it, so the customer is never asked the same thing twice.

Order and wording

Fields can be reordered, including the built-in ones. Labels are yours: a veterinary practice might relabel “Name” as “Your name” and add “Pet's name”; a garage might relabel it and add a registration.

Ask in the order somebody would naturally answer, and put anything optional last.

Ask for less

Every field costs you joiners

The form is standing between a customer and a place in your queue, often on a phone, often one-handed, often in a hurry. Before adding a field, ask whether you could find out the answer when they get to the counter. Usually you could.