Conversation OS
Start free
All posts

Retail

Abandoned cart recovery on WhatsApp

VartaDesk

Abandoned cart recovery on WhatsApp without spam: same thread as the hold and pickup, approved templates, DLT SMS fallback, opt-out, and when email should fire.

A shopper on a city street with bags — the website cart and the store hold are the same person, or you will double-message them.
A shopper on a city street with bags — the website cart and the store hold are the same person, or you will double-message them.

Abandoned cart recovery on WhatsApp works when the shopper already knows you. It fails when a brand treats WhatsApp like a cheaper email blast — five “still thinking??” pokes after they already asked the store to hold a size until Saturday.

Meta’s template rules, the 24-hour window, and opt-out are not decoration. Neither is India DLT if the fallback is SMS.

The useful design: the cart, the hold, and the pickup live on the same person, and the reminder leaves on the channel they already used.

Why most WhatsApp cart flows feel like spam

  • They blast a list, not the person who abandoned *this* SKU.
  • They ignore the 24-hour window and send a marketing template that reads like a guilt trip.
  • They do not know about the in-store hold, so the associate and the bot contradict each other.
  • They keep going after STOP.
  • They never offer email for the receipt-heavy shopper who hates chat.
Makeup and shopping clutter on a table — recovery should name the SKU, not “Hey, you left something.”
Makeup and shopping clutter on a table — recovery should name the SKU, not “Hey, you left something.”

A sequence that does not annoy

  1. Checkout drop or on-site event creates or updates the shopper in the CRM — not a new anonymous blast list.
  2. If they messaged you in the last 24 hours on WhatsApp, a service-style reminder can be conversational. If not, you need an approved template that matches the registered body, variables included.
  3. One reminder. Then a different move: hold expiry, size restock, or a human. Not five pokes.
  4. If WhatsApp is quiet, SMS (DLT-registered in India) or email carries the link. That is why a four-channel desk beats a WhatsApp-only bot.
  5. If they reply, human takeover pauses the journey. An associate who is already packing the hold must not fight a bot.

VartaDesk retail models hold requests and pickups so the associate sees the SKU and the until-time next to the thread.

Shopify is not the whole job

Commerce tools and Interakt-style WhatsApp-for-Shopify setups are strong at the cart event. They are weaker when the same human also has a store hold that never existed in checkout — “keep the linen shirt until Saturday.” The CRM record has to represent both, or the associate keeps a sticky note and you will double-message.

You may keep Shopify as the order system of record. VartaDesk can listen to store orders as an overlay, not a second inventory. For the commerce-vs-desk split see Interakt alternative.

A market stall — pickup and cart are one shopper; the journey should know both.
A market stall — pickup and cart are one shopper; the journey should know both.

Consent, quota, bans

Cart recovery is still outbound. Globally opted-out leads, or per-channel WhatsApp/SMS/email opt-out, must not be messaged. Bulk campaigns should check reach and plan quota before enqueueing. A recovery flow that “just sends” is how WABAs get banned and Headers get parked.

India: SMS templates need complete DLT. DLT explainer.

Week-one definition of done

  • Holds expire in the CRM, not in someone’s head.
  • WhatsApp template matches the approved body.
  • SMS templates carry DLT IDs.
  • A live agent can take the thread without the journey talking over them.
  • You can show a shopper who both abandoned a cart *and* has an open hold — and only one reminder goes out.

See retail or start a trial. Abandoned cart is a journey. The product is the desk that still knows the pickup.

Retail pack Start free