Clients Overview
The Clients section in IZI CRM is the registry of all identified players at your club. Each client card stores contacts, two balances (gaming and bonus), complete session and transaction history, group memberships, and staff notes. The database builds automatically from the first identified visit — every cashier action or app operation updates the card in real time. For club owners this means a live picture of who is spending what and when; for admins it means a one-screen answer to “who is this person and what is their balance right now.”
What the client database is in IZI
Section titled “What the client database is in IZI”The key distinction is between identified clients and anonymous guests. An anonymous guest starts a session without a phone number — revenue is recorded but no profile is created. An identified client has a card with a phone number: history accumulates, bonuses accrue, and automation rules can target them.
The client list is not just a contact directory. It is an operational tool: open a card and immediately see the balance, visit count, last visit date, and which groups the client belongs to. A marketing admin filters by activity level and triggers a re-engagement rule. A club owner compares average spend across VIP and regular segments for the month. All of this runs on one data structure — the player card.
How clients enter the database
Section titled “How clients enter the database”Four channels feed the database and complement each other:
Cashier registration on first visit. The admin opens the “Register client” form, enters a name and phone number — the card is created instantly. The only mandatory field is name; a phone number is required for a full identified profile. Email, date of birth, and groups are optional and can be filled in later.
Self-registration via the mobile app. The guest downloads the IZI app, enters their phone number, and confirms it — the card is created automatically and appears in the club database on first visit. This reduces cashier workload and delivers a verified phone number.
Manual addition. An admin can create a card at any time without linking it to an active session — for example, to register a client who is not yet in the system.
Bulk migration. When switching from another system, the client base is transferred via API. The minimum data set is name and phone. Balances from the old system are transferred separately through financial operations; session history is not imported and counters start from zero in IZI.
What a client card stores
Section titled “What a client card stores”The card is structured in blocks for both quick viewing and analytics.
| Block | Contents | Where it is used |
|---|---|---|
| Identity | Name, last name, phone, email, date of birth | Search, segment-based automations, notifications |
| Balances | Gaming balance (real money), bonus balance | Session and product payments, bonus accruals |
| Groups | List of groups the client belongs to | Special tariffs, automations, segmentation |
| Stats | Session count, registration date, last visit | Segmentation, ARPU/LTV calculations |
| History | Recent sessions, transactions, orders (tariffs, products, combos) | Admin context, dispute resolution |
| Notes | Free text visible only to staff | Personal approach, agreed terms |
Two balances are the core difference from a plain contact list. The gaming balance holds real money deposited at the cashier or via the app. The bonus balance holds virtual credits from the loyalty programme — spendable but not withdrawable. Every movement on both balances is stored with its source: cashier, app, automation rule, manual adjustment, or refund.
Searching and filtering clients
Section titled “Searching and filtering clients”In the Clients section, the search bar at the top of the list finds clients by:
- Phone number — the most common method at the cashier
- Name — partial match works
- Email — full or partial
Beyond search, the list supports filters:
- Group membership
- Gaming balance range
- Bonus balance range
- Total spend over any period
- Total time played
- Last visit date range
- Whether the client has a phone on file (useful for identifying completeness of the base)
Client groups and tags
Section titled “Client groups and tags”Groups are named segments within a single club. Examples: VIP, Newcomers, Students, Corporate, Tournament Players. One client can belong to multiple groups at the same time.
Each group has a name and an optional description. The club’s group list is managed in a dedicated section that also shows how many clients are in each group and when the group was last updated.
Groups serve four main purposes:
- Special tariffs. Assign a tariff with a different price or conditions to a group — for example a student daytime rate or a VIP tariff with a reserved zone.
- Automation rules. A rule with the condition “client is in group VIP” awards a higher bonus or sends a custom notification.
- List filtering. On the Clients page, filter by group to work with only the relevant segment.
- Bulk assignment. Select multiple clients and add them all to a group in one action without opening each card individually.
Group management inside the client card: the Groups block uses a multi-select; changes save instantly.
Calculating ARPU and LTV from the client base
Section titled “Calculating ARPU and LTV from the client base”Both metrics are calculated from the active identified base — cards with a phone number that are not archived. Anonymous guests are excluded because they cannot be deduplicated.
ARPU (average revenue per user over a period)
Section titled “ARPU (average revenue per user over a period)”ARPU = Revenue from identified clients in period ÷ Unique clients with at least one payment in periodThe denominator is “clients with at least one payment,” not “registered clients.” Including all registered clients dilutes the metric with an inactive base. ARPU should reflect revenue from the paying audience.
Choose the period to match the task: weekly ARPU for operational monitoring, monthly for segment comparison, quarterly for trend analysis.
LTV (lifetime value)
Section titled “LTV (lifetime value)”Simple model:
LTV = Average monthly ARPU × Average number of active months per clientWhere an “active month” is any month with at least one payment. For a multi-club network, calculate LTV per club separately — audience mix and average spend differ across locations, and a blended average is misleading.
More precise model incorporating churn:
LTV = Monthly ARPU ÷ Monthly Churn RateWhere Churn Rate is the share of clients who did not return within N days (choose N for your club — typically 30 or 45). At 20% monthly churn, LTV equals 5 months of ARPU. At 10% churn it equals 10 months. Reducing churn by 5 percentage points doubles LTV — which is why retention through a bonus programme pays back faster than acquisition spend.
Segment ARPU
Section titled “Segment ARPU”The most actionable use is comparing ARPU across groups:
Segment ARPU = Revenue from group clients in period ÷ Group clients with at least one payment in periodIf the VIP group ARPU is significantly higher than the base average, that ratio signals how much value a loyalty programme can unlock by moving more clients toward VIP behaviour. Substitute your own figures from club analytics.
What connects to the client card
Section titled “What connects to the client card”The card is not an isolated profile. It ties together several IZI modules:
Bonus programme (Top-up bonus guide). Every accrual from an automation rule appears on the card’s bonus balance with a source label. Expiry records are stored in the same movement history.
Retention via bonuses (Bonus engine overview). Segment rules for “sleeping client,” “newcomer,” and “VIP” are linked to the card through groups and last visit date. Automation reads the card state and triggers the action.
Mobile app (IZI mobile app overview). The client sees their card in the app: balance, history, active bonuses. A top-up via the app updates the card in real time.
Archiving and client status
Section titled “Archiving and client status”IZI supports soft archiving. An archived client does not appear in the main list, but their history and balances are fully preserved and can be restored at any time. Hard deletion without restore is not available in the standard UI.
Clients can also be blacklisted — see Blacklist a client for the workflow.
Bulk actions
Section titled “Bulk actions”Select multiple clients in the list using checkboxes, then:
- Add all selected clients to a group
- Export selected to CSV or Excel
See also
Section titled “See also”- Register a new client
- Client history
- Client segments
- Manage balance
- Blacklist a client
- Top-up bonus guide
- Bonus engine overview
- Tariff basics
- IZI mobile app
Client card fields and available filters depend on your IZI version and organisation settings. ARPU and LTV formulas are parametric — substitute your own average spend, visit frequency, and churn rate from club analytics.
Frequently asked questions
What is the client database in IZI?
The client database is the registry of all identified players at your club. Each player has a card with contacts, two balances (gaming and bonus), full session and transaction history, group memberships, and admin notes. The database builds automatically from the first identified visit — every cashier or app action updates the card in real time.
What data does a client card store?
First name, last name, phone (required for an identified profile), email, date of birth, groups, admin notes, gaming balance, bonus balance, session count, registration date, last visit date, and full history of transactions, orders, and sessions.
What is the minimum required to register a client?
A name is mandatory. A phone number is required for a full identified profile — without it the person is treated as an anonymous guest with no card. Email and date of birth are optional and can be filled in later.
Can a client have accounts in multiple clubs?
Yes. If clubs are in the same IZI organisation with shared loyalty enabled, one client account works across all clubs. Otherwise each club maintains its own client list.
What are client groups and why do they matter?
Groups are named segments within a club — for example VIP, Students, or Corporate. A group can be assigned a special tariff or automation rule, making it the primary tool for differentiated pricing and targeted marketing. One client can belong to multiple groups simultaneously.
How do I search for a client in IZI?
Use the search bar at the top of the Clients list. You can search by name (partial match works), phone number, or email. You can also filter by group, gaming balance range, bonus balance range, total spend, time played, last visit date, and whether the client has a phone on file.
Is session history visible in the client card?
Yes. The client card has tabs for recent sessions, recent transactions, and recent orders (tariffs, products, combos). A session counter is shown separately in the stats block.
Where are balances and top-ups shown in the client card?
In the Financial Information block: gaming balance (real money) and bonus balance. The movement history for both balances is in the Recent Transactions tab. Each entry shows its source: cashier, app, automation rule, manual adjustment, or refund.
Can a client be blocked or archived?
Yes, IZI supports soft archiving. An archived client does not appear in the main list, but their history and balances are preserved and can be restored. Hard deletion without the option to restore is not available in the standard UI.
What does the admin note field do?
The note is a free-text field on the client card, visible only to club staff. Use it for service remarks — preferences, agreements, context for a personal approach. Notes are not included in statistics or automation conditions.
How do I segment the base for marketing?
Basic segmentation uses client groups. Advanced segmentation uses list filters: total spend, balance, last visit, activity level. For automated campaigns (for example 'not visited in 14+ days' or 'new client under 30 days') use the Automations module with segment-based conditions.
How does IZI distinguish a one-time guest from a registered client?
A one-time guest is a session with no phone — no identified profile. A registered client has a card with a phone number. One-time guests cannot be deduplicated: the same person without registration creates a new anonymous session each visit. The 'unique clients' base therefore only counts cards with a phone number.
Can I export the client list?
Yes. In the Clients section use the export function to download a file with name, contact details, groups, financial figures, and session statistics for selected columns. Format is CSV or Excel depending on organisation settings.
How is the client card connected to the loyalty programme?
The bonus balance in the card is the loyalty programme account. Accruals from automation rules (top-up bonus, promo codes, referral programme) appear as transactions with a source label. Bonus expiry is visible in the movement history — all in one place.
Can I import clients from another system?
Migration from third-party systems is possible via the IZI API; see the migration documentation for details. The minimum data set is name and phone. Balances from the old system are transferred separately through financial operations. Session history from external systems is not imported — counters start accumulating from zero in IZI.
How many clients can the IZI database hold?
There is no limit on the number of clients. All data is stored in the IZI cloud.