A retention CRM for an online casino is a system that holds the history of every player, predicts what each one is likely to do next, and turns that into a short list of actions for your team: who to contact today, with which offer, through which channel. I run Sellrise, so I am biased, but I will try to keep this definition useful even if you never buy from us.
What does a retention CRM actually do?
It does three jobs, and the order matters. First it keeps one record per player: segments, actions taken, contact history. Second it scores each player with models: churn risk, VIP potential, the chance of the next deposit, and the value the player is likely to bring over 90 days. Third it converts those scores into an action for a person: contact this player today, by WhatsApp, with a reload from your catalogue.
The third job is what separates a retention CRM from a reporting tool. A report tells you that churn went up last month. A retention CRM tells a manager that player 48392 looks like a VIP in the first week and should get a call today.
In Sellrise the screen your team opens every morning is exactly that list. For each player it shows the reason, the priority, the channel, the time to contact, the offer and the next step. The point is to move from "10,000 players" to "the 86 who need attention today". Those numbers are from our demo data, not from a client.
How is it different from a generic CRM or a marketing automation tool?
A generic CRM stores contacts and deals. A marketing automation tool runs journeys that your team designs: if a player does X, send Y. Both are useful, and both depend on a human deciding the rules and the segments in advance.
A retention CRM adds a prediction layer underneath. Instead of a segment such as "no deposit in 14 days", you get a per-player score and a reason. Instead of one offer per cohort, you get an offer matched to the player's stage and value, and sometimes the answer "do not give this player a bonus now, they are already winning".
That last point is where a lot of bonus budget goes. The same bonus for the whole base is expensive, because part of it goes to players who were going to deposit anyway. A retention CRM should be able to show you what bonuses actually did: deposits after the bonus, and how much of that the bonus itself brought.
None of this makes a generic tool bad. If your team already runs strong event-driven journeys, you may only need the prediction layer next to them. I wrote up the honest trade-offs against established platforms in our comparison pages.
What data does a retention CRM need?
Less than most teams expect. For the forecasts in Sellrise we need four tables keyed by Player ID:
- Players
- Deposits
- Bets
- Sessions
Name, phone and email are optional and only needed if messages and calls go through the system. A Player ID is enough for the models. Every client gets a separate database, and integration is at our cost.
In general terms, the work behind any scoring system is mostly in the data layer, not in the model. Features should be computed from raw transactions at the moment of scoring, never from pre-aggregated platform statistics that may already contain information from the future. I wrote about this in more detail in two engineering notes on per-player scoring architecture and gradient boosting for iGaming retention.
What forecasts should it produce?
Four are worth asking for, and each should be shown honestly:
- Churn risk: who is about to leave, flagged before they are gone rather than after they show up in a report.
- VIP potential: future VIPs spotted from the first week after the first deposit, so a manager can pick them up early.
- Chance of the next deposit: especially the step from a one-time depositor to a returning player, when a well-timed offer matters most.
- Value over 90 days: always as a range. A single number on a 90-day horizon is fiction, and a system that gives you one is hiding its uncertainty.
If a vendor shows you only a risk score with no reason, ask for the reason. Your team will not act on a number nobody can explain.
Who decides and who sends?
In our model, your team. Sellrise suggests, a person decides and sends, through your own channels or through ours (SMS, Viber, WhatsApp, email, Telegram and calls; push and in-app go through your platform). Nothing goes out on its own.
There is a scale of automation and you choose where to stand on it. As a CRM, all players, segments and contacts live in Sellrise and your team works inside it. With suggestions, Sellrise proposes the action and a person decides. On autopilot, scenarios run within your rules. We switch autopilot on only after the pilot, once the result is proven on your own players.
I prefer that order because a model that has not yet been checked against your data should not be sending messages to your customers.
Does a retention CRM replace the CRM we already have?
Not necessarily. Sellrise works alongside your platform and CRM: your scenarios stay where they are, and the system gives your team lists and suggestions as an export or over an API. If you do not have a CRM, it can be your main one.
Whether to run it alongside or as the main system is a practical question about your team. If you have a CRM team that already builds journeys, keep them and add the forecasts. If you have a small team and a thin ARPU, one system is simpler.
How do you know a retention CRM works?
You measure it on your own players. The test I recommend, and the one we run in a pilot, has three groups: a control group that nobody contacts, your team working as it does today, and your team following the system's suggestions. After one month you compare average turnover per player in each group. The difference is the effect.
We do not quote percentages before the test, because any percentage we could quote would come from someone else's players. We agree the group sizes and the metric before we start, so nobody can move the goalposts afterwards.
This is also the question to ask any vendor: how will you prove it on my data, and what happens if you cannot?
Who is a retention CRM not for?
Be honest about fit. Sellrise has no gamification: no loyalty mechanics, missions or tournaments inside your product. If gamification is your first lever, look at platforms built for it. If you want a full enterprise marketing hub at the centre of your stack with a dedicated team building campaigns, that is a different category, and I would not pretend otherwise.
It fits when you want a forecast for every player and a short list for today, when your ARPU is thin enough that per-seat pricing hurts, and when you want to keep the stack you have. If that sounds like you, the demo runs on synthetic data and shows the morning list, or you can start a pilot on your own players.