Every receipt and every visit is a signal. Act on it before the next one.
A member who has not visited in forty days. A basket that shrank three trips running. A category they bought for the first time yesterday. Most retailers record all three at the till and in the app. Here each one starts a journey on the member's channel, checks your stock and your loyalty system first, and stops the moment they are back in the store.
The moments that matter.
Each one is a moment the platform can act on. Here is what it does.
- 01RFM · At Risk
A member who has not visited in forty days.
RFM on your own visit cycle moves them into At Risk; one offer on their channel, then silence.
- 02Segment entry
A basket that has shrunk three trips running.
A segment on the receipt events catches the shrink, your system names the categories that fell away, and one message offers the private label in those lines.
- 03Your stock decides
A receipt with a category they have never bought before.
Your stock system confirms the adjacent line is in their store, and one WhatsApp offers it with a tap to reserve.
- 04Your loyalty system
A member forty points short of the next tier, with the quarter ending.
Your loyalty system confirms the gap and the date, and one message says what gets them over. The journey stops when they cross.
- 05Session rule
A product page opened three times, size picked, no order.
A session rule fires when the visit ends, checks stock at their store, and sends one message with a tap to finish or reserve.
- 06Story · RSVP
A store event this weekend, in the city where they shop.
A Story with the invitation and an RSVP poll goes to the members of that store; a yes is written to your system and reminded the day before.
- 07Smart link · QR
A shelf QR scanned by someone without the app.
A smart link opens the product in the app if installed and the store page if not; the install is credited, matched on Android and estimated on iOS.
- 08Wait until date
Points that expire at month end, none redeemed.
The journey waits until the date your loyalty system holds, reminds once with what they usually buy, and stops when they redeem.
- 09One offer
The private label tried once and not since.
One buying cycle later, a check of the receipts, a stock check, and one offer at member price on the line they tried.
Signals from four places, one member record.
Your tills and your loyalty system send the receipt, the categories on it, the points, the tier and the store by API. The app and the site send what members look at, what they pick, and the session itself. The points and order messages you already send become events. Every read, tap, poll answer and consent change comes back to the same record.
The messages you already send are behaviour data.
A template declares which of its fields count as an event. The points message you send after every visit becomes a visit event with the store, the points and the balance, with no SDK and no release. Visit history starts on day one, from the traffic you already send.
Catch the member who is drifting before the lapse.
Nobody cancels a loyalty card. The visits stretch out, the basket shrinks, the points balance grows while nothing is redeemed. RFM on your own visit cycle and your own receipt values catches the first two; a segment on redemption catches the third. Entering a segment starts a journey. One offer, on their channel, then silence.
Offer the adjacent category the day the receipt shows a new one.
A receipt with a category the member has never bought starts the journey. It asks your stock system whether the adjacent line is in their store, and only then sends one WhatsApp with Reserve or Not now. A tap goes to your system to hold it. No blast, no offer for something the store does not have.
Sell the next thing on the receipt, not the calendar.
A first purchase in home is the adjacent line. A basket that shrank in fresh food is the private label in the lines that fell away. Forty points short of the next tier is the tier, with what gets them over. Two formal shirts in a month is the fitting evening at their store. Each signal checks your stock and your loyalty system first, then sends one offer on the channel they answer. If they do not act, the journey ends. Nobody gets the same offer twice.
Turn a size picked into an order.
The product page opened three times, the size picked, the visit ended with no order. A session rule fires when the visit ends, asks your system whether that size is in their store, and sends one message with a tap to finish the order or reserve it to try on. Consent checked first, and the journey stops when the order lands.
See where the app and the site lose people.
The SDK and the web tracker capture what members do. Funnels show where sign-up, the first order and redemption stop. A session rule turns what did not happen into a trigger: a product page opened and no order, a points balance viewed and nothing redeemed. Ask the question in plain language and get the answer this session, not a ticket.
Launch the drop with Stories you can measure.
A text about the new collection reports one delivery. A Story in your app, on your own domain or inside an email walks the member through the drop page by page, asks which line they want in a poll, and reports views, completion, the drop between pages and every answer. The drop, the store event, the tier explainer: built in the builder, live the same afternoon, withdrawn in one action, no release.
From the shelf to the app, credited to the shelf.
A QR on the shelf, the receipt or the bag is a smart link. It opens the product in the app if installed and the store page if not, and the install that follows is credited to the campaign that printed it: matched on Android, estimated on iOS, and the report says which.
One message a week, at their hour, on the channel they answer.
Every member carries a best time to send, a best channel by time of day and an engagement score that falls when you over-message. A journey checks the score before it sends, a campaign lands at each member's local hour, and the member who stopped opening gets fewer messages, not more.
Consent that travels with the member.
WhatsApp, SMS, push and email each carry their own consent, with the history of every change and where it came from: the till, the app, a reply. A journey checks it before the first message. An opt-out on one channel never silences the order and collection messages on another.
A journey you could ship in the pilot.
First-time category on a receipt (your tills) → in stock at their store? your stock system → WhatsApp: Reserve / Not now → tap: your system reserves it → confirmation → no tap: silence.
Playbooks you can configure.
Ten journeys a retailer can configure, from the adjacent category on yesterday's receipt to the question after the visit, each drawn as it runs in the builder.
- 01Offer the adjacent category the day the receipt shows a new one.
- 02Bring the member back before the lapse.
- 03Win back the lines that fell out of the basket.
- 04Get the member over the tier line before the quarter ends.
- 05Turn a size picked into an order.
- 06Remind before the points expire, not after.
- 07Fill the store event with the members who shop there.
- 08Take the shopper from the shelf into the app.
- 09Turn one private-label trial into a habit.
- 10Ask after the visit and route the answer to the store.
These are configurations you build in the pilot, not documented deployments.