IZI Automation — Rule System Overview
IZI Automation: How the Rule System Works
Section titled “IZI Automation: How the Rule System Works”Automation in IZI follows the pattern “when event X occurs and condition Y is met — perform action Z”. A rule is configured once and then runs on its own: accruing bonuses, sending notifications, moving clients between groups. No admin involvement required.
Automation powers the deposit bonus, the rank system, balance status notifications, and any other scenario that should fire on a client event.
Where to find the section
Section titled “Where to find the section”In the sidebar, select your organization → Automation. The page shows a list of all rules with name, status (active / inactive), and creation date.
Rules are created at the organization level and apply to all clubs by default. You can restrict a rule to specific clubs when creating it.
What a rule consists of
Section titled “What a rule consists of”Every rule has three components:
1. Trigger event — what must happen for the rule to fire. One rule — one event. Full list → Triggers catalog.
2. Conditions — optional filter. If conditions are set, the rule only runs when the client meets them. You can check accumulated hours, spending amount, group membership, balance. Details → Rule conditions.
3. Actions — what happens: accrue bonuses, send a notification, add or remove a client from a group. One rule can contain multiple actions — they execute in order. Full list → Actions catalog.
Execution lifecycle
Section titled “Execution lifecycle”When a client performs an action (ends a session, tops up balance, etc.), IZI:
- Finds all active rules with a matching trigger event
- Checks each rule’s conditions for this client
- For rules where conditions are met, executes the actions
- Records the result in the execution history
A rule with status Skipped means the event occurred but conditions were not met — this is normal, not an error.
Scope: organization and clubs
Section titled “Scope: organization and clubs”A rule is created at the organization level, but can be restricted to specific clubs:
| Setting | What happens |
|---|---|
| Clubs field is empty | Rule runs in all clubs of the organization |
| Specific clubs selected | Rule only fires in those clubs |
This lets you test a new mechanic on one club without affecting the others. Once you confirm it works, expand it to the whole network.
What you can automate
Section titled “What you can automate”Core scenarios:
- Deposit bonus — a progressive ladder where the percentage grows with the top-up amount
- Rank system — move clients into groups based on accumulated hours or spending
- Notifications — inform clients about bonus accruals, rank achievements, balance expiry
- Bar cashback — a percentage of the order total credited to the bonus account
- Welcome bonus — accrue a bonus on a new client’s first session
Each scenario gets its own rule. Multiple rules on the same event run simultaneously and do not interfere with each other.
How to create your first rule
Section titled “How to create your first rule”Step-by-step walkthrough for creating and configuring a rule → Create an automation rule.
Troubleshooting
Section titled “Troubleshooting”If an expected action did not happen:
- Check that the rule is active (toggle is on)
- Open the execution history — look at the status for the specific client
- Status Skipped — conditions were not met; review the condition logic
- Status Error — problem at the action level; open the entry and read the error details
See also
Section titled “See also”Frequently asked questions
How is an automation rule different from manually accruing bonuses?
A rule fires on its own — no admin involvement. Set it up once: every time a balance is topped up, a session ends, or an order is paid, the system automatically accrues the bonus, sends a notification, or moves the client to the right group. Manual accrual is a one-time admin action in the client's profile.
Can I create a rule for just one club instead of the whole network?
Yes. When creating a rule, select specific clubs in the Clubs field. If you leave it empty, the rule applies to all clubs in the organization. This is convenient for local promotions without affecting the rest of the network.
How many rules can I create?
There is no limit on the number of rules. Rules are processed sequentially for each event, so it is better to create separate rules for different events rather than trying to combine everything into one.
What happens if a player matches multiple rules at the same time?
All matching rules execute — each independently. If two rules accrue bonuses for the same event, the client will receive both accruals. Watch for overlapping conditions.
Where can I see the execution history for a specific rule?
In the Automation section, open the rule and go to the History tab. Each execution is listed with its status: completed, skipped, or error. More details in the execution history section.
Can a rule be temporarily disabled without deleting it?
Yes. The Rule active toggle turns it on or off. An inactive rule retains all its settings and does not run until you re-enable it.