Request a demo

Satome Labs · CRM and progression

iGaming CRM and progression built on dynamic segments

A segment is a rule that stays current as players deposit and play. Bonuses and messages use the same audience and the same preview-and-confirm path.

Segments are rules

A segment describes who counts as the audience, for example “two or more deposits in seven days”, “deposited at least 10,000 in thirty days”, or “deposited once and has not placed a bet in thirty days”. It stores the rule, not the players, and is evaluated from the deposit and bet tables when it is used. Bonus campaigns and CRM broadcasts take their audience from the same segment, so a campaign and its message always target the same people.

ConditionMeaningExample
Deposits in a windowAt least N approved deposits in the last D daysSecond deposit this week
Deposit sum in a windowApproved deposits add up to at least XVIP candidates
Days without a betNo bet in the last N daysDormant depositors

Messages follow the same discipline

A broadcast to a segment is a mass operation, like a bonus grant. The operator prepares it in chat or in the screen, sees the recipient count, a sample and the exact text, and confirms. Only then are messages queued. Confirming the same plan twice does not duplicate them, and recipients are taken from the segment at the moment of confirmation.

A message about a bonus is a separate decision from the bonus itself: one campaign, one broadcast, each with its own preview and its own audit record.

Progression, player states and experiments

Every player has a live state: new, active, at risk or lapsed, and a move between states is an event the platform can act on. Loyalty tiers and welcome journeys are costed before they go live. A campaign can hold out a control group, so the lift in retention is measured, not assumed.

Runs on Satome or on top of your platform

CRM and progression work as a standalone module. Player events (deposits and bets) come in from your platform by webhook or API, decisions are made here, and rewards go out through your own bonus engine and wallet.

Why it matters

  • No stale lists. Nobody exports a file on Monday and mails it on Thursday.
  • One audience, two actions. The bonus and the message cannot drift apart.
  • People stay responsible. A message to live players is never sent by the AI alone.

Questions and answers

What is a dynamic segment?

A segment is a rule, not a list of player ids. It is computed from deposit and bet facts at the moment you ask, so a player enters and leaves it automatically and there is no list to refresh.

Which conditions can a segment use?

The number of approved deposits in a window of days, the sum of approved deposits in that window, and the number of days without a bet. Conditions combine with AND. Cancelled attempts are not counted.

Which channels does CRM support?

Push, SMS and LINE. Delivery runs through the operator's own provider; in the demo, confirmed messages are queued.

Does CRM send anything on its own?

No. A broadcast is a mass operation, so it follows the same path as a bonus: plan, preview with recipient count and sample, confirmation by an operator, then queueing.

Want to see it on your use case?

See it running on a live demo: a player-facing casino and a back office you can talk to.