AI COD confirmation calls and WhatsApp to cut RTO for Indian D2C stores

Updated 2026-09-19 · 5 min read · By the Convo360 team

Why RTO happens on Indian COD orders

Return-to-origin is rarely one problem. It's a mix of impulse orders placed late at night, addresses typed in a hurry, customers who genuinely change their mind, and a share who simply aren't reachable when the courier calls once.

Because COD still makes up a large share of orders for many D2C categories in India, a confirmation step before dispatch is one of the few controllable levers a brand has over RTO.

The cost of an RTO isn't just the lost sale. Forward shipping, reverse shipping and repackaging all add up, and a product that's been through a failed delivery attempt often can't be resold at full price. A single well-placed confirmation step, run before the order ever leaves the warehouse, is cheaper than absorbing that cost after the fact.

The call-then-WhatsApp fallback, and why order matters

Sending a WhatsApp message with Buttons, 'Confirm order' and 'Cancel order', right after checkout catches easy confirmations cheaply and instantly. For orders that go unanswered for a few hours, an outbound AI voice call is more effective than a second text, because it reaches customers who don't check WhatsApp often or whose number is a family member's phone.

Some brands do it the other way for high-value orders: call first for anything above a value threshold, then fall back to WhatsApp only if the call isn't picked up. Either order works: the point is using both channels rather than one.

A call also catches something WhatsApp can't: tone. A hesitant 'haan, theek hai' on a call often signals a customer who's still unsure, giving the AI agent a chance to ask a clarifying question right then that a one-word WhatsApp reply would have hidden entirely.

A sample confirmation script and cadence

Keep the voice script to under a minute: greet, state the order and amount, ask for a yes/no, confirm the delivery address aloud, and close. A script that drags on with cross-sell attempts during a confirmation call tends to increase hang-ups rather than build goodwill.

What to do when the customer says no

A clean cancellation protects your relationship with that customer for their next order. The AI agent should acknowledge the decision, ask once, politely, if there's a reason worth noting (wrong size, changed mind, found it cheaper elsewhere), and then confirm the cancellation without arguing.

Capturing that reason in your CRM pipeline is useful: a pattern of 'found cheaper' cancellations tells you something pricing can't fix with more calls, while a pattern of 'wrong size' cancellations points to a sizing-chart problem on your product page.

Timing rules, edge cases and mistakes to avoid

• Call between 10 AM and 7 PM; avoid early morning and late evening.
• Don't call more than twice for the same order: after that, let WhatsApp carry the follow-up.
• Skip the call entirely for repeat customers with a clean delivery history; confirm them by WhatsApp only.
• Edge case: if the number is unreachable (switched off, invalid), flag the order for manual review rather than looping retries indefinitely.
• Mistake to avoid: calling before the WhatsApp Utility template has even had time to be read. Give it at least 2-3 hours before escalating to a call.

These rules aren't just courtesy, they protect your brand's reputation. A customer who gets called twice a day for a single order is more likely to block your number entirely, which then affects every future order confirmation and marketing message you try to send them.

Deciding which orders even need a call, and setting it up on Convo360

Not every COD order carries the same RTO risk. New customers, first-time high-value orders, and orders shipped to areas with a known history of failed deliveries are worth the extra step of a call. Repeat customers with a track record of accepting deliveries can often be confirmed by WhatsApp alone, which keeps your calling volume, and cost, proportional to actual risk rather than blanket-calling every order.

1. Connect your store's new-order event as an inbound webhook, mapping order ID, product, amount and address to variables.
2. Trigger a chat flow that sends a Send Template message with Confirm / Cancel buttons.
3. Add a Wait / Delay of 2-3 hours; if there's no button reply, branch with a Condition block into an outbound call using the voice blocks, gather to collect a spoken yes/no.
4. On confirmation, a Webhook block posts back to your store to release the order for packing; on cancellation, it posts a cancel status instead.
5. Either outcome logs to the CRM pipeline for reporting.

See the voice docs for setting up outbound calling.

What it costs, and measuring the impact

Because Convo360 is BYOK, you pay your telephony provider (Exotel, Plivo, Twilio or your own SIP trunk) directly for call minutes and Meta directly for the WhatsApp template, there's no per-message or per-minute markup from the platform. On the ₹999 Starter plan you get WhatsApp confirmation flows; AI voice calling is available from the ₹2,999 Pro plan.

To measure whether this is working, track RTO rate before and after adding the confirmation step, split by orders confirmed via WhatsApp only versus orders that needed a call. If the call-escalated group still shows high RTO, the address-confirmation part of the script needs more attention than the yes/no part.

Step by step

1. Send a WhatsApp Confirm/Cancel templateTrigger immediately after checkout with order details and Buttons for Confirm and Cancel.
2. Wait 2-3 hours for a replyUse a Wait / Delay block; most easy confirmations happen in this window without needing a call.
3. Escalate non-responders to an AI voice callBranch with a Condition block into an outbound call that asks for a spoken yes/no and confirms the address.
4. Post the outcome back to your storeUse a Webhook to release confirmed orders for packing or mark cancelled ones, and log both to the CRM pipeline.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.