Every checkout, parcel and return sends a signal. Act on it the same day.
A checkout started and never paid. A cash-on-delivery order refused at the door for the second time. A product viewed three times this week and never bought. Most stores record these in the order system, the courier's callback and the storefront. Here each one starts a journey on the shopper's channel, asks your order system first, and stops the moment they buy.
The moments that matter.
Each one is a moment the platform can act on. Here is what it does.
- 01Session rule
A checkout started and never paid.
A session rule starts a journey when the visit ends: consent, a wait, a check that they have not bought, then one WhatsApp with a Finish order button.
- 02Your order system
A cash-on-delivery order placed and not confirmed before dispatch.
One WhatsApp with Confirm or Cancel. A tap goes to your order system, and the courier is booked only on a Confirm.
- 03Segment entry
A cash-on-delivery order refused at the door, for the second time.
The shopper enters a segment you defined, your order system is set to prepaid-only for them, and one message says so with a payment link.
- 04Stock confirmed first
The same product viewed three times this week, never bought.
Your system confirms the item is in stock in their size, and one message carries a link back to it. No coupon, no second nudge.
- 05Wait until the date
A thirty-day pack whose run-out date your order already holds.
The journey waits until the date your order holds, asks Reorder or Not now with one tap, and stops if they already did.
- 06Exchange, not refund
A return started, with the reason given.
Your system confirms the next size is in stock, and one WhatsApp offers the exchange before the refund is processed.
- 07One message
Two orders, then nothing for sixty days.
RFM moves them to At Risk on your windows, and one message from the store goes on the channel they answer. A discount only if your rule says so.
- 08Update becomes event
A parcel out for delivery today.
The update you already send becomes a delivery event, and the review request waits for the delivered event and sends once.
- 09Story if read
A category browsed every week and never bought from.
A Story on the category, on your domain or in the app, and one offer only if they read it to the end.
Signals from four places, one shopper record.
Your order system sends the order, the confirmation status, the courier's attempt, the refusal and the return by API. The storefront and the app send what shoppers view, add and leave, and the session itself. The shipment updates you already send become events. Every reply, read and tap comes back to the same record.
The shipment updates you send are already behaviour data.
A template declares which of its fields count as an event. The out-for-delivery update you send today becomes a delivery event with the order, the amount due and the status, with no SDK and no release. Behaviour history starts on day one, from the traffic you already send.
Catch the customer who is leaving quietly.
Nobody unsubscribes. The second order never comes, the app stays installed and unopened, the reorder date passes. RFM on your events and your windows moves them to At Risk before they are Lost, and entering the segment starts one journey. One message from the store, on the channel they answer, then silence. A discount only if your rule says so.
Offer the reorder the week the pack runs out.
A thirty-day pack delivered starts the journey. It waits until the run-out date your order holds, asks your system whether the item is in stock and whether they have already reordered, and only then sends one WhatsApp with Reorder or Not now. A tap places the order in your system. No calendar campaign, no reminder to someone who already bought.
Sell the next product on the signal, not the ad.
Running shoes delivered are a socks and insoles bundle ten days later. A third order of baby formula is the nappies category they have never bought. Coffee beans three months running are a subscription. A return for size is an exchange, not a refund. Each signal asks your system for stock and what they already bought, then sends one offer on the channel they answer. If they do not act, the journey ends.
Turn browsing into an order.
The same product viewed three times with nothing added to the cart, the size guide opened and closed. A session rule checks consent, asks your system whether the item is in stock in their size, and sends one message with a link back to the product. The journey stops when they add it, and there is no second nudge.
See where the store loses people.
The tracker and the SDK capture what shoppers do. Funnels show where product, cart, address and payment lose them, and a session journey shows the one visit that stalled, step by step, with the time spent on each. A session rule turns what did not happen into a trigger: added to cart with no checkout, a cash order with no confirmation reply. Ask the question in plain language and get the answer this session, not a ticket.
Stories you can measure.
A text says one thing and reports one delivery. A Story on your domain, in the app or inside an email walks the shopper through the new drop, the size guide or the category they have never bought, page by page, and reports views, completion, the drop between pages, poll answers and form submissions. Built in the builder, withdrawn in one action, no release.
Confirm the cash order before the courier is booked.
A cash-on-delivery order not confirmed within your window sends one WhatsApp with Confirm or Cancel. A tap writes the answer to your order system: the courier is booked, or the stock is released. No reply escalates to SMS, then a call with a keypad answer, in the order you set per message type, effective on save. The confirmation call your team dials today becomes the last step, not the first.
Ask your system before every step.
Before an offer, the journey asks your system whether the item is in stock. Before a reminder, whether the order is still open. After a tap, it writes the outcome back: confirmed, cancelled, reordered, exchanged. The journey never guesses stock, price or delivery date. xNotify carries the journey; it does not become the model.
Credit the install to the message that earned it.
Links resolve to the exact message that carried them. Android installs are matched deterministically, iOS as an estimate, and the report says which. Per-person referral links with a leaderboard turn refer-a-friend into a configuration, and every click is an event you can segment on.
Prove what happened, per order.
Every confirmation, update and reminder keeps one record: route, attempts, outcome, the reply, and what was written back to your order system. When the courier and the shopper disagree about the doorstep, the record settles it. Exportable, per message, per order.
A journey you could ship in the pilot.
COD order placed, not confirmed in your window → WhatsApp: Confirm / Cancel → confirm: your system books the courier → dispatch confirmation → cancel: stock released → no reply: SMS, then a call with a keypad answer → outcome to your order system.
Playbooks you can configure.
Ten journeys an online store can configure, from the cash order confirmed before the courier is booked to the customer who stopped ordering, each drawn as it runs in the builder.
- 01Confirm the cash order before the courier is booked.
- 02Recover the checkout that stalled, once.
- 03Ask for prepayment after the second refusal.
- 04Offer the reorder the week the pack runs out.
- 05Sell the bundle after the delivery, not with the ad.
- 06Open the category they browse and never buy.
- 07Turn the third monthly order into a subscription.
- 08Turn the return into an exchange.
- 09Nudge the product viewed three times, once the stock is checked.
- 10Reach the customer who stopped ordering, before they are Lost.
These are configurations you build in the pilot, not documented deployments.