ข้ามไปยังเนื้อหา

IZI Automation — Rule System Overview

Опубликовано: · Обновлено: (6 дней назад)· IZI Team

เนื้อหานี้ยังไม่มีในภาษาของคุณ

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.

In the sidebar, switch to the organization → Marketing → Automation. The Rules list page shows all rules with their clubs, a short summary and an on/off switch; rules can be sorted into folders. The Run history page is the log of rule runs.

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.

Every rule has three components:

1. Trigger event — what must happen for the rule to fire. One rule — one event. Events are of two types: Client action (session, top-up, purchase, refund, groups) and Date (birthday, N days without a visit, N days without spending bonuses). 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: add or debit 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.

When a client event happens (a session ended, a balance was topped up, a birthday came), IZI:

  1. Finds all enabled rules with this event whose active period includes the current date and whose clubs include the club
  2. Checks each rule’s conditions for this client
  3. For rules where conditions are met, executes the actions
  4. Records the result in the run history

One event runs a rule once. Rules do not fire for staff service accounts.

A run with status Skipped means the event occurred but conditions were not met — this is normal, not an error.

A rule is created at the organization level, but can be restricted to specific clubs:

SettingWhat happens
Clubs field is emptyRule runs in all clubs of the organization
Specific clubs selectedRule 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.

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
  • Purchase cashback — a percentage of the money spent on tariffs, products or combos credited to the bonus account
  • Birthday bonus — a gift on the client’s birthday
  • Bonus expiration — debiting bonuses the client has not spent for a long time
  • Win-back — an invitation to clients who have not come for N days
  • 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 together: if two rules credit bonuses for one event, the client gets both credits.

Step-by-step walkthrough for creating and configuring a rule → Create an automation rule.

If an expected action did not happen:

  1. Check that the rule is enabled and today is within its Active period
  2. Open the run history — look at the status for the specific client
  3. Status Skipped — conditions were not met; open the run and compare Variables with the conditions
  4. Status Failed — problem in an action; open the run and read the reason. Rule failures also appear in the Notifications bell in the club CRM header

คำถามที่พบบ่อย

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, an order is paid or a birthday comes, 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. A rule has one event, so different events need separate rules. To keep the list tidy, sort rules into folders.

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 organization menu open Marketing → Automation → Run history and pick the rule in the filter. Each run is listed with its status: «Succeeded», «Skipped» or «Failed».

Can a rule be temporarily disabled without deleting it?

Yes. The switch in the rules list or «Rule is active» in the form turns it on or off. A disabled rule keeps all its settings and does not run. For dated promotions set the «Active period» — outside it the rule does not fire.

About IZI