For licensed iGaming operators
Player data in a warehouse that is yours, lifecycle stages and churn risk from each player's own history, journeys on every channel you send on, and support on the same record – with self-exclusion, opt-outs and your own rules enforced where each message and bonus is sent.
The operator's week
Self-exclusions live in one system and campaign lists in another, joined by an export that ran yesterday. A player who self-excluded this morning can still be in Saturday's free-spins send – the one message that player must never receive, and the one your compliance team will be asked about.
When every amount on a player's record is read as a sale, withdrawals and payouts land in revenue, the return on a campaign looks better than it was, and the retention report says a win-back paid for itself when it did not.
A player writes in about a bonus that expired last week. The agent cannot see what was granted, the CRM team cannot see the complaint, and the next journey step sends the same player a reminder to use it.
Each brand needs its own voice, senders, lists and rules, and one team still has to see all of it. With separate tools per brand, every list is exported twice, every rule is kept in two places, and each copy is one more place for a mistake.
What you get
Deposits, withdrawals, bets, wins and bonus grants arrive as events under your names, with the player roster (status, tier, KYC state, self-exclusion flag) and your catalog of games and bonuses. You declare what counts as revenue, so a withdrawal is never counted as one.
Eight lifecycle stages computed from each player's own history, and churn risk ranked by the value at stake. When a player moves from active to at risk, the move is an event, and a journey can start on it the same day.
Email from your own domain, SMS through your own provider, WhatsApp through your own Business account, web and app push, and website messages, in one journey with waits, splits and goals. Holdout groups show what a journey caused, not what happened near it.
Lists that block everything, suppress marketing, or flag a player for care – filled by hand, by import or from your own systems. A player on a marketing-suppression list stops getting offers and still gets the payout notice. If a list cannot be read, the send does not go.
Your platform keeps the reward and credits it; The AI CMO holds the catalog, decides who gets what and sends a signed grant instruction. Exclusion rules run before anything is delivered, and a journey continues only for players whose credit actually applied.
Every conversation sits on the player's record. A request to self-exclude, a sign of harm, a chargeback or a legal threat never reaches a model. It goes to a person, and on a chat the AI stays paused until someone allows it again. Knowledge about a promotion stops being used after the end date you set.
How the week runs
From your warehouse, the retention specialist proposes the week: the high-value players going quiet, the new players who have not come back, the win-back losing steam, each with the money at stake.
Approved journeys move each player by what they did, across every channel you send on. The lists are checked at every send, and service messages such as a payout notice keep reaching players who stopped marketing.
What was sent, what the lists stopped and what the holdout groups say the journeys earned – every stopped send logged, in a history no one can edit.
Governance
Approval where you place it
ask first, wait a day or publish at once – set per agent, so your team decides which work waits for a yes
Hard limits
budgets, channels and actions pass one policy gate – there are no side doors
Suppression at the core
0 sends to a suppressed customer, enforced in the send path itself
A history of every action
append-only – even owners can't erase it
Questions
An iGaming CRM is the system an operator uses to know each player (what they deposit, play and claim) and to decide what to send them, when, on which channel, and who must not be contacted at all. On The AI CMO it runs on your own player data, with self-exclusion and opt-outs enforced where each message is sent.
Your team keeps the register; the platform enforces it. Players go on a list that suppresses marketing or blocks everything – added by hand, imported, or sent by your own systems as the register changes. Every send, journey enrollment, audience build and bonus grant checks the lists first, and every stopped send is logged.
The message never reaches a model. It goes to the people who take that brand's tickets, marked as needing a person, with a short holding reply prepared for them to review; on a chat, the AI stays paused on that conversation until someone allows it again. Recording the exclusion stays with your team and your systems. Once it reaches your list, every send respects it.
No, and it does not pretend to. Rules differ by jurisdiction and change. Your team writes what your license requires as your own brand rules: the platform follows them when it writes, and checks agents' work against them before it publishes. The platform's own industry notes are shown as advice, never as a block.
Yes. Each brand keeps its own voice, senders, player records, lists and rules, and a blacklist can be copied from one brand to another. The Helpdesk opens on All brands: one queue, each conversation naming its brand. Enterprise carries unlimited brands and seats.
Your platform keeps the reward and credits it. The AI CMO holds the catalog, decides who gets what and delivers each grant as a signed instruction; your platform reports back when the player claims or uses it. Exclusion rules run first, and a stopped grant is reported as suppressed, never silently dropped.
Read next
See it on your own player data – arrange a walkthrough, or talk to us about enterprise volumes.