A consent configuration is the definition of one consent type, created once and then referenced everywhere: on guest profiles, in campaigns, and by your PMS or API. Two toggles on it decide what status a guest's consent starts in, and those two toggles are where most consent problems begin.
The fields
FormCode / Code. The internal identifier. This is what your PMS, the API, and CSV imports use to reference and map consent data, so it has to match on both sides.
Title. The readable name shown to Operators and to guests managing their preferences.
Body. The longer text explaining what the guest is opting into. Always fill this in. Leaving it empty produces a blank or confusing consent screen in the guest-facing flow.
Label. Short microcopy next to the checkbox or toggle, for example "I agree to receive marketing emails".
Description. An Operator-facing explanation of what the consent is for. On some screens guests can see it too.
The two toggles
Require Confirmation (double opt-in). When on, any consent added to a guest, however it arrives, is set to pending first. It becomes granted only when the guest clicks a confirmation link you send. When off, consent can be stored directly as granted, or as implicit if it came from auto-grant.
Auto-Grant with Reservation. When on, Bookboost adds the consent to a guest automatically when a reservation is created or synced. Rules can narrow this, for example to the primary guest only, or to bookings from a particular channel.
How the two combine
The status a guest's consent lands in depends on both toggles together.
Both off. Nothing is added automatically. Consent added manually, by PMS, or by API is stored as granted.
Auto-grant on, confirmation off. A reservation adds the consent as implicit. Enough for operational messages, not for marketing.
Auto-grant off, confirmation on. Consent arrives as pending and stays there until the guest confirms.
Both on. A reservation adds the consent as pending, and it becomes granted only after the guest clicks the confirmation link.
Creating a consent configuration
Go to the Consent settings area.
Select Create New Consent Configuration.
Fill in the Code, Title, Body, Label, and Description, as described above.
Set Require Confirmation, depending on whether you want double opt-in.
Set Auto-Grant with Reservation, if consent should be added automatically on booking.
Save.
Using a consent in a campaign
Open the campaign.
Find the Consent Requirement setting in the campaign's sending rules.
Choose no consent required, implicit consent required, or explicit consent required. Implicit accepts both implicit and granted; explicit accepts granted only.
Save and activate.
Common setups
Newsletter opt-in. Double opt-in, so guests explicitly confirm before any campaign reaches them.
PMS-driven marketing consent. Auto-grant on reservation sync, then confirm through a pre-arrival email carrying the confirmation link.
SMS or WhatsApp marketing. Gate the campaign so it only sends to guests with granted or implicit consent for that channel.
Guest self-service. Let guests manage their own preferences through the Guest App.
What this does not do
An empty Body field breaks the guest screen. Guests may see a blank or confusing consent page. Fill it in before activating the configuration.
Require Confirmation applies to every source. Consent arriving from a PMS or the API is set to pending too. The guest still has to click a confirmation link, whatever the external system recorded.
Unsubscribing is silent. No confirmation email is sent when a guest uses an unsubscribe link. If your guests expect one, build a separate follow-up campaign.
What to do next
For what each status means and how campaigns check them, see Consent management essentials. For collecting consent through forms and the API, see Collecting marketing consent.
Getting help
Open Help at the bottom of the left menu and choose Talk to Us, or email support@bookboost.io.