WhatsApp cart recovery for Indian DTC brands: a setup guide

If you sell DTC in India, your abandoned-cart email open rates are likely below 15%. Your WhatsApp message open rates are probably 80% or higher. The gap is so wide that any recovery strategy that leads with email is leaving most of the recoverable revenue on the table.

This guide walks through setting up WhatsApp cart recovery end-to-end: the two API options, getting your templates approved, the message-timing strategy that works for Indian shoppers, and wiring it into a rule that fires automatically.

Why WhatsApp wins in India

India has more than 500 million WhatsApp users. For most DTC shoppers, it's the primary communication channel — they check it constantly, while the inbox gets days of neglect. A recovery message sent over WhatsApp typically reaches the visitor within minutes; an email might sit unread for a week, by which time the intent has gone cold.

WhatsApp also lets you ask a question and get a reply conversationally — something email is structurally bad at. A message like "Hi Priya, was the size what you wanted? I can hold your cart for 30 minutes if you want to come back."feels like a real human checking in, not a marketing blast.

The two API options: Twilio vs Meta Cloud API

WhatsApp Business messaging requires going through one of WhatsApp's approved Business Solution Providers. The two most common in India:

• Twilio — easier to set up, pays-per-message, comprehensive docs. Good for anything under 5,000 messages/month.
• Meta Cloud API (direct) — slightly cheaper at scale, requires you to set up a Meta Business Manager account and a WhatsApp Business Account. Better for high volume.

Either way, you'll need:

• A registered business name and address
• A phone number not currently on personal WhatsApp
• Your business GST number (helps Meta's verification)
• One pre-approved template for cart recovery (more on that below)

Getting templates approved

WhatsApp doesn't let you send arbitrary marketing messages. Every outbound message that initiates a conversation must use a pre-approved template — short, specific, and usually limited to one variable insertion.

Approval times in India are usually 24–48 hours. Reasons for rejection: anything that reads as a discount blast, anything with promotional emojis stacked at the start, anything that asks for sensitive info (PAN, Aadhaar). Lean conversational; lead with utility.

Templates that get approved easily and convert well:

• Hi {{1}}, you left a {{2}} in your cart at {{3}}. Would you like me to hold it for you? Reply YES to keep it, STOP to opt out.
• Hi {{1}}, this is {{2}} from {{3}}. Did you find what you were looking for? I can answer any question or help with sizing.
• {{1}} — your {{2}}is still waiting. Order today and we'll ship by tomorrow. Use code {{3}} to save 10%.

When to send: timing strategy for Indian shoppers

Indian DTC shoppers usually browse during three windows: 9–11am, 2–4pm, and 9–11pm. Cart abandonment timing data from a handful of Indian merchants suggests these heuristics:

• 15 minutes after abandon — best moment for the first WhatsApp. Visitor is still in browse-mode, often on the same phone they used to add the item.
• Between 8am and 10pm only — late-night messages feel intrusive and reduce conversions. Build a quiet-hours window into your rule.
• Maximum two messages per cart — first at 15 min, second 24 hours later if still no order. A third message hurts more than helps.

Wiring it up in RecartIQ

Once your WhatsApp template is approved and you have either Twilio credentials or Meta Cloud API tokens, here's the setup:

1. On your site detail page, scroll to Integrations → WhatsApp section. Pick provider (Twilio or Meta), paste credentials JSON. Encrypted at rest.
2. Create a rule: Trigger: Cart abandoned for 15 minutes. Action: Send WhatsApp. Paste your approved template name and variable mappings.
3. Add a second action on the same rule: Generate coupon with a 10% discount if you want to include a code in the message.
4. Save. The rule fires when the cron sweep runs (every 1–2 minutes if you're using cron-job.org) and the visitor is still unconverted.

What to track

The two metrics that matter:

• Reply rateon the first message. If it's below 5%, your template copy is too promotional. Rewrite as a conversational check-in.
• Recovery rate(orders / messages sent). Healthy benchmarks: 8–15% on the first message, 3–6% on the follow-up. If you're below this, look at timing and template copy first; discount amount second.

RecartIQ's conversion uplift report breaks this down per rule — exposed visitors (who got a WhatsApp) versus organic (who didn't). That's the real measure of incremental revenue.

Common pitfalls

• Sending too soon (under 5 min) — feels stalkery, reduces trust.
• Stacking three or more messages — high opt-out and STOP rates, hurts your sender reputation with Meta.
• Discount-led messaging — trains shoppers to abandon carts intentionally to get coupons. Lead with utility, discount last.
• Skipping STOP handling— your provider needs to process opt-outs. Twilio and Meta Cloud handle this automatically if you set it up correctly; don't bypass.

What about email and popups?

WhatsApp recovers what popups and email can't — visitors who already left the site. Run all three together:

• Exit-intent popupas the first line of defense while they're still on your site
• WhatsApp at 15 minutes for visitors who have identified themselves with a phone number
• Email at 2 hours as a backstop for visitors who gave email but no phone

Stacking all three is what gets total recovery rate from ~3% to the 12–18% range that well-tuned Indian DTC stores hit.