Consent-Gated Player Communication Workflows

Why check at send time

An automated flow can run for days or weeks. A customer who entered a welcome series on Monday may self-exclude on Tuesday, opt out of text messages on Wednesday or be flagged by a safer gambling interaction on Thursday. If the flow checked eligibility only on entry, every later step would be sent on stale facts.

In Great Britain, social responsibility code 3.5.3 asks for all reasonable steps to keep marketing away from self-excluded customers, as set out in suppression for self-exclusion and objections. A send-time check is the most direct of those steps.

The gate, in order

Step 1 comes first because safeguarding outranks any permission: a customer can hold a valid opt-in and still be excluded. Step 2 follows because the Information Commissioner's Office (ICO) describes the right to object to direct marketing as "absolute". Step 4 reflects code 5.1.12 (Great Britain, remote casino, bingo and betting licensees), under which customers must not receive direct marketing that goes against their product or channel preferences. Step 5 reflects code 5.1.11's requirement to "be able to provide evidence" of consent: if the evidence is incomplete, a person should look before anything is sent.

You can run this order on your own examples in the offline consent decision tool.

Safer gambling signals

Remote licensees in Great Britain must also stop marketing when the customer interaction process requires it. Treat an active safer gambling flag like an exclusion in step 1. Safeguarding overrides and protective messages explains how to keep protective messages flowing while marketing stops.

What the workflow itself should look like

1. Trigger. An event such as registration, first deposit or inactivity.
2. Wait or branch. Delays and branches never send on their own.
3. Gate. Each send step calls the decision point and receives eligible for human review, suppress or hold.
4. Approve. A person, or a campaign rule a person signed off for that market and template, approves an eligible send. The approver and the reason code are written to the send log.
5. Send. Only after that approval.
6. Exit. A suppress result for an exclusion or objection removes the customer from the flow entirely.

Example, illustrative only. A welcome series has three emails over seven days. On day 3 the customer opts out of casino email but keeps betting email. Email 2 promotes casino games, so the gate suppresses it; email 3 is a betting update, so it is eligible and goes on to approval. If the customer had self-excluded instead, the gate would suppress email 2 and remove them from the flow.

Failure modes to design out

• Fail-open checks. If the decision service is unreachable, hold the send.
• Cached segments. A segment built at 9:00 is used at 17:00 without re-checking.
• Side channels. Text messages sent by a separate tool that does not call the gate. Channel rules for those messages are in sender and opt-out rules for texts.
• Manual sends. One-off campaigns uploaded as files. The Gambling Commission lists "manual “workarounds”" among reported causes of marketing to self-excluded customers.

Before launch, test every one of these with the workflow test plan. If you are choosing a platform to run these flows, the automation platform criteria turn the same failure modes into vendor tests. The rest of the automation guides cover propagation, message rules, safeguarding and testing.