Recovery emails the model actually writes

Each email is generated per-shopper from a recovery-tuned prompt grounded in the products they abandoned, the policies they may care about (shipping, returns, sizing), and your brand voice. The subject line, opening, body, and PS are all generated. Product cards inject as structured blocks pulled from your live catalog so the AI never invents prices, stock or shipping windows. This is the difference between a templated abandoned cart email with 8% recovery and an AI-written one closer to 19% — the prose is per-shopper, not per-blast.

Yes. Recovery email brand overrides cover logo, primary and accent colors, footer text, sender name, and reply-to address. Combine with brand voice settings (tone, formality, emoji policy, sign-off, house phrases) and the output reads like it was written by someone who works at your store. White-label brand overrides also let agencies push consistent styling across multiple client stores with one click.

By default, Zubby sends transactional recovery email via Resend with managed DKIM and SPF. You can also route through Mailchimp (transactional or contact-list sync), Klaviyo (flow injection), HubSpot (marketing email API), or your own SMTP. The choice is per-store and can be changed without losing attribution or send history.

A configurable cadence: a second email a day later with a different angle, an optional third with a small incentive if you've enabled smart offers. You can stop the cadence the moment the cart converts — the journey-execution worker checks every minute, so timing is tight enough to avoid awkward 'still thinking about it?' emails after the order has shipped.

The model detects the shopper's language from their session and writes the email in it. 25 languages supported, including right-to-left scripts (Arabic, Hebrew) and CJK (Japanese, Korean, simplified and traditional Chinese). The product card labels (price, shipping note, CTA) translate automatically, and merchants can override per locale.

Resend handles DKIM, SPF, and bounce / complaint processing automatically. Hard bounces auto-suppress and never re-send. Soft bounces back off with exponential retry. The widget's GDPR layer respects unsubscribe and erasure requests instantly — if a shopper is forgotten, their email is purged from the next-send list within minutes. See the Resend deliverability docs for the underlying primitives.

Yes. The A/B Thompson sampling bandit applies here: write three subject lines or three opener angles and the bandit routes traffic to whichever wins per audience segment. You don't have to do the stats yourself — the dashboard surfaces winning variants automatically as the data matures.

Every recovery email includes signed click tokens that bind the click to the cart, the email send, and the shopper ID. Orders that convert inside a configurable attribution window (default 7 days) are credited as email-attributed revenue, separated from in-session and cart-rescue revenue so the dashboard never double-counts. The same primitives feed the Outcome tier ledger.