Every Apaleo reservation carries a debtor profile, and understanding how it is created helps explain how guest data appears in Bookboost. This article explains how Apaleo builds debtor profiles, how Bookboost reads them, and how Bookboost matches profiles so a guest ends up as one clean record.

When a reservation is created in Apaleo, three profiles exist:

A debtor profile is always created. This is Apaleo's default behaviour and Bookboost does not change it. By default, Apaleo copies the debtor's details from the primary guest. So if no specific debtor is set at booking, the debtor's details are based on the primary guest. If the debtor should reflect the booker instead of the guest, that is configured in Apaleo.

One consequence: a debtor may not have an email. If the primary guest has no email, the debtor profile copied from the guest will not have one either.

Bookboost does not change Apaleo's debtor logic. It reads the debtor email from the debtor profile on the reservation folio, and stores and reflects the data as received, since Apaleo is the source of truth.

Bookboost matches profiles to keep guest data clean and unified. If the booker, guest, and debtor share the same name but only one of them has a valid email, Bookboost merges them into a single profile.

For example, if all three are 'John Doe' and only one carries 'john@gmail.com', Bookboost merges them into one profile with that email. So even when Apaleo sets the debtor as a guest who has no email, Bookboost keeps the correct email on the merged record.

No setup is required. Debtor profiles are created by Apaleo automatically, and Bookboost reads them as part of the standard integration. If you need the debtor to reflect the booker rather than the guest, configure that in Apaleo.

Please contact us through the 'Talk to Us' option on the left menu in the platform, or through the Bookboost Support email at support@bookboost.io if you have questions or need additional support.