Skip to main content
Custom forms let you ask your customers for individually tailored information directly during booking. You create one or more forms with different field types and flexibly assign them to individual booking options, so you can collect customer data efficiently and precisely.

How do custom forms work?

You create a form with any number of fields and define at which level the data is collected:
  • Booking: customers fill in the form for each individual booking.
  • Order: customers fill in the form once per overall order (e.g. with several bookings in one cart).
  • Customer: customers fill in the form once for their customer profile (e.g. for rarely changing master data).
Each form is assigned to a booking option. Several forms can be active on one booking option at the same time. Forms you do not currently need can be moved to the inactive area by drag and drop, and you can reactivate them or assign them to another booking option at any time. anny attaches an active form to every new booking of this booking option, so you do not have to add it to each booking yourself. Existing bookings do not get it afterwards; add it to them one by one (see below). If only your team should fill in the form in the admin area, turn off Request in checkout. Once a form is added to a booking option, you define the collection time per form:
  • At booking completion: customers fill in the form directly at checkout (default behavior).
  • Later (at check-in): customers can already fill in the form optionally at checkout. It only becomes required at check-in if details are still missing. This is especially useful when details only become relevant or known shortly before the appointment.
  • Later (at check-out): your team fills in the form when it checks the booking out in the admin area, for example “Key card returned?”. It does not appear at checkout. See Presence in booking details.
You find more details on setting up and running the delayed form request at check-in in the article Check-in: Getting Started. After booking, customers can view and edit their submitted form data in the booking overview, provided you enable later editing in the respective service. This function is currently only available in the web version.
Use the “Customer” level for details that rarely change (e.g. company data, certificates). This way customers only need to enter this information once.

Attach a form to a record

In Admin 3.0 you attach an existing form to a booking, a customer, a company, an order, or a subscription. Add opens Custom forms. Under Available you pick a form that belongs to that kind of record. Added shows what is already attached. Your changes only apply when you click Save; Close drops them. Removing a form keeps the answers already stored on the record. You create new forms where they are offered: on the service, product, plan, or inquiry form. The overview is under Account → Settings → Data fields, section All forms. The same tab holds Calculated fields: the customer profile shows the value, and you edit the definition there.

When do I use this?

  • You ask for specific details per booking (e.g. number of participants, special requests, arrival time): create a form on the booking level with the fitting field types.
  • You need one-time details per order that apply to all included bookings (e.g. project name, insurance confirmation): use the order level so customers only enter the information once.
  • You collect rarely changing master data (e.g. trade license, certificate): use the customer level so the detail is stored permanently in the profile.
  • You want documents in advance (e.g. proof, photos, filled-in PDFs): use the file upload field type.
  • A question only matters to some of your customers (e.g. allergies only when catering is booked): use Show only if … to show it only when an earlier answer matches (see Settings & options). You can’t add new conditions at the moment.
  • Not suitable for: plain contact data (name, email, phone), because anny already collects these automatically in the customer profile.

Relationship with other features

  • Legal documents: legal documents are also configured in the Form tab. They serve legal protection (e.g. terms confirmation), while custom forms collect content information.
  • Recurring bookings: for booking series, form data is stored exclusively on the master appointment and is only visible and editable there.
  • Check-In terminal: on badge templates you can insert form fields from the booking, the customer and the order as variables.
  • Customer display: you send a form from the admin to the check-in terminal at the counter. Customers fill it in and sign there, and you see their answers live.

Settings & options

For the file upload field type, you additionally define the maximum file size (default: 5 MB) as well as the minimum and maximum number of allowed files. With a condition, a question only appears once the answer to an earlier question in the same form matches. Customers only see the questions that are relevant to them.
For now, you can’t add new conditions in the form editor. Only a question that already has a condition shows the condition link, e.g. “Only if “Catering requested?” is checked”. These conditions keep working, and you can edit them there or delete them with Remove condition. A removed condition can’t be added again at the moment.
1

Open the form

Open the form, e.g. on the booking option in the Form tab or under Account → Settings → Data fields → All forms.
2

Open the condition on the question

At the bottom of the question you want to hide, click Show only if … (next to Advanced Settings and Required). The Show this question only if … dialog opens.
3

Choose the question and the condition

Under Question, choose the question whose answer decides whether this one is shown. Then choose the Condition and, if needed, the matching Answers or the Value.
4

Apply and save

