A browse abandonment flow messages identified visitors who viewed products but never added one to a cart — and because that intent is much weaker than a cart, the omnichannel version uses fewer and gentler channels, not more. The working recipe: one email a few hours after the browsing session, one web push reminder a […]
Category Archives: Omnichannel Automation
To attribute sales across email, SMS, and push, you need three things: one attribution model applied the same way to every channel, a rule that says each order counts once no matter how many messages touched it, and a regular sanity check against your store’s actual revenue. Most stores have none of these. They read […]
To A/B test a channel sequence, split one automation into two paths that differ in exactly one structural way — email then SMS versus SMS then email, or push added versus push removed — and judge the winner on profit per recipient after message costs, not on opens or clicks. Run the split inside the […]
An omnichannel win-back flow works as an escalation ladder: start on email, the cheapest and least intrusive channel, and only climb to push and then SMS for customers whose value justifies the cost — because a lapsed customer is, almost by definition, someone your emails stopped reaching. Trigger it when a customer passes your store’s […]
An omnichannel abandoned cart flow runs email, web push, and SMS in sequence, not in parallel. Email does the heavy lifting: it fires about an hour after abandonment and again the next day. Web push slots in between as a free, low-pressure nudge for people who never opened the first email. SMS goes last, and […]