E-Commerce · D2C · Retail
Sell on WhatsApp, confirm every COD, and keep the channel you built
One agentic AI operating system for the whole commerce lifecycle: ad clicks that land in a thread that actually sells, carts recovered with a pay link, COD orders verified before dispatch, and repeat demand you do not have to buy twice.
- Shopify, WooCommerce & custom
- Catalogue & inventory sync
- Pay links in-thread
- Opt-in, capping & opt-out
- Template quality protection
- One number, every store
Discovery & Conversion
Your ad click lands in a conversation that sells
Click-to-WhatsApp is some of the cheapest high-intent traffic in Indian commerce — and most of it dies in a thread nobody answers for six hours. An AI agent picks up every click immediately, answers the question standing between the customer and the order, and closes in the same thread.
-
Answered in the first minute, including at 2am
The window where purchase intent is highest is the one your team is asleep for. The agent replies instantly, in the customer’s language, whether the click came at noon or midnight — and a slow first reply is the most expensive thing in this funnel.
-
The questions that actually block a purchase
Size and fit against a real chart, ingredients and allergens, device compatibility, fabric and care, warranty terms, and whether it reaches their PIN code before the weekend. Answered from your catalogue, not guessed.
-
Catalogue browsing without leaving the thread
Customers browse, filter and compare inside the chat. The agent narrows six plausible options down to the two that match what they actually said — the job a good shop assistant does and a product grid cannot.
-
Recommends, then closes
Once the customer picks, the agent confirms variant and quantity and sends a pay link in the thread. No bounce to a website where the cart has to be rebuilt from scratch and half the buyers never arrive.
-
Every click carries its attribution
Campaign, ad set and creative travel into the thread and stay attached to the order. You get to see which creative produced conversations and which produced revenue — two lists that are rarely the same.
Quick check: our linen runs slightly relaxed. If you normally wear a fitted M, M is right. If you like room, size up.11:47 pm
- SourceInstagram · click-to-WhatsApp
- CampaignMonsoon Drop · Reel 04
- First reply11 seconds
- Outcome₹2,480 · prepaid
Cart & Checkout Recovery
Recover the cart — then make sure the order survives dispatch
These are two different leaks. An abandoned cart loses you the order before it exists. RTO loses you the order after you have paid to pick, pack and ship it, and it comes back as a refund plus two-way freight. Both are conversations, and both run on the same cadence engine.
- Cart abandoned · +30 minutes
A reminder listing the exact items, with a link back into the same cart rather than the homepage. No coupon by default — most carts come back without discounting the margin away, and a reflexive 10% teaches customers to abandon on purpose.
- COD confirmation before dispatch
Every cash-on-delivery order gets a confirmation message with the item and address before it enters the shipping queue. Unconfirmed orders are held, not shipped. For most Indian D2C brands this single automation is the highest-ROI thing on this page.
- Address repair, not cancellation
When a PIN code does not match the city, a flat number is missing or the landmark is unusable, the agent fixes it in-thread while the packet is still in your warehouse — instead of the courier discovering it at the door.
- Prepaid conversion at the confirmation step
The moment a customer confirms a COD order is the moment they are most willing to prepay for a small incentive. Every switch removes an RTO risk completely and improves your working capital at the same time.
Recovery flows obey the same rules as campaigns: frequency caps, quiet hours and opt-out all apply. A customer who has said stop is not chased, and nobody sits inside three sequences at once because three teams each built one.
Cart & COD recovery Rolling 7 days
RunningPost-purchase & Support
Retire the “where is my order” queue
WISMO is the largest single support category in commerce and almost none of it needs a human. Put shipping state, returns and refunds into the same thread the customer bought in, and the tickets stop being created rather than being answered faster.
Order & shipping updates
Every state change pushed into the thread as it happens, so the customer never has to ask — and never has to find a tracking page or an order number to do it.
Delivery exceptions, handled early
A failed attempt, an unreachable address or a courier delay triggers a conversation the same day — while it can still be fixed, instead of turning into a refund and a one-star review.
Returns & exchanges without a form
Reason captured conversationally, photo proof uploaded in-thread, pickup slot chosen from real availability, exchange size confirmed against live stock.
Refunds, and knowing when to stop automating
Refund status answered from the system of record. Anything genuinely broken — damaged goods, a wrong item, a customer who is already angry — routes to a human with the order, the photos and the history attached.
- ConfirmedWed, 11:52 pm
- Packed & shippedThu, 10:20 am · BLR hub
- Out for deliveryToday, 8:40 am · arriving by 2 pm
No charge, and you keep the original until pickup.09:14 am
Take the volume out before it becomes a ticket
- Proactive updates at every state change, so nobody needs to ask
- Tracking answered live from the courier API, inside the thread
- Return pickup slots booked without a phone call
- Damaged or wrong items route to a human with the photos attached
Retention & Repeat
Buy the customer once, not every time
Paid acquisition gets more expensive every quarter, and the cheapest order you will take this month is the second one from a customer who already trusts you. Email gets 20% opened. WhatsApp gets read — which is exactly why it has to be used carefully.
Replenishment timed to consumption
A 30-day supplement, a 60-day refill, a quarterly filter. The reminder lands when the customer is actually running out — calculated from their order, not from a generic 45-day blast to everyone.
Win-back before they are gone
Lapsed cohorts get a sequence built around what they actually bought, not a generic “we miss you”. A customer who bought running shoes in March needs a different message from one who bought a gift.
Drops, restocks and early access
New-drop and festive campaigns to segmented cohorts rather than the whole list, and back-in-stock alerts that go only to the people who asked for that exact variant — the highest-converting message most brands never send.
Loyalty that lives where they already are
Points balance, tier status, referral links and reward redemption answered in the thread. A loyalty programme nobody can check is a loyalty programme nobody uses.
Retail & Omnichannel
Every store on one number, none on a personal phone
Store staff already message customers — usually from their own handsets, on threads you cannot see, with a customer list that walks out the door when they resign. The answer is not to ban it. It is to bring it onto the brand’s number without taking the relationship away from the store.
Routed to the right store, from one brand number
The customer messages the brand. PIN code, stated location or purchase history routes the thread to the store that can actually serve them — with stock at that store, not the national catalogue.
Clienteling without personal numbers
An associate keeps their customer relationships inside the Unified Inbox. When they move stores or leave, the conversations, preferences and notes stay with the brand — and the next associate opens the thread with the full history.
Appointments and click-and-collect
Trial slots for high-consideration categories, styling appointments, service bookings, and collection coordination — confirmed in chat with a reminder the morning of, which is where most no-shows are actually lost.
Store-level performance you can finally see
Response times, conversations handled, appointments booked and outcomes per store and per associate — the visibility that was impossible when this ran on personal WhatsApp.
Operations & Governance
The channel is an asset. Most brands spend it.
WhatsApp punishes brands that over-message. Blocks and reports drag your quality rating down, your messaging limit falls with it, and the channel you spent two years building quietly stops delivering — usually discovered during a festive sale. Everything here exists to make volume safe.
Your stack, connected both ways
Shopify, WooCommerce and custom back-ends via API and webhooks. Orders, carts, shipping events and customer records move in; conversation outcomes and consent state move back out.
Catalogue and stock in sync
Products, variants, prices and availability stay current, so the agent never sells something you cannot ship. Out-of-stock becomes a back-in-stock signup instead of a broken promise.
Opt-in captured, opt-out honoured
Consent is recorded with its source and timestamp — checkout, ad click, website widget or store. Opt-outs propagate across every campaign and every team immediately, not at the next list export.
Frequency capping and quiet hours
A hard ceiling on promotional messages per customer per week, enforced across every campaign no matter which team scheduled it — plus quiet hours, so nobody gets a sale alert at 6am.
Quality rating watched, not discovered
Block and report rates are tracked per template and per campaign. A send that is damaging your rating is capped or paused before the tier drops — rather than being diagnosed after your messaging limit has already been cut.
What customers complain about, clustered
Conversational analytics groups what is actually being said across every thread — a size that runs small, a colour that photographs wrong, a courier failing in one city. The return rate has a reason, and it is usually visible here first.
Volume that does not cost you the channel
Quality rating and messaging limit are the two numbers that decide whether next month’s campaigns get delivered at all. The platform tracks both against the sends that move them, caps a campaign before a tier drops, and shows you plainly which template is doing the damage.
Sender health & template performance Rolling 7 days · +91 80 4718 2200
MonitoringWhat changes
Where the margin actually comes back
- 20–30%of abandoned carts recovered, without discounting the margin away
- 30–50%less RTO on COD orders that pass through a confirmation step
- 70%+of “where is my order” resolved without a support agent touching it
- 3–5×cheaper to reactivate a past buyer here than to re-acquire them on paid
Illustrative ranges modelled on common commerce deployment patterns for this class of workflow. They are not measured results from a named customer. Your own numbers will depend on category, average order value, COD share, existing automation and how disciplined your campaign calendar is.
Questions from growth, ops and engineering
The objections we get asked first
Short answers here; your team gets the full integration and pricing detail during evaluation.
Does this work with Shopify, WooCommerce or our custom stack?
Shopify and WooCommerce connect through their standard app and API surfaces — orders, carts, customers, fulfilment events and catalogue. Custom and headless stacks connect through REST APIs and webhooks in both directions. The integration you actually need is usually smaller than expected: order and cart events in, conversation outcome and consent state back out. Anything unusual in your stack is a scoping conversation, and we will say plainly if something is not supported rather than promise around it.
How does catalogue and inventory sync stay current?
Products, variants, prices and stock levels sync from your store, and the agent reads availability at conversation time rather than from a nightly copy. That matters most in the two moments customers notice: the agent never recommends something that just sold out, and an out-of-stock variant converts into a back-in-stock signup instead of a broken promise you have to apologise for later.
Will heavy campaigning get our number flagged or rate-limited?
It can — that is a real risk on WhatsApp and the reason this is a first-class feature rather than a footnote. Quality rating is driven by blocks and reports, and messaging limits move with it. The platform tracks block and report rate per template and per campaign, enforces a promotional frequency cap per customer across every team, honours quiet hours, and will cap or pause a send that is trending badly before the tier drops. The failure mode we design against is the one brands actually hit: discovering the problem during a festive sale, when the limit has already been cut.
Where do opt-ins come from, and how is consent handled?
Consent is captured with its source and timestamp at the point of collection — checkout, an ad click, a website widget, a QR code in store — and stored against the customer. Opt-outs apply immediately across every campaign, every sequence and every team, and are honoured by recovery flows too. Uploading a purchased list is not a supported growth strategy here; it is the fastest way to lose the number.
What does this actually cost per message at our volume?
Two components: Meta’s own conversation pricing, which varies by category and country and is billed through to you, and the platform fee. The lever most brands miss is category — utility conversations like order confirmations and shipping updates price differently from marketing ones, so a flow designed well is materially cheaper than the same flow designed carelessly. We will model your mix against your real order volume during evaluation instead of quoting a per-message number that hides the variable.
Can we attribute revenue back to click-to-WhatsApp ads?
Yes. The campaign, ad set and creative that produced a click travel into the conversation and stay attached through to the order, so you can separate the creatives that generate conversations from the creatives that generate revenue — two lists that are rarely the same. Outcomes can be pushed back to your analytics stack so this sits alongside the rest of your paid reporting rather than in a separate dashboard nobody opens.
Do we still need a support team?
Yes, a smaller one working on harder things. Order status, tracking, returns intake and refund status are high-volume and low-judgement, and those stop becoming tickets. What remains — damaged goods, a genuinely angry customer, an exception the courier caused — lands in the Unified Inbox with the order, photos and full history attached, and AI Co-pilot drafting the reply. The headcount question usually resolves as redeployment rather than reduction.