Click Apply and save the form. The question now shows e.g. “Only if “Catering requested?” is checked”.
Once the condition is saved, customers only see the question when their answer to the chosen question matches.
“Show this question only if …” dialog with the question “Catering requested?” and the condition “is checked”, arrow pointing at the Condition field
Question list in the form editor: below the question “Diet”, the link “Only if “Catering requested?” is checked” shows the condition, arrow pointing at it
You can only choose saved questions that sit above the current question in the same form. If there is no saved question above it yet, the dialog shows a hint. Create the question it should depend on first and save the form. Each question has exactly one condition. Remove condition makes the question always visible again. Which conditions are there? The conditions you can choose depend on the field type of the question the display depends on: How answers are compared:
  • is one of: the question appears as soon as one of the chosen answers is selected. For a multiple selection, it is enough if one of the selected options is among them.
  • is: the answer must match the value. Upper and lower case and spaces at the start and end don’t matter (“Yes ” matches “yes”). The text is compared, not the number: “1.0” does not match “1”.
  • is greater than, is less than: the number is compared, so “1.0” is not greater than “1”. Without an answer the question stays hidden, e.g. “Name of guest 2” with “Number of guests” is greater than 1.
  • is answered: the question appears as soon as any answer is entered.
  • isn’t checked: the question appears as long as the checkbox isn’t checked, including before the first input.
What happens in the form?
  • Live: the question appears or disappears immediately while customers fill in the form.
  • Never required while hidden: a hidden question doesn’t block completion, even if it is marked as Required field. As soon as it is visible, it is required again.
  • Answers are discarded: if someone answers a question and then changes the answer that hides it, anny clears the answer of the hidden question. When customers complete the checkout or an inquiry, anny doesn’t save answers to hidden questions.
  • Chains: a question can depend on a question that has a condition itself. If the earlier question is hidden, it counts as unanswered.
Conditions take effect at checkout, in inquiry forms, when personalising a booking, and when editing the details later in the booking overview.
A field from Calculated fields can’t trigger a condition. Calculated fields are never asked; they are calculated from other data.

Available field types

Supported file types for upload: JPEG, PNG, GIF, WebP, PDF, Word (.doc/.docx), Excel (.xls/.xlsx), OpenDocument (.odt/.ods/.odp), text (.txt), CSV, ZIP, MP3, MP4.

Practical examples

A workshop provider wants to ask each booking for the participants’ skill level and dietary preferences, in order to sort groups and plan catering.
A rental provider wants to ask once per order for the project name and a damage insurance confirmation, regardless of how many devices are included in an order.
A seminar venue offers optional catering with every room. The booking-level form first contains the checkbox “Catering requested?”, below it the selection “Diet” (No restrictions, Vegetarian, Vegan, Other) and the required field “Allergies and intolerances” (Text long).
  • “Diet” gets the condition: Question “Catering requested?”, Condition is checked.
  • “Allergies and intolerances” gets the condition: Question “Diet”, Condition is one of, Answers “Other”.
Without ticking catering, the customer only sees the checkbox at checkout and can book right away. If she ticks it, “Diet” appears. If she picks “Other”, the required allergies field appears. If she unticks catering again, both questions disappear and their answers are not saved.

FAQ

Yes. For selection and multiple selection, each option in the form editor is an input field. Fix the text right there. If a question uses Show only if … with this option, the condition takes over the new text.
Yes. You find existing forms centrally in the Custom Forms area. From there you can assign them to different booking options by drag and drop.
For booking series, form data is stored exclusively on the master appointment. In the individual series appointments, the fields are not editable, to ensure the consistency of the series.
Yes, if you enable later editing in the respective service. Customers then see their details in the booking overview and can edit them there. This function is currently only available in the web version.
There is no fixed upper limit. You add any number of fields within a form via + Add field.
JPEG, PNG, GIF, WebP, PDF, Word, Excel, OpenDocument, text, CSV, ZIP, MP3 and MP4. The default file size is 5 MB.
On several answers, yes: for selection and multiple selection you can choose any number of answers under is one of, and one of them is enough. On several questions, no: each question has exactly one condition. You can chain questions, though, so that a question depends on another conditional question.
Yes. It is only required while it is visible. While it is hidden, customers can still complete the form.

Troubleshooting

The form may be in the inactive area. Open the booking option, switch to the Form tab and check whether the form is on the left (active) or right (inactive). Drag and drop it to the left to activate it.
Check whether later editing is enabled in the respective service. Also make sure the person uses the web version, since the function is not yet available in the mobile app.
This is expected behavior. Form data is only collected and stored on the master appointment for series. The individual series appointments do not show the fields separately.
You can only choose saved questions that sit above the current question in the same form. Create the question it should depend on above it and save the form. Then open the condition again.
Check the question in the form. If it says “Condition inactive: the question it depends on is missing or comes later”, the triggering question was deleted or moved below the conditional question. Move it back up or choose another question.
With is, anny compares the text of the answer with the Value you entered. Different spellings, e.g. “1.0” instead of “1”, don’t match. Also check whether the triggering question is hidden itself: then it counts as unanswered.