Registration fields

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.

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.

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.

Only team members who can see every location can add or change a chain-wide field. A member limited to some branches can still give their own branch its own version.

Party size and a note

Further down the same page a branch can ask two more things. Party size goes on the waitlist form, with the largest group that can join online; bigger groups are asked to speak to a member of staff. A note — “Anything we should know?” or your own wording — can go on the waitlist form, the booking form, or both.

The note is kept apart from your team’s own notes on the visit, so editing one never overwrites the other. Both are off until you switch them on.

The same page can require a service on the waitlist form. Visitors then can’t pick “Not sure / something else”; staff adding a walk-in still can. It only applies where the branch has waitlist services, and the booking form always asks for one.

Needs the permission locations.update_all_settings (update all locations settings). Owners and Admins have every permission by default.

Order and wording

Fields can be reordered, including the built-in ones. The order belongs to the branch you are looking at; a chain can push one branch’s order to every location. 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

Marketing consent is not a field

The marketing tick box is configured separately, under marketing, because what gets stored is different — the exact wording shown at the time, with a timestamp, rather than just an answer.