Triggered Messages in IZI: Welcome, Churn Risk, Reactivation

Triggered Messages in IZI: Welcome, Churn Risk, Reactivation

Triggered messages are notifications that go out automatically at key moments in a client’s lifecycle. The three most important: greeting on first visit, churn risk signal after a long absence, and reactivation offer for those who disappeared. All three are assembled in IZI through automation rules.

Core automation logic → Automation in IZI: Overview.

Type 1 — Welcome: First Session

Why

The first 7 days after the first visit are the most critical retention window. The client isn’t yet accustomed to the club, doesn’t understand the loyalty program, doesn’t know about the app. A welcome notification closes this gap: informs that a bonus was awarded, explains what to do with it, and creates a sense of personal attention.

Rule: Welcome Bonus + Notification

Element	Setting
Name	”Welcome: first session”
Trigger event	Session ended
Condition	Session count = 1
Action 1	Award bonuses — fixed amount
Action 2	Send notification

Fixed bonus amount: aim for 10–20% of the average rate. If the average rate is 300, then 30–60 bonuses — noticeable but not economically damaging.

Welcome bonus expiry: 14–21 days. Long enough for the client to have a reason to return; not so long that they put it off.

Message Template

Field	Text
Title	”Welcome!”
Message	”Great to have you! Welcome bonuses are in your account — use them on your next session.”

Variant emphasizing the program:

Field	Text
Title	”You’re in the club!”
Message	”Every top-up earns bonuses. Play more — rise in the rankings. Bonuses are in your account.”

Additional: Notification on Second Visit

Client came back — lock in the second visit. Event: “Session ended,” condition: “Session count = 2.”

Field	Text
Title	”Welcome back!”
Message	”Second visit — you’re already a regular. Top up your balance; bonuses grow with top-up amount.”

This notification has no bonus — just a program reminder.

Type 2 — Churn Risk: 14 Days Without Visit

Why

A client who hasn’t visited in 14 days is starting to “cool off.” This is not yet a loss: the client still remembers the club and can return with the right incentive. After 30 days it’s harder; after 60 — very hard. Intervention at day 14 is the cheapest return point.

Rule

The event for this scenario depends on available triggers in your IZI version. Check the trigger event catalog — if there’s an event “client hasn’t returned for N days,” use it directly.

If no such event exists — the scenario is implemented via external segmentation: regularly (weekly) update the “Dormant 14+” group manually or via export, and run the rule on adding to that group.

Element	Setting
Name	”Churn risk: 14 days without visit”
Trigger event	Group assigned (group “Dormant 14+“)
Condition	—
Action 1	Award bonuses — small fixed amount
Action 2	Send notification

Day-14 bonus: small with a short expiry. This isn’t a “bribe” — it’s a reminder that the client is remembered and expected.

Message Template

Field	Text
Title	”We miss you!”
Message	”It’s been a while. Bonuses waiting — come play.”

Variant with urgency emphasis:

Field	Text
Title	”Bonuses waiting for you”
Message	”Return before end of week — bonuses with short expiry in your account.”

Bonus expiry: 5–7 days. Creates urgency without pressure.

Type 3 — Reactivation: 30 Days Without Visit

Why

30 days of absence — the client has practically left. But there’s still a chance to bring them back: they still have memory of the club and possibly unfinished gaming progress. The reactivation offer must be noticeably stronger than the day-14 signal.

Rule

Element	Setting
Name	”Reactivation: 30 days without visit”
Trigger event	Group assigned (group “Dormant 30+“)
Condition	—
Action 1	Award bonuses — larger amount, 7-day expiry
Action 2	Send notification

The reactivation bonus must be noticeably larger than the day-14 one — otherwise there’s no point in having two levels. If you gave 50 bonuses on day 14, give 150–200 on day 30.

Message Template

Field	Text
Title	”Long time no see”
Message	”A month without you — that won’t do. Come back: big bonus waiting, valid 7 days.”

Neutral variant:

Field	Text
Title	”Come back!”
Message	”A special return bonus for you. Valid until end of week.”

Full Client Lifecycle Table

Stage	Rule	Event	Text
First visit	Welcome	1st session	”Welcome, bonuses credited”
Second visit	Lock-in	2nd session	”Welcome back, you’re already a regular”
First rank	Rank notification	Bronze group assigned	”Bronze rank — you’re in the program”
Next rank	Rank notification	Silver/Gold group assigned	”New level reached”
14 days without visit	Churn risk	Added to “Dormant 14+” group	”Miss you, bonuses waiting”
30 days without visit	Reactivation	Added to “Dormant 30+” group	”Big return bonus”

General Principles

One moment — one notification. If a client receives a welcome message, session cashback, and rank notification simultaneously — that’s overload. Space events out in time or combine into one message where possible.

Bonus expiry = urgency tool. Long expiry (30+ days) gives flexibility but removes the incentive to return soon. Short expiry (3–5 days) — aggressive. The 7–14 day range works for most scenarios.

Tone by situation: welcome — warm and engaging. Churn risk — neutral, no pressure. Reactivation — with a tangible offer, no reproach.

No more than two reactivation messages. Day 14 and day 30 — sufficient. After the second non-return — notifications won’t help; they just annoy.

Diagnostics

Problem	Cause	Solution
Welcome doesn’t fire	visit_count = 1 condition not met	Check: client may have had a previous account; visit_count may already be > 1
Client received welcome twice	Account merge reset the counter	Normal situation with manual profile merging
Reactivation bonus not awarded	”Dormant 30+” group not updated	Verify the group is currently populated

See Also

• Anti-Churn Automation: Full Playbook
• Push Notifications: Campaign Setup
• Segmented Broadcasts
• Automation Best Practices
• Creating Your First Automation Rule