When a reservation has more than one guest, a check-in form collects details for all of them rather than only the person who received it. The primary guest fills in their own form, then chooses whether to continue with the others.
This switches itself on. Any pre-check-in or check-in form does it automatically whenever the reservation has more than one guest, including forms you built before, because the reservation is read at the time the form is opened rather than when it was created.
If you do not want that, build the form as a custom type instead. That is the only way to switch it off.
What the guest sees
The primary guest completes their own form and submits it. They are then asked whether they want to fill in the others.
Yes takes them to the next guest's form.
Not now submits their own form as normal and stops there. The remaining forms stay open for later.
Forms for guests already in your system are pre-filled the same way the primary guest's is.
How many forms are generated
Bookboost reads the reservation and generates a form for each guest on it. Where the guest count is higher than the number of profiles, the extras are generated blank.
Worked example. A reservation for four guests, with three profiles: one primary guest, one debtor, one secondary guest.
The form goes to the primary guest.
A second form is generated for the secondary guest, pre-filled.
Two guests are still unaccounted for, so two blank forms are generated.
What you get back
Each guest has their own submission record, so you can see who has been completed and who has not.
The person who originally received the form is recorded as the submitter on all of them, even where they filled in someone else's details. That is worth knowing if you are ever reconstructing who told you what.
What reaches your PMS
This is where the two integrations differ, and the difference is significant.
Mews. Every existing profile is updated, and new profiles are created for guests who were not in the system. A four-guest reservation can come back with four profiles.
Apaleo. Only the profile that received the form is updated. No new profiles are created, so details collected for accompanying guests stay in Bookboost and do not appear in Apaleo.
What this does not do
You cannot switch it off on a check-in form. The only way to avoid it is to use the custom form type instead.
It applies retroactively. Forms you built and sent before behave this way too, because the reservation is read when the form is opened.
On Apaleo, accompanying guests do not reach the PMS. Their details are collected and stored in Bookboost only.
Nothing chases the unfinished forms. If the primary guest chooses "Not now", the remaining forms simply sit there.
The primary guest is trusted with everyone's data. They can enter details on behalf of the others, which is convenient and worth being aware of.
What to do next
See Online check-in for what your PMS does with the data, and Create a form for choosing the form type in the first place.
Getting help
Open Help at the bottom of the left menu and choose Talk to Us, or email support@bookboost.io.