Cart & browse rescue
Recovery is the highest-ROI feature on the platform. Zubby watches every shopper session and drafts a personalized email, SMS, WhatsApp, or Telegram message when somebody leaves before completing an action you care about: filling a cart, viewing a product, viewing a category. This page covers the three recovery surfaces and how to wire them up.
The three recovery surfaces
| Surface | Trigger | Typical timing |
|---|---|---|
| Cart rescue | Shopper added items to cart but didn’t check out. | 15 min → 1 day → 3 days |
| Browse rescue | Shopper viewed 3+ products from a category without adding to cart. | 4 hours → 24 hours |
| Post-purchase / win-back | X days since last order, signal of churn risk. | 30 / 60 / 90 days |
Channels
What makes Zubby’s recovery different
- AI-drafted bodies — not a generic template with merge tags. The AI references the shopper’s actual conversation, their browse path, and the products they hesitated on.
- Smart offers — when needed, the AI proposes a time-limited discount within the bands you set. Bands are global caps (“never over 15%”) and per-product floors (margin protection).
- Per-shopper sequence pruning — if a shopper opens the first email and clicks through, we drop the rest of the sequence. If they ignore it, we escalate.
- Replies become conversations — when a shopper replies to a recovery email, the thread flows into the same inbox your team works.
Setting it up
From Dashboard → Recovery:
- Pick a starting campaign. Zubby ships with five templates: the Classic 3-Step for carts, the Single-Touch Browse for browse, and three winback variants by lifecycle stage.
- Set your From address and reply-to. We strongly recommend a real human address (e.g.
founder@acme.com) — reply rates double vs. a generichello@. - Configure discount bands. The AI never offers more than you allow. Default cap is 10%; some stores comfortably go to 20%. Setting cap to 0 means the AI never discounts.
- Confirm suppression rules — recent buyers, opted out, hard-bounced.
- Flip the toggle.
Attribution
Every recovery message includes signed UTM parameters scoped to the shopper and the message. When the shopper clicks through and orders, Zubby stitches the order to the message — attribution is exact, not last-click guess. We use a 14-day attribution window by default; configurable from Recovery → Settings.
Deliverability
Zubby signs every email with DKIM, sets a SPF include, and rotates IPs across our warmed sender pool. If you want to send from your own domain, configure SPF/DKIM under Recovery → Domain. Bounce and complaint feedback loops are processed automatically — hard bounces are suppressed for 90 days, complaints are permanently suppressed.
Don’t over-mail
Browse abandonment specifics
Browse rescue uses different signals from cart rescue: which categories the shopper hovered on, which products they zoomed into, and what conversations they had with the AI in the same session. The result is a message that references the actual interest, not a guessed one.
To enable browse rescue, the embedding worker has to be running and the page-view beacon needs to be installed. Both happen automatically on Shopify and WooCommerce installs.
Win-back specifics
Win-back targets profiles flagged as churn risk by the lifecycle engine. The AI considers their order history, favorite categories, and any unaddressed support issues from past conversations before drafting the message — so a win-back doesn’t feel like spam.
Next: journeys
Recovery sequences are powered by the journeys engine, which also supports multi-step drips, branching by behavior, and custom triggers beyond the built-in three. See Journeys & sequences.