Players & CRM
The Players area is the operational heart of the CRM.
The player list
- Search / sort / filter by name, status, and lifecycle stage.
- Bulk status actions — select multiple players and change status at once.
- Mobile card view for smaller screens.
- CSV import / export — bring players in, or export the current view.
Player 360
Open any player for the full record:
- KPIs — deposits, withdrawals, GGR/NGR/wagered, counts, last activity. These are derived from the event stream by the worker, not entered by hand.
- Timelines — paginated events, sessions, and transactions, with “load more”.
- Lifecycle — the current stage plus a transition history.
- Consent — a master marketing consent plus per-channel consent, and a per-player frequency-cap override.
- Identity & contacts — profile fields, phone, country, Telegram connect.
- Ownership — the host / VIP manager who owns this player’s book.
Where player data comes from
Players are created and updated automatically when the PAM pushes events (the
player is upserted by (brand, player_id)). Identity fields (email, name, …) can
be populated by the integration’s player field map,
by CSV import, or edited manually.
Data quality
Players → Data quality is a completeness/hygiene dashboard: missing or invalid email, no consent, duplicate email, missing name/phone/country/DOB, with a per-field health score. Use it to find and fix gaps that would hurt deliverability or segmentation.
Custom fields
Operators can define custom fields on players (Settings). Values are stored
per player and can be set by the integration’s mapping
(custom_field:<key>), by import, or manually — and used in segments.
Consent & responsible gaming
- Consent is respected by messaging: a player with marketing consent off is suppressed from outbound comms; per-channel consent narrows it further.
- Responsible gaming status (self-exclusion, limits, cooling-off) is flagged via the player’s status/events. Operators flag players manually via player status where needed.