Skip to content
E-commerce · Playbook

The e-commerce playbook. Built in the builder, decided by your order system.

Ten journeys, each drawn below as it runs. The decision comes from your order system or criteria you set; the journey carries it. Aims are targets to agree in the pilot, not results.

PLAYBOOKS · 01

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 books the courier or releases the stock in your order system, and silence escalates to SMS, then a call with a keypad answer.

Decides
your confirmation window and your order system.
Aim
fewer parcels sent to a doorstep that will refuse them.
Built in the journey builder
Confirm the cash order before the courier is bookedE-COMMERCEOne WhatsApp with two buttons; the courier is booked only on a Confirm.
E-commerce
PLAYBOOKS · 02

Recover the checkout that stalled, once.

A session that reaches checkout and ends unpaid starts a consent-checked journey that waits an hour, checks for a purchase first, sends one WhatsApp with a Finish order button, and falls back to one SMS.

Decides
a session rule you set, and your cap per shopper.
Aim
recovered checkouts, once per shopper.
Built in the journey builder
Recover a stalled checkoutRETAILStarts when the visit ends, stops itself if they already bought.
E-commerce
PLAYBOOKS · 03

Ask for prepayment after the second refusal.

A shopper who refused cash on delivery twice in ninety days enters a segment; your order system is set to prepaid-only for them, one message says so with a payment link, and a prepaid order within thirty days restores the option.

Decides
your refusal window and your payment policy.
Aim
the return-to-origin bill cut without losing the honest shopper.
Built in the journey builder
Ask for prepayment after the second refusalE-COMMERCEA segment on your rule, a flag in your order system, one message, and the option restored when they pay.
E-commerce
PLAYBOOKS · 04

Offer the reorder the week the pack runs out.

A thirty-day pack delivered starts a wait until the run-out date your order holds; your system confirms stock and that they have not reordered, then one WhatsApp asks Reorder or Not now, and a tap places the order.

Decides
the run-out date your order holds and your stock.
Aim
repeat orders before the shopper searches elsewhere.
Built in the journey builder
Offer the reorder the week the pack runs outE-COMMERCEWaits until the date your order holds; your system confirms stock before anyone is asked.
E-commerce
PLAYBOOKS · 05

Sell the bundle after the delivery, not with the ad.

Ten days after running shoes are delivered, your system confirms the bundle is in stock and not already bought, and one WhatsApp offers it with a tap that creates the order.

Decides
your product pairs and your stock.
Aim
a higher order value from shoppers who already trust the delivery.
Built in the journey builder
Sell the bundle after the delivery, not with the adE-COMMERCEA delivered order, a wait, a stock check with your system, one offer, one tap to order.
E-commerce
PLAYBOOKS · 06

Open the category they browse and never buy.

A shopper who browses a category every week and has never ordered from it gets one Story on it, on your domain or in the app, and one offer only if they read it to the end.

Decides
your segment definition.
Aim
a second category per customer.
Built in the journey builder
Open the category they browse and never buyE-COMMERCEA consent check, one Story, then an offer only if they read it to the end.
E-commerce
PLAYBOOKS · 07

Turn the third monthly order into a subscription.

A third order of the same item in ninety days asks your system whether a subscription is already in place, then sends one WhatsApp with Subscribe monthly or Not now; a tap creates the subscription in your system.

Decides
your subscription rules.
Aim
predictable repeat revenue without a monthly reminder.
Built in the journey builder
Turn the third monthly order into a subscriptionE-COMMERCEYour system says whether a subscription already exists before anyone is offered one.
E-commerce
PLAYBOOKS · 08

Turn the return into an exchange.

A return started for size asks your system whether the next size is in stock, then offers Exchange or Refund on WhatsApp; a tap books the exchange pickup and delivery, or processes the refund.

Decides
your stock and your returns policy.
Aim
returns kept as sales.
Built in the journey builder
Turn the return into an exchangeE-COMMERCEYour system checks the next size before the exchange is offered; the refund stays one tap away.
E-commerce
PLAYBOOKS · 09

Nudge the product viewed three times, once the stock is checked.

A session rule for the same product viewed three times with nothing added to the cart checks consent and stock, checks they have not added it since, and sends one WhatsApp with a link back to the product. No second nudge.

Decides
a session rule you set and your stock.
Aim
browse to buy, without a coupon.
Built in the journey builder
Nudge the product viewed three times, once the stock is checkedE-COMMERCEConsent, then stock from your system, then a check they have not added it since. One message.
E-commerce
PLAYBOOKS · 10

Reach the customer who stopped ordering, before they are Lost.

Two orders and none in sixty days moves the shopper to At Risk on your RFM windows; one message from the store, not a discount, goes on the channel they answer; a reply reaches your support desk, and silence waits and checks again.

Decides
your RFM windows and your win-back rule.
Aim
the second order that never came, caught before the customer is gone.
Built in the journey builder
Reach the customer who stopped ordering, before they are LostE-COMMERCEOne message from the store, not a discount; a reply reaches a person, silence is checked again.
E-commerce

Where a step says your system decides, the journey calls your system and branches on its answer. xNotify carries the journey; it does not become the model.

The pilot

One use case. Six to eight weeks. A number you agreed first.

Book a Demo