Automation in IZI: What Can Be Automated and How It Works
Automation in IZI: What Can Be Automated and How It Works
Section titled “Automation in IZI: What Can Be Automated and How It Works”Automation in IZI is a system of rules that operate independently after a one-time setup. Every rule follows a single scheme: event → condition → action. A client finishes a session, tops up their balance, reaches an hours threshold — the system checks whether the client meets the rule’s conditions, and if so — awards bonuses, moves them to a new group, sends a notification. No administrator involvement required.
The Event → Condition → Action Paradigm
Section titled “The Event → Condition → Action Paradigm”Any rule is assembled from three components:
Trigger event — what must happen for the rule to activate. One rule — one event. You cannot set “top-up OR session end” in one rule — two separate rules are needed.
Conditions — an optional filter. Without conditions, the rule fires for all clients who experienced the event. With a condition — only for those who match it. Example: “event = top-up” + “condition = top-up amount ≥ threshold” — the rule fires only on large top-ups.
Actions — what happens: award bonuses, send notification, add or remove client from a group. One rule can contain multiple actions — they execute in order.
Full trigger catalog → Trigger Event Catalog. Full action catalog → Action Catalog.
What Can Be Automated in a Club
Section titled “What Can Be Automated in a Club”Bonus Program
Section titled “Bonus Program”The primary scenario — awarding bonuses for balance top-ups. Classic setup: multiple rules with different amount thresholds, each giving a higher percentage.
| Top-up Threshold | Bonus Percentage |
|---|---|
| From baseline × 1 | 4–6% |
| From baseline × 2–3 | 10–14% |
| From baseline × 5+ | 18–22% |
Where baseline is the average top-up for your database. More on building the ladder → Top-up Bonuses.
Second scenario — bar purchase cashback: rule on “Order payment” event, action “Award bonuses,” formula {{order_total}} * 0.05.
Rank System
Section titled “Rank System”Ranks are built through client groups and automation rules. Each rank is a group. When a session ends, the rule checks the client’s accumulated hours (or spend) and if a threshold is reached — removes the old rank and assigns the new one.
Three-tier system example:
- Bronze — from 1 hour
- Silver — from 10 hours
- Gold — from 50 hours
Step-by-step setup → Rank System Setup.
Client Notifications
Section titled “Client Notifications”Rules automatically inform clients of significant events: bonus awarded, new rank reached, bar purchase made. The notification arrives through the IZI mobile app at the moment of the event — no SMS costs and no delay.
Returning Dormant Clients
Section titled “Returning Dormant Clients”When a client hasn’t returned for 14+ or 30+ days, rules can send a reactivation notification with a personal offer. The bonus expiry period is set short (5–7 days) — creates an incentive to spend quickly without being aggressive.
More on the return strategy → Anti-Churn Automation.
Welcome Mechanics
Section titled “Welcome Mechanics”“First session” rule: event “Session ended” + condition “Session count = 1” + actions “Award bonuses” + “Send notification.” A first-time client immediately receives a welcome bonus and notification — this locks in the first impression.
Where the Section Is Located
Section titled “Where the Section Is Located”In the sidebar menu: Automation. List of all rules with name, status, and creation date. Rules are created at the organization level and by default apply to all clubs.
Application Levels
Section titled “Application Levels”| Setting in “Clubs” field | What Happens |
|---|---|
| Field empty | Rule works in all organization clubs |
| Specific clubs selected | Only in those clubs |
Leave the field empty for network-wide mechanics (bonus ladder, ranks). Select a specific club for testing or local promotions.
Rule Firing Lifecycle
Section titled “Rule Firing Lifecycle”On every client action, the system:
- Finds all active rules with a matching event
- Checks each rule’s conditions for this client
- For rules where conditions are met, runs the actions
- Records the result in the firing history
If a client matches multiple rules with the same event — all of them execute. Rules don’t conflict or block each other.
Diagnostics
Section titled “Diagnostics”If an expected action didn’t happen:
- Verify the rule is active — toggle is on
- Open the rule history: find the entry for the relevant client
- Status Skipped — event occurred but conditions weren’t met; check condition logic
- Status Error — problem at the action level; open the entry and read the details
- No entry at all — event didn’t occur or the rule was inactive at the time of the event
Typical Rule Set for a Club
Section titled “Typical Rule Set for a Club”Minimal working configuration:
| Rule | Event | Purpose |
|---|---|---|
| Top-up bonus | Balance top-up | Core motivation to top up |
| Welcome bonus | Session ended (1st) | Lock in first visit |
| Rank system (3–5 rules) | Session ended | Retention through progression |
| Rank notifications (3–5 rules) | Group assigned | Client awareness |
| Bar cashback | Order payment | Upsell incentive |
Expansion: reactivation of dormant clients, additional bonus top-up tiers, personalized promotions for specific groups.
Rule Management
Section titled “Rule Management”- Enable/disable — toggle on the rule card or in the list
- Edit — changes apply to future firings; past history is unchanged
- Duplicate — useful for creating similar rules (e.g., different bonus ladder tiers)
- Delete — irreversible; if in doubt — disable instead
How to create your first rule → Creating Your First Automation Rule.
See Also
Section titled “See Also”Frequently asked questions
What is automation in IZI?
Automation is a rule of the form 'when event X happens and condition Y is met — perform action Z.' Set up once: awards bonuses, moves clients between ranks, sends notifications without administrator involvement.
How is automation different from manual bonus awards?
A rule fires automatically on every matching event. Manual award is a one-off administrator action in a client card. Automation scales to the entire database without additional effort.
Can automation be restricted to a single club?
Yes. When creating a rule, select specific clubs in the 'Clubs' field. If the field is empty — the rule works across the entire organization. Useful for testing mechanics on one club before rolling out to the network.
What happens if a client matches multiple rules?
All matching rules execute independently. If two rules award bonuses for the same event — the client receives both awards. Monitor condition overlaps.
How many rules can be created?
No limit. Typical configuration: 8–15 rules — bonus ladder on top-up (2–3 rules), rank system (3–5 assignment + 3–5 notification rules), bar cashback, welcome message, reactivation.
Where can I see the rule firing history?
Automation → open the rule → 'History' tab. Each firing: status (Completed / Skipped / Error), date, client. Status 'Skipped' means the event occurred but conditions weren't met — that's normal.
Can a rule be temporarily disabled without deleting it?
Yes. The 'Rule active' toggle — on/off. An inactive rule is saved with all settings and doesn't fire until re-enabled.
Will a rule fire for clients whose triggering event happened before the rule was created?
No. Rules only fire on future events. If you create a 'first session bonus' rule today — clients whose first session was earlier won't receive the bonus.
Will a notification reach a client without the mobile app?
No. Notifications only arrive through the IZI mobile app. Clients without the app or without active authorization won't receive the notification — this is not considered an error.
How do I test a rule before rolling it out to the whole database?
Enable the rule for one club only, perform a test operation (e.g., top up a test client's balance), open the rule history and check the status. Verified — expand to the whole network.