Operations
E-commerce Cart Recovery via Call + WhatsApp (2026 Playbook)
Complete cart-abandonment recovery playbook for Indian e-commerce — WhatsApp + voice cadence, COD verification, and the 24h-2h-24h timing that recovers 60-70%.
Indian e-commerce sees 70-75% cart abandonment. That's not a problem unique to India — it's universal. What IS unique is the recovery channel mix: WhatsApp dominates, voice still matters, email is a fallback. Here's the playbook that recovers 25-40% of abandoned carts.
Why most cart recovery flows fail in India
- Email-only cadence — Indian customers open email at 25-30% rates; WhatsApp at 95%+
- Generic copy — "You left items in your cart" without product detail or urgency
- Wrong timing — sending the first nudge 24+ hours later, when the customer's intent has cooled
- No COD-specific handling — for COD orders, abandonment is different from prepaid abandonment
- Channel silo — email team doesn't know what voice team is doing, customer gets contradictory messages
The 4-touch cadence that works
- T+1h — WhatsApp template: "Hi {name}, you left {product} in your cart. Complete in 2 taps: {checkout link}." One CTA, one product image.
- T+24h — Voice call: AI Receptionist or human, 30-second script. "We saw you were interested in {product}. Anything we can help with?"
- T+48h — WhatsApp follow-up: with a small incentive — free shipping, 5% off, bundle suggestion.
- T+72h — Email: final reminder, broader catalogue if first item is sold out.
What each channel actually does
| Channel | Open / answer rate | Recovery contribution |
|---|---|---|
| WhatsApp T+1h | 92% | 60% of total recovery |
| Voice T+24h | 30% | 25% of total recovery |
| WhatsApp T+48h | 85% | 10% of total recovery |
| Email T+72h | 28% | 5% of total recovery |
WhatsApp is the workhorse. Voice catches customers who don't read messages. Email cleans up the long tail.
COD verification — the second use case
For Cash on Delivery orders, the cadence is identical but the trigger is different: COD order placed but not yet verified within 60 minutes. Outcomes:
- 30-50% lower RTO rate — verified orders ship; unverified ones get cancelled before fulfilment
- Higher prepaid conversion — during the verification call, AI offers a small prepay discount
- Address validation — confirm pin code, landmark, alternate number
Compliance — DPDP and TRAI implications
- DPDP consent — checkout flow must capture explicit opt-in for cart-recovery communications
- Calling window — voice calls 9 AM – 9 PM IST; WhatsApp anytime
- DLT registration — the WhatsApp templates and voice scripts need DLT approval
- Opt-out — every WhatsApp message must have a one-tap unsubscribe
- Data residency — cart events and customer details must stay on Indian infrastructure
Worked example
An Indian D2C brand with 10,000 monthly carts:
- Abandonment: 7,500 carts (75%)
- Average order value: ₹1,200
- Lost revenue at baseline: ₹90 lakh / month
- With recovery cadence at 30%: 2,250 recovered orders × ₹1,200 = ₹27 lakh / month recovered
- Cost of WhatsApp + voice cadence: ~₹2-3 lakh / month
- Net upside: ~₹24 lakh / month
ROI is dramatic for any brand above ₹500 AOV. Below that, the unit economics tighten but a WhatsApp-only flow still works.
How Kedeyo runs it end-to-end
Kedeyo's e-commerce stack ships:
- Webhook trigger from Shopify / Magento / WooCommerce on cart abandonment
- Pre-built WhatsApp templates approved on your DLT entity
- AI Receptionist voice script for the T+24h call
- Multi-channel attribution — see which touch converted
- WhatsApp Business API + voice + email in one dashboard
Bottom line
Cart recovery is the highest-ROI lever in Indian e-commerce. Run a 4-touch cadence (WhatsApp + voice + WhatsApp + email), respect DPDP consent, and most brands above ₹500 AOV recover 25-40% of abandoned carts. Reference: Baymard Institute for global cart-abandonment benchmarks.
Frequently asked questions
What's a realistic cart-recovery rate?+
Should I call or WhatsApp first?+
Does this work for low-AOV products?+
Is calling abandoned-cart customers DPDP compliant?+
How does this connect to COD verification?+
Kedeyo Editorial
Reviewed by the Kedeyo product team
Last updated
16 May 2026