Direct answer: before an AI sales assistant, CRM workflow or WhatsApp/email bot **auto-sends** a “similar stay / similar tour” chase after an incomplete UK travel enquiry, the product must already prove the **PECR products and services soft-opt-in gates** — or hold valid marketing consent for that channel. Soft opt-in is not “the model decided the guest seemed interested.” It is a deterministic CRM/booking-stack check: contact details obtained **directly** during a **sale or negotiation to sell**; message limited to **your similar products/services**; a **simple opt-out offered at collection**; and a **simple opt-out in every subsequent message**. If any gate fails, the assistant must not send unsolicited electronic mail marketing to an individual subscriber.
That is the operator question Kaize is answering here. We are a UK AI product studio for travel and hospitality: we help hotels, villa managers, tour operators, DMCs and travel-tech teams put AI into real booking and operations systems without creating compliance or trust failures. Enquiry chase is a product-component problem — preference flags, channel scopes and send gates — not a prompt that says “be PECR-aware.”
Primary evidence is first-party UK material from the Information Commissioner’s Office: the Guide to PECR page on electronic mail marketing, the detailed guidance on how to comply with the PECR electronic mail marketing rules (including the products and services soft opt-in), and what else to consider on UK GDPR lawful basis when soft opt-in is used. No invented client open rates, no fictional ICO outcomes.
Why this is a CRM / booking-stack problem, not a prompt problem
PECR regulation 22 sets the electronic mail marketing rule. In short, you must not send electronic mail marketing to individuals unless they have specifically consented, or you meet the soft-opt-in conditions for previous customers / negotiators about similar products or services — with a simple opt-out at collection and in every message. The ICO’s electronic mail definition is deliberately broad: emails, texts, picture/video messages, voicemails, **direct messages via social media**, and similar stored messages. That is why hotels and villa managers chasing incomplete enquiries on WhatsApp-like private messaging still need the same class of control as email — not a separate “chat doesn’t count” story.
The products and services soft opt-in (available to all organisations, including charities for commercial products) requires **all** of the following, as set out in the ICO’s detailed guidance:
- **You obtained the contact details** — directly from the person you want to message. Soft opt-in does not apply to bought-in lists, partner-passed leads, or another group company collecting for you.
- **While selling or negotiating to sell** a product or service — a completed booking is enough; so is an active expression of interest in buying (quote request, more details about what you offer, free trial). Mere browsing, or a location/HR-style query that is not about buying, is not enough.
- **Only your similar products and services** — based on reasonable expectation from the prior interaction; not third-party offers; not unrelated categories people would not expect.
- **Opt-out at collection** — a clear, simple chance to refuse electronic mail marketing when details are first taken (prominent form control or verbal offer). An opt-out buried in a privacy policy, or only added later in a confirmation message, does not meet this requirement.
- **Opt-out in every subsequent message** — simple unsubscribe / STOP-style path, free of charge apart from the person’s own send cost; not “log into your account to change preferences.”
A large language model that “sounds helpful” after an abandoned villa enquiry does not create those facts. If the CRM never recorded opt-out-at-collection, channel scope, negotiation flag and similar-product eligibility, the send is guessing — the same class of failure as bolting AI onto journeys that break in production.
What counts as electronic mail for travel enquiry chase
For AI follow-up design, treat promotional chase as electronic mail marketing when it is advertising or marketing material directed to particular individuals and sent as a stored private message. The ICO is explicit that the same PECR electronic mail rules cover emails, SMS/texts and social-media **direct messages**. Purely administrative service messages (for example confirming a known booking problem without promotional content) are a different category — but stuffing a “similar products” offer into a service message turns that message into marketing.
Live and automated **telephone calls** sit under separate PECR telephone-marketing rules. Do not invent a soft-opt-in path for calls by analogy. If your assistant places or triggers calls, map those flows to the ICO’s telephone guidance with counsel — this article stays on electronic mail channels that hotels and tour ops actually automate after incomplete enquiries.
What changes when AI auto-sends the chase
AI compresses sales follow-up. The moment a tool can enqueue email, SMS or WhatsApp-like marketing without a human clicking send, soft-opt-in eligibility becomes a **pre-send gate** on the workflow — not a style guide for the draft. Consent, where used, must be specific to the **type** of electronic mail (email vs text vs other messaging); a vague “marketing” tick is not specific enough per ICO examples.
What the assistant may draft
- Candidate chase copy **after** a soft-opt-in / consent component has already returned ALLOW for that person, channel and similar-product scope.
- Questions that collect structured enquiry fields (dates, party, product interest) into the booking/CRM record — without claiming that free text alone proves soft opt-in.
- Internal agent summaries and escalation notes when soft-opt-in flags are missing, opted-out, or the enquiry was never a negotiation to buy.
- Solicited replies the guest has specifically asked for (for example “please email me that villa quote”) — which are not the soft-opt-in path and must not be stretched into ongoing similar-product marketing without the gates or consent.
What the assistant must not own
- Inferring soft opt-in from chat tone, abandoned cart heuristics, or “they opened the brochure PDF.”
- Sending similar-product marketing when contact details came from an OTA partner, bought list, or another brand in the group — ICO: you must obtain the details yourself.
- Marketing unrelated products (for example insurance or banking-style add-ons that people would not reasonably expect from that enquiry context) under soft opt-in.
- Skipping opt-out-at-collection because the confirmation email will “mention unsubscribe later.”
- Treating a soft-opt-in email pass as permission for a different electronic mail channel without the right consent/opt-out record for that channel.
- Ignoring an absolute UK GDPR objection to direct marketing — ICO: failing to opt out of soft opt-in does not override an objection; stop marketing processing.
That split matches how Kaize thinks about controlling AI agents that access booking and customer systems: generation is optional; permission to market is not. It also fits connecting booking systems and CRM without a second system of record: preference and soft-opt-in flags need a named owner, not a transcript copy.
Build soft-opt-in eligibility as a product component
Treat PECR soft opt-in as a booking/CRM component contract, not content the model is allowed to improvise.
- **Capture at source:** on web enquiry, chat handoff, call-centre assist and WhatsApp intake, record whether details were obtained directly; whether the interaction was a sale or negotiation to sell; channel addresses collected; and a prominent opt-out choice **at that moment**.
- **Persist flags, not vibes:** `soft_opt_in_eligible`, `opt_out_at_collection_offered`, `marketing_opt_out_email|sms|dm`, `similar_product_scope_id`, `lawful_basis_note` (typically legitimate interests for soft opt-in per ICO, with an assessment where you rely on it).
- **Pre-send gate:** every automated chase path (batch job, agent tool, CRM playbook) must call the component and receive ALLOW/DENY before enqueue. DENY if any soft-opt-in requirement is unmet and no valid channel-specific consent exists.
- **Message envelope:** identity not disguised; valid contact address; simple opt-out in every marketing send; suppression list checked before send.
- **Similar-product ruleset:** map enquiry product family → allowed chase SKUs in application code. The model may draft within that allow-list; it must not invent “you might also like” outside it.
- **Instrument the send:** log gate outcome, basis (soft_opt_in vs consent vs solicited), channel, and whether the assistant was blocked — instrument the CRM/marketing event, not only the chat transcript.
Wire the same gate into every path that can create unsolicited marketing: ESP, SMS gateway, Meta/WhatsApp Business API tools, and any agent that can call `send_message`. A fluent draft without an ALLOW is not a pass.
Incomplete enquiries — when soft opt-in can apply, and when it cannot
Hotels, villa managers and tour ops live on incomplete enquiries: dates held, then silence; a quote opened, then abandoned; a WhatsApp thread that stops mid-party-size. Soft opt-in can cover **negotiating to sell** — ICO examples include requesting a quote or asking for more details about what you offer. It does **not** cover passive browsing, or queries that are not about buying your products/services.
- **Likely negotiation (if other gates met):** guest submits a villa enquiry form for named dates; guest asks “can you quote seven nights in September for four?”; guest requests a brochure/details for a specific tour product.
- **Not enough on ICO’s framing alone:** guest only asks whether you will open a new destination office; guest browses the site without submitting interest in buying; lead scraped from a public directory or partner dump.
- **Still need opt-out-at-collection:** even a perfect quote request fails soft opt-in if staff or the form never offered a simple marketing opt-out when the email/mobile was taken.
If soft opt-in fails, options are: send only solicited content the guest asked for; obtain valid UK GDPR-standard consent specific to the channel; or do not send marketing. Do not “let the AI try once.”
Adjacent controls — do not confuse soft opt-in with booking, price or ATOL gates
PECR soft opt-in sits beside, not instead of, other UK booking controls. A compliant chase message does not fix DMCC total-price presentation when you later show a priced invitation. It does not replace ATOL AST 1.4 disclosures before choice. It does not authorise inventing ETA eligibility on inbound trips — see UK ETA checks before AI confirms travel. Marketing permission is one component; fulfilment and consumer-facing truth are others.
How this fails when AI is bolted onto chase
The failure mode is familiar: marketing wants fewer abandoned enquiries; an agent is given `send_whatsapp` and a prompt to “nudge similar villas”; production sends to partner-sourced mobiles, to guests who never saw an opt-out on the form, or to people who only asked an admin question. Compliance discovers the gap in an ICO complaint file or a spike of STOP replies — not when the demo looked warm.
Instrument chase sends. Log soft-opt-in component results, consent IDs where used, channel, similar-product scope, and blocks. Pair that with the same production discipline used for AI rebooking boundaries: prepare and explain, do not silently own regulated customer-facing actions.
What Kaize will and will not claim
This article is systems and product guidance for UK hotels, villa managers, tour operators, DMCs, OTAs and travel-tech teams implementing AI-assisted enquiry follow-up. It is **not legal advice**, not an ICO endorsement, and not a claim that Kaize has audited any named operator’s marketing stack. PECR and the ICO’s electronic mail guidance remain the primary sources; your compliance and counsel decide how they apply to your channels. We do not invent GSC rankings, GEO scores or client conversion lifts.
If you want a structured review of where AI belongs in enquiry and booking journeys — and which preference and send components must stay deterministic — start with Kaize’s AI Opportunity Review or the practical framing in AI for Travel.
FAQ
Does soft opt-in cover WhatsApp chase after a website villa enquiry?
Only if the PECR electronic mail conditions are met for that messaging path. ICO treats social-media direct messages as electronic mail. You still need direct collection during sale/negotiation, similar products only, opt-out at collection, and opt-out in every message — or valid channel-specific consent. Do not assume an email soft-opt-in flag automatically clears WhatsApp.
We took the mobile for “booking updates only” — can AI still send similar-stay offers?
Not under soft opt-in if you never offered a simple marketing opt-out at collection, or if you only use the number for service messages. Marketing content needs consent or a fully met soft-opt-in. Mixing promotional offers into service messages makes the message marketing.
Is an incomplete enquiry enough to be “negotiating to sell”?
It can be, when the person actively expressed interest in buying (quote, product details, free trial). ICO examples say browsing alone is not enough, and non-purchase queries are not enough. Persist a structured negotiation flag from the form/agent intake — do not let the model invent one later.
Is this legal advice?
No. PECR, UK GDPR and channel-platform rules remain with your compliance, legal and marketing owners. This page explains how AI enquiry-follow-up UIs and CRM automations should keep soft-opt-in eligibility outside freeform generation.