| Function | Description | Placement | Examples / Use Cases |
| Wait Event | Starts a journey until a action happens/triggers. | Usually at the start, but can also be placed in the middle to wait for a next action. | Customer signs up, customer makes purchase > RM30 |
| Automated Event | Starts the journey based on a system-driven (daemon) check. | Recommended only at the beginning of a journey. | Detect birthday, detect inactive user |
1. Wait Events

What it is:
The starting point of a customer journey, based on real customer actions captured by the system.
How it works:
You define what “event” triggers the journey to begin — for example, a customer making a purchase above a certain amount.
Example Use Cases:
- Customer signs up for membership.
- Customer spends over RM30 in a single purchase.
- Customer redeems a voucher.
Why it matters:
Wait Events let you design journeys that respond directly to what your customers actually do, creating more relevant and timely engagement.
Wait Events List
Wait Event | Description |
Customer Signup in Loyalty | User successfully sign up as loyalty member (app/lite) |
Apply Voucher Redeem Code In Loyalty App | User apply redeem code in loyalty to get voucher |
Top Up Credit In Loyalty App | User topup credit in loyalty app |
Login In Loyalty App | Login into loyalty account |
Submit Feedback Form | Submit loyalty feedback |
Upgrade Member Type Based On Lifetime Points | User got upgraded to certain Tier when they hit the lifetime points threshold set in backend. |
Complete Sales | Customer purchase/make sales |
Customer Sign Up In Xilnex Platform | Customer creation via POS/Xilnex Classic |
Complete Loyalty Achievement | Customer/user complete stamps/achievements |
Purchase Voucher Via Catalogue | Customer/User redeem voucher from voucher catalogue |
Add Xcard Into Account In Loyalty App | When card added to user/customer/s account. |
2. Automated Events
What it is:
These are system-triggered events that must be placed at the beginning of a customer journey. They automatically start the flow based on predefined customer data conditions and do not rely on real-time user actions.
| Automated Event | Description |
| Birthday Trigger | Automatically triggers the journey on a member’s birthday. You can configure the journey to start on the exact date, or during birthday month |
| Dormant Users Trigger (Reactivation) | Starts a journey for inactive members who have not made any purchases for a defined number of days. Ideal for win-back or “We Miss You” campaigns. |
A journey that starts automatically based on system-driven checks (daemon processes) — instead of waiting for a live action.
How it works:
The system runs periodic checks (e.g., daily) and triggers journeys when conditions are met.
Example Use Cases:
- Detect if today is a customer’s birthday and send them a birthday voucher.
- Identify customers who have been inactive for the last 30 days and send them a reactivation offer.
Why it matters:
Automated Events help you proactively engage customers even if they’re not currently interacting with your business.
Important difference
- Wait Event: Flexible — can be used to start a journey, or later in the journey to wait for another action before continuing.
- Automated Event: Designed to only start journeys (e.g., daily birthday scan).
Placing Automated Events in the middle of a journey is not recommended and can cause unexpected behavior.
Action Events
3. Trigger Actions
What it is:
The “response” part of your journey — actions automatically triggered when conditions in the journey are met.
How it works:
When a customer reaches this step in the journey, the system performs a predefined action.
Trigger Actions in CX Builder
| Trigger Action | Description |
| Send SMS | Sends an SMS to the customer (Make sure you alreaady have the SMS account setup) |
| Send Email | Sends an email to the customer's registered email address. |
| Send Push Notification | Sends a push notification to the customer’s app. (Only applicable for Loyalty App) |
| Send Email to Specified Email | Sends an email to a custom email address (not necessarily the customer’s). Normally used for internal team alert |
| Tag Customer | Adds one or more tags to the customer profile. |
| Issue Voucher | Assigns a selected voucher to the customer’s account. |
| Issue Accumulate Points | Rewards a specific amount of points to the customer. |
| Issue Lifetime Points | Adds lifetime (tiering) points to the customer — used for tier level calculation, not spendable. Backend setup required. |
| Increase Journey Counter | Increments a journey counter value for the customer, useful for tracking repeated actions. |
| Top Up XCard Credit | Adds XCard credits to the customer’s XCard balance. |
| Deduct XCard Credit | Deducts XCard credits from the customer’s XCard balance. |
| Flush Accumulated Points | Clears all accumulated (but unused) points of the customer. |
| Update Customer Active Status | Marks the customer as active or inactive. |
| Update XCard Status | Sets the XCard status (e.g. Active, Expired, Suspended). |
Example Use Cases:
- Issue a welcome voucher after signup.
- Grant loyalty points for a specific behavior.
- Send an SMS, email, or push notification thanking the customer.
Why it matters:
This is where the engagement happens — automatically rewarding, informing, or reminding customers, leading to higher satisfaction and retention.
Journey Counter
A Journey Counter in CX Builder records how many times an action happens, either:
- Per Customer (Individual Count): Tracks how many times that specific customer has triggered the event in the journey.
- Overall (Share Count): Tracks the total number of times all customers combined have triggered the event in the journey.
The system stores this count, and you can set a condition to check the number before deciding the next step.
Example:
- Per Customer: If a single customer completes 5 purchases within 15 days → Send RM20 voucher.
- Overall: If 1,000 redemptions are reached for a campaign → Stop sending vouchers.
Key points:
- Can track individual or total journey actions.
- Can be updated using the Increase Journey Counter action.
- Useful for reward thresholds, campaign limits, or milestone tracking.
Conditional Based Events
A Conditions Event in CX Builder is a powerful way to branch your customer journey into different paths based on data, behavior, or logic.
It helps personalize the journey and control who receives which offers or messages.
4. Conditions Event
CX Builder supports several types of conditions you can use to design smarter journeys:
| Condition Type | What it checks | Example Use Case |
| Journey Counter | Number of times the customer did something within this journey. | After a customer makes 5 purchases in the journey, send a special reward. |
| Customer Profile | Customer attributes like: – Customer type – Current points balance – Created outlet | Send different vouchers to VIP vs. Regular members; give extra offer if points balance > 500. |
| Days of the Week | What day it is when the journey reaches this step (Monday, Tuesday, etc). | Send special weekend-only promo if today is Saturday or Sunday. |
| Random Decision by Percentage | Randomly splits customers by chance, based on set percentages. | Run an A/B test: 70% get offer A, 30% get offer B. |
How it works in practice
After starting the journey (with Wait Event or Automated Event), you can insert a Conditions Event to decide what happens next.
For example:
- Customer signs up →
Conditions Event: Check if customer type = VIP
- If yes → Issue RM20 voucher
- If no → Issue RM10 voucher
Or:
- Automated Event: Detect inactive customer →Random Decision: 50% get SMS reminder, 50% get email reminder
Why this matters
- Helps target the right customers with the right rewards.
- Allows real personalization, making campaigns more effective.
- Supports business strategies like segmentation, testing, and exclusive offers.
5. Wait Delays

What it is:
A step that adds a pause in the journey before the next action.
How it works:
You set a delay (e.g., hours or days) after an event before moving to the next step.
Example Use Cases:
- Send a follow-up email 3 days after a purchase.
- Send a reminder message 7 days after customer signup if they haven’t redeemed their voucher.
Why it matters:
Wait Delays allow you to space out communication, making your engagement feel natural and not overwhelming.
How It All Comes Together
Using these building blocks, a business can create complex, fully automated customer journeys.
For example:
Customer purchase, tag customer, send rewards and notify customer
Wait Event: Complete sales- Customer makes purchase on certain product →Trigger Action: Tag customer→ Wait Delay of 3 days → Trigger Action: Send thank-you email→Trigger Action: issues a loyalty voucher→ End
All this can be done visually inside CX Builder — without writing code.