Player lifecycle, defined and enforced
Define the stages your operation actually uses, then move players automatically with rules — each testable against real players before it is applied, with movement safety and manual-override handling.
iGaming CRM & retention Comply, engage,
Comply, engage,
and grow.
Built for regulated markets: multi-brand operator structure, player lifecycle and reactivation — with consent enforced in the mechanism and every action recorded.
The operator's problem
Several brands, several markets, one compliance obligation
- Multiple brands under one operator, each needing its own data, currency and reporting
- Acquisition is expensive, so retention and reactivation carry the economics
- Every message has to respect consent and the rules of the market it lands in
- Regulators and partners expect a record of what was sent, to whom, and on whose authority
Multi-brand by design
Each brand isolated, all of them from one login
Brand isolation is structural rather than a plan tier. Each brand has its own separated data store, branding, currency, timezone, team and reporting.
- Separate data per brand — nothing crosses between them
- Per-brand currency, with metrics split by platform rather than summed across currencies
- Roles scoped per brand for staff, contractors and partners
- Custom short-link domains per brand, so links carry the brand rather than a generic shortener
Retention and reactivation
Where the economics actually are
Acquisition costs what it costs. The difference is made by noticing someone is drifting before they are gone.
Risk scores as an audience, not a chart
Churn risk, engagement and channel preference are conditions in the segment builder, so “high risk, previously high value, reachable and opted in” is one segment that keeps itself current.
Reactivation that stops when they come back
Build the lapsed-player audience from real behaviour, run it as a journey, and let it exit the moment someone returns — so nobody is chased after they are already back.
Compliance and responsible gaming
Controls that are part of the mechanism
These are product behaviours rather than policies written on a page.
Consent enforced at the point of sending
A global unsubscribe blocks everything. Email, SMS and WhatsApp each require their own opt-in. Skips are reported honestly as consent skipped rather than quietly dropped.
The models will not recommend contacting someone they shouldn't
Where a player cannot be contacted, the recommended action returned is to wait. The system does not suggest an action it is not permitted to take.
An audit trail over every action
Including the actions an agent took rather than a person — which is the question that actually gets asked in a review.
Approval before anything reaches a player
Set any agent to hold its work in a queue. Promotional content shows its code, discount, validity and target segment before you release it.
Consent management on your own site
Categories, enforcement, expiry, versioning that can force re-consent when the policy changes, and support for the browser's Global Privacy Control signal.
Responsible gaming obligations differ by market and remain yours to define. What Nommos provides is the enforcement surface — consent, approval, roles and a record — rather than a claim to satisfy any particular regulator.
The sports betting preset One of three industry presets shipped today. The agents start with topic sources, content patterns, offer types and calls to action appropriate to sports betting, then the brand profile shapes them to your operation's voice.
Switch between two brands, then look at the audit trail
Those two things together answer most of what an operator wants to know in the first ten minutes.