Loyalty, CRM & Marketing
Points, tiers and referrals, customer segments, and message journeys, all run on your own customer and order data.
Loyalty, CRM and marketing share one customer record. Customers earn points on their orders, move through tiers, refer friends and redeem rewards. You build segments from customer and order fields, and use them in journeys that send SMS, WhatsApp or email through the provider you already use. The sections below say what each part does today and where its limits are.
What Loyalty, CRM & Marketing does
7 capabilities, each described as it works today.
Points, tiers and rewards
Customers earn points on orders, move through tiers and redeem rewards, with bonus campaigns for promotions.
A purchase rule sets how many points a customer earns per 100 of order value. The earn is multiplied by the customer's tier and by any active bonus campaign, and the result is written to a ledger. The rules also support points for reviews, sign-ups, referrals, shares, birthdays and streaks. Tiers, a rewards catalog, missions and badges sit on top. A return reverses the points earned on that order, in full. Points can expire, and a liability view shows what you owe in points.
- Points per 100 of order value, with a multiplier for each tier
- Time-boxed bonus campaigns with their own multiplier
- Other earn actions: reviews, sign-ups, referrals, shares, birthdays and streaks
- Tiers, rewards catalog, missions and badges
- A return reverses the whole earn for that order
- Point expiry and a liability view
Referrals and affiliates
Reward customers who refer friends, and pay affiliates who bring in sales.
Referrals reward both sides: the referrer gets a reward and the new customer gets a first-order benefit. A separate earn programme supports affiliates with tiers, attribution windows, conversion tracking and payout batches, with payouts by UPI, bank transfer or credit and tax deducted at source calculated on each batch. The affiliate programme runs separately inside each business, not as a shared pool across brands.
- Two-sided referral rewards
- Affiliate tiers, attribution windows and conversion tracking
- Payout batches by UPI, bank transfer or credit, with tax deducted at source
- Runs inside each business, not as a cross-brand pool
Customer segments
Build segments from customer and order fields with nested AND and OR rules, and preview the size before you save.
A segment is a set of rules joined by AND and OR, with groups nested inside groups. Rules use customer fields: email, name, phone, city, country, sign-up date, order count, lifetime value, last order date, points, lifetime points and tier. The segment is evaluated against your live data when you ask for it, so it is as current as the data, but it is not a continuously updated stream. It does not yet use browsing session, return or support-ticket events.
- Nested AND/OR groups
- Fields: order count, lifetime value, last order date, points, tier, city, country and more
- Evaluated on request against live data
- Count and sample preview
- Session, return and support-ticket events are not available as fields yet
Journeys
AutomationA visual canvas for message flows with triggers, waits, conditions and actions.
Journeys are built on a canvas from trigger, condition, action, wait and end nodes. A condition can split customers into branches, including an A/B split. Actions send an SMS, WhatsApp or email message or move the customer to a new journey stage. Steps for adding a tag, adding to a segment or applying a discount are recorded as having run, but they do not yet change the customer or create a discount. Each customer's progress through a journey is logged node by node. Journeys are processed on a 10-minute cycle, so a message goes out within about that window of its trigger rather than instantly. There is no dry-run mode.
- Trigger, condition, action, wait and end nodes
- Condition branches, including A/B splits
- Actions that send a message or update the customer's journey stage
- Tag, segment and discount steps are only recorded for now
- A per-node run log for each customer
- Processed on a 10-minute cycle
Messages through your own providers
Send SMS, WhatsApp and email through the providers you already use.
Journey actions send through the provider configured for your business. SMS goes through Exotel or MSG91, WhatsApp through MSG91, Gupshup or Interakt, and email through SendGrid, Brevo or MSG91. A Mailgrid email client is also available. Push notifications are not part of the journey sender today.
- SMS: Exotel and MSG91
- WhatsApp: MSG91, Gupshup and Interakt
- Email: SendGrid, Brevo and MSG91
- Push notifications are not sent from journeys
Back-in-stock alerts
Tell customers when a product they wanted is available again.
A scheduled job checks products that customers asked to be told about and sends the alert when stock returns. It runs alongside the other lifecycle messages.
- Customers subscribe to a product they want
- A scheduled job sends the alert when stock returns
Attribution
Credit orders to marketing touches with first-touch, last-touch, linear, time-decay or position-based models.
Orders can be attributed to the marketing touches that led to them using five rule-based models: first touch, last touch, linear, time decay and position based. These are standard multi-touch models, not causal measurements, so use them to compare channels rather than to prove what caused a sale.
- Five rule-based multi-touch models
- Compare channels under different models
- Not a causal or incrementality measurement
QuantumOS Dispatch
Insights for commerce operators
Operator stories, platform deep dives and notes on what ships.
We'll send the QuantumOS Dispatch by email. Unsubscribe any time. See our privacy notice.