Browse Abandonment and Post-Purchase Flows

Browse abandonment mail must be weaker than cart mail, because the signal is weaker: a product view is curiosity, not intent, so the email should be a light, useful continuation - the thing viewed, the question it usually raises answered, an easy way back - sent rarely, capped hard, and never pretending the visitor nearly bought. Post-purchase mail must serve before it sells: delivery and use first, care and success next, and any further offer only after the purchase has had time to prove itself. Both flows convert by calibration. The same intensity that suits a cart insults a browser, and a sales pitch inside a delivery week insults a buyer.

Send browse mail only where the browsing was substantial - a return visit to the same product, a category explored in depth, an item saved or searched repeatedly - and only to subscribers whose capture promise plausibly covers it, which the capture discipline in capture points beyond the popup decides. One email, not a sequence, is the default shape: here is the thing you were looking at, here is the detail people usually want next, here is the route back. Category-level browsing earns category-level help (the guide, the comparison) rather than a product ambush. When in doubt, do not send; an unsent browse email costs nothing, while an over-eager one costs the subscription.

The browse email that earns its open behaves like a good assistant who noticed what you were considering: it shows the viewed item accurately, adds the one piece of information the product page data says visitors seek (fit, compatibility, delivery), and offers the neighbouring comparison honestly, including when a different product suits better. What it must not do: manufacture urgency around a casual look, imply a price movement that did not happen, or retell the visit back creepily in surveillance language. The line is between being remembered helpfully and being tracked obviously, and small businesses stay on the right side of it by writing as a person, not as a system.

The days after purchase belong to the purchase: confirmation in the inbox the buyer will search later, delivery information that arrives before anxiety does, and - timed to actual use - the guidance that makes the product succeed: setup, care, the common mistake, the answer to the week-two question. These emails are opened at rates campaigns envy, because they are useful, and they build the only asset the next sale needs: a buyer whose first purchase went well. Review requests belong late in this sequence, honestly framed and easy to decline, following the honesty rules for reviews the trust bench sets out.

When a further offer is right - replenishment timed to real consumption, the accessory that completes the bought item, the next step in a sequence the buyer began - it should arrive as a continuation written from the purchase, not as a campaign that happens to know their name. The segmentation guide, segmentation for small lists, covers aiming by what was bought; the restraint rule here is timing: never before delivery, never alongside a service problem, and always suppressed while any support conversation is open. A buyer courted while their issue is unresolved learns the business sells better than it serves, a lesson that outlasts the discount that taught it.

Browse, cart, welcome and post-purchase flows can all plausibly fire at one person in one week - the subscriber who browsed, bought, and still has a cart open somewhere. The programme needs the roster discipline of the parent guide, email capture and flows: post-purchase service outranks everything, an active cart sequence outranks browse, welcome yields to both, and a per-person weekly cap trims the rest. Draw the priority order once, set it in the platform, and audit it whenever a new flow is added, because flow collisions are invisible in each flow's own dashboard and obvious only in the subscriber's inbox.

These two flows live or die on relationship measures more than immediate orders: browse mail on its unsubscribe rate and its assisted return visits, post-purchase mail on repeat purchase over a season and on support outcomes, both read under the rules in email metrics that matter. A browse flow with modest clicks and near-zero unsubscribes is a quiet asset; one with clicks bought by complaints is a liability wearing a good chart. Review both flows twice a year by reading them as their recipients - the curious browser and the new buyer - and cut anything whose job you cannot state in their words.