What counts as consent
Per channel, never bundled
Per channel, never bundled
A guest agrees to e-mail and to messages (text and WhatsApp) as two separate decisions. Agreeing to one is not agreeing to the other, and neither is ever bundled into accepting your terms or completing a booking.
Never pre-ticked
Never pre-ticked
Every consent box starts empty. A guest who does nothing has said nothing, and is not marketed to.
The words are yours, and they are on record
The words are yours, and they are on record
Your hotel sets the wording a guest sees, in each language, on the Consent screen. Every edit creates a new version and the old ones stay readable, so a guest who agreed last year is still matched to the exact words they were shown.
An incentive is allowed; a condition is not
An incentive is allowed; a condition is not
You may give a reason to say yes — a members’ rate, early access to offers. The guest who says no still gets every service they came for. Consent is never a condition of a booking, a request or a stay.
Consent belongs to an address
Consent belongs to an address
A decision is bound to the phone number or e-mail address the guest gave. If that address later changes on the profile, the earlier consent no longer covers the new one — the guest is asked again.
Where a guest is asked
Consent is asked where the guest already is, with the same words each time:- On the booking form, after the booking details, as separate boxes
- In the chat sign-in card, after the guest has proven their phone number
- On the self check-in screen, after the guest has proven their phone number
- In a WhatsApp conversation, once, at a natural moment — the guest answers with a plain yes or no in their own language
What is recorded
Every decision — yes, no, or a later withdrawal — is written to a ledger that is never edited, only added to. Each entry records:- the channel and the decision
- the exact words the guest was shown, and their language
- where it was given (which screen or conversation) and when
- the address it binds to, and whether the guest had proven they hold that address
- who recorded it — the guest themselves, or a named member of your team
How a guest stops
Every marketing message carries the guest’s way out, and each is honoured on its own:
A stop is durable. It outranks every audience built afterwards, survives a profile merge, and is not something a screen can work around.
What a broadcast checks before it sends
An audience can match more guests than you can reach. The Audiences screen shows both figures, and names why the difference exists: no address on file, no consent, or a stop on record. Before each message leaves, the platform checks the guest again — consent still standing, address still the one it was given for, no stop recorded since the audience was built. A guest who no longer qualifies is skipped, and the broadcast reports it. For a first send to a new audience, the platform sends a small share first and waits for your review before sending the rest.What your hotel can show
Every such download requires a right that only we grant to a named person at your hotel, a fresh one-time code to that person’s phone, and is recorded and announced to your managers. That is deliberate: a consented address book is exactly what should not leave a hotel unnoticed. The full mechanism is described in Guest data protection.
What the platform does not do
- It does not import a purchased list, and it does not market to a contact whose consent was not recorded on the platform.
- It does not treat a booking, a stay or a conversation as consent.
- It does not send a marketing message from a number or address the guest cannot reply to or stop.
- It does not let a member of your team say yes on a guest’s behalf.
How to ask for more
support@hotellinkage.com
Tell us your hotel name and which question your review is asking.