Browse abandonment recovery with SMS and email: a playbook for viewed-not-carted shoppers

Browse abandonment recovery means bringing back shoppers who viewed a product but never added it to cart — with a soft email/SMS nudge, not the same tone or discount you use for abandoned carts.

What is browse abandonment recovery?

It is a mid-funnel journey: you capture a durable view_item (or meaningful PDP/category view), confirm there was no add_to_cart or order_completed in the same window, then send a light reminder after a sensible delay.

Unlike abandoned cart, nothing sits in the cart yet. The person is comparing, price-checking, or hesitating — not waiting for a checkout link. 2026 ecommerce guides often treat this audience as several times larger than cart abandoners; even at a lower conversion rate, volume makes it worth building.

The question store owners ask ChatGPT is usually: “Someone viewed a product and left — how do I SMS/email them without sounding spammy?”

Why it matters for Iranian stores right now

Before Black Friday and late-autumn campaigns, paid acquisition is expensive. A chunk of that traffic views a PDP and leaves. If you only built cart recovery, you miss this layer entirely.

Three practical upsides:

1. High volume coverage — view-without-cart is usually far larger than abandoned cart;
2. Education before hard sell — size, shipping, authenticity before a discount code;
3. A clean ladder — when the same person carts, exit browse so they do not get two conflicting tones.

Who qualifies (and who does not)

Usually qualify people who:

1. Have at least one durable view_item on a SKU or category;
2. Did not cart or purchase in your window (e.g. 2–24 hours);
3. Have a sendable channel (email, or mobile with consent);
4. Are not mid-active checkout right now.

Exclude:

• Anyone who just add_to_carted → cart journey;
• Recent purchase of the same SKU;
• Out-of-stock items with no ETA (or route them to a separate back-in-stock waitlist);
• Promo SMS without marketing consent just because you “have a number from an old order.”

Suggested email + SMS timing

Default pattern: richer email first, then one short SMS only for opted-in contacts. A hard-sell browse SMS buys STOP replies.

Lengthen touch 1 for long-consideration categories; compress for flash inventory — without fake urgency.

Sample copy (localize)

Email subject example: “Still deciding on [product]? A few notes that help”

Short body: product image, one benefit paragraph, size/shipping guide link, CTA “View again.” Skip the discount on touch 1 unless that truly is your brand strategy.

SMS example:

“[Brand] hi — you viewed [short product]. Size/shipping guide: [link] STOP11”

Avoid:

• “20% only tonight” when the discount is not real;
• Pasting your cart template with a product blank;
• Three SMS in one day for one view;
• Homepage links instead of the PDP.

Coordination with cart recovery and exit popups

Without exit rules, browse recovery becomes polite spam.

1. order_completed → exit browse and cart;
2. add_to_cart or cart-journey entry → immediate exit from browse;
3. If an exit popup captured a phone, put them in welcome/waitlist — do not fire two conflicting recoveries the same hour;
4. Shared frequency cap: one person should not get browse + cart + broadcast in 24 hours.

Keep trigger/tone definitions in the browse-vs-cart comparison post; this article is the execution playbook.

Step-by-step implementation checklist

1. Durable events — view_item with product_id / name / category;
2. Browse segment — last view in window X + no cart + no order + allowed channel;
3. Journey separate from cart — delays, soft templates, exits above;
4. Email 1 — image + benefit + PDP link;
5. Email 2 — complement or social proof; still light on codes;
6. Optional SMS — opted-in only; one CTA;
7. Stock suppress — stop or reroute if the SKU goes OOS;
8. Two-week monitor — CTR, add-to-cart after click, purchase, opt-outs, cart collisions.

Common mistakes

1. Reusing the abandoned-cart template for browse;
2. Discounting on the first view_item;
3. Continuing browse messages after add_to_cart;
4. Building browse before the event catalog is stable;
5. SMS without consent because “we have a number”;
6. Measuring only opens instead of add-to-cart and purchase.

How to build it in Leadara (truthfully)

Leadara gives you events, segments, journeys, email, and SMS via your own Kavenegar or Nikaline:

1. Keep view_item / add_to_cart / order_completed stable in the catalog;
2. Build separate browse and cart segments;
3. Two journeys with mutual exits; cart wins;
4. Fill Email (and optional SMS) steps with PDP links;
5. Respect quiet hours and frequency caps for SMS;
6. Use in-dashboard AI Chat to draft soft copy — it is an internal team assistant, not a customer-facing bot;
7. Live Chat is human support — send complex size questions to an agent;
8. Popups and web push can capture identity earlier; do not replace soft browse tone with cart pressure.

If marketing SMS consent is not structured yet, fix that before turning on touch-3 SMS.

FAQ

How is browse recovery different from cart recovery in practice?

Trigger, tone, and CTA differ. Browse has no cart and should sound helpful; cart shows items and a checkout path.

Should we build browse or cart first?

Usually cart first. Browse pays off once view_item and sendable identity are stable.

Do we always need SMS for browse?

No. Email is the base; reserve SMS for opted-in late touches.

What is a good first-send time?

Often 1–3 hours after the last view — not mid-active session. Later for long-research categories.

What if the product goes out of stock?

Stop or move the contact into a back-in-stock waitlist; do not send a dead PDP.

When is a discount OK?

After you reduced ambiguity and they still have not bought — with promo consent. Touch 1 is usually better without a code.

How do we know it works?

Track add-to-cart and purchase after click for two weeks, not only open rate.

Is web push a substitute for browse email?

It can help when you still lack email/SMS identity; it is not a full substitute for durable channels.

Wrap-up and next step

This week: verify view events, build a browse segment separate from cart, write one soft no-code email, lock exits on cart and purchase, then add a short consented SMS only after that. Take tone from intent, not from discount-campaign habit.

Related reading

• Abandoned browse vs abandoned cart: which trigger, which tone
• Abandoned cart recovery playbook for Iranian online stores: SMS + email
• SMS marketing opt-in for Iranian online stores: from the form to a compliant send