A consent option is a thing a guest can agree to: a newsletter, marketing by SMS, a loyalty programme. You define them once under Settings > Consent, and every guest profile then shows a toggle for each one.
They are not freeform labels. Each is a configuration with required fields and two toggles that change how consent behaves in campaigns, so it is worth setting up deliberately rather than adding as you go.
Creating one
Go to Settings in the left menu.
Open Consent.
You will see the consent options you already have. Select Add New.
Fill in the details. Give it a name a guest would understand, since some of these fields are shown to them rather than only to your team.
Select Save.
Two settings on the configuration change behaviour rather than wording:
Auto-grant decides whether the consent is given automatically rather than asked for.
Require confirmation is double opt-in. With it on, a guest sits at pending until they confirm, and pending guests are excluded from campaigns. With it off, consent goes straight through.
See Consent management essentials for what those two do in combination.
Applying one to a guest
Open the guest's Profile.
Find the Consent field. Every consent option you have created is listed.
Toggle the relevant one on to grant it.
For more than a handful of guests, use an import instead. A consent column in your CSV applies the status in bulk, rather than opening profiles one at a time.
Naming them well
Guests see some of this wording, and your team reads the rest of it every time they check a profile.
Name by what the guest agreed to, not by the mechanism. "Monthly newsletter" is clearer than "Marketing opt-in 2".
Separate the channels you genuinely treat separately. If you would never send a WhatsApp promotion, do not create a consent for it.
Do not create one per campaign. Consents are long-lived. Audiences are where you narrow to a specific send.
What this does not do
Deleting a consent option affects existing guests. Filters and segments built on it stop working, and the record of what those guests agreed to goes with it. Review where it is used first.
Creating an option does not collect consent. It gives you somewhere to record it. The asking is done through a form or your PMS.
A toggle is not evidence. Switching one on by hand records a status; it does not create a defensible audit trail of the guest agreeing.
Auto-grant is not consent everywhere. Whether assumed consent is lawful for a given message depends on your jurisdiction, not on the toggle.
What to do next
See Guest consent statuses for what each status on a profile means and which campaigns it lets through.
Getting help
Open Help at the bottom of the left menu and choose Talk to Us, or email support@bookboost.io.