COD Confirmation Calls: How D2C Brands Cut RTO in India

Part of our guide: AI Calling for Real Estate in India: Enquiry to Site Visit Playbook

A COD confirmation call is the cheapest check an Indian D2C brand can run between "order placed" and "order packed". Cash on delivery still drives a large share of orders in India, and every unwanted COD parcel costs you shipping twice, ties up stock and comes back as RTO. This guide explains when to call, what to say, how NDR calls save failed deliveries, and the maths that decides whether calling is worth it for your brand.

Why does cash on delivery drive RTO in India?

Because COD costs the buyer nothing to place and nothing to refuse. Impulse orders, duplicate orders, wrong numbers, incomplete addresses and buyers who simply change their mind all ship as normal, and the brand pays forward and return freight on each one. Prepaid buyers have already committed money, so fewer of them walk away.

The scale is large. In a May 2024 disclosure filed with BSE, Delhivery stated that COD orders make up more than 60% of e-commerce orders in India. On returns, internal data from the checkout company GoKwik, cited by YourStory in September 2024, put the average RTO rate in Indian e-commerce at about 20–25%, rising to 40% depending on industry, location or product type.

RTO moves with the season

RTO is not a fixed number. Data from Shipway, Unicommerce's logistics arm, reported by YourStory in April 2026, showed RTO rates of nearly 39% during the November 2025 festive season, falling to about 21% by February 2026. The same analysis found Tier II and III cities drove 66% of new D2C orders in FY2026. Festive spikes and smaller-town growth both mean more first-time COD buyers, which is exactly where a confirmation call earns its cost.

What is a COD confirmation call, and when should it happen?

A COD confirmation call is a short call placed after a cash-on-delivery order and before dispatch. It confirms the buyer really placed the order, checks the amount and address, and records one of a few outcomes. Timing matters most: call within minutes of the order, while the buyer remembers it and before you pay to ship it.

Orders reach our agents the same way leads do. A connected Google Sheet is checked every two minutes, and webhooks or CSV uploads work too. For a D2C health and wellness brand we connected, the sheet was shared privately with our service account as Editor (never made public), only Indian +91 numbers were called, and each call's result was written back into four new columns. Numbers typed with a "+" but no country code were flagged for the team rather than guessed. That brand's sheet held funnel leads rather than COD orders, but the same mechanics apply to an order sheet: private access, clean numbers, results written back where your ops team already works.

The outcomes worth recording

What should the confirmation script sound like?

Short and factual. Greet the buyer by name, name the product, state the amount, confirm the address area, and ask one question: "Shall we send it?" One fact per turn, then stop and listen. If the buyer hesitates, let them cancel easily. A reluctant yes on the call often becomes a refusal at the door.

Here is a hypothetical example for a skincare brand. Product, amount and town are placeholders.

1. "Namaste, Priya ji. I'm calling from Glow Naturals about your order today."
2. "It's the vitamin C serum."
3. "The amount on delivery is 799 rupees."
4. "We'll deliver to your address in Hubballi, near the bus stand. Is that right?"
5. "Shall we send it?"
6. "Thank you, Priya ji. It should reach you in a few days. Have a good day."

The structure comes from real feedback on our calls. A sales manager who tests them told us long monologues feel rushed even when the voice speed is fine, and that a buyer saying "hello?" mid-sentence made a naive agent restart its whole line. One number per turn (here, just the amount) fixes most of that. Using the buyer's name with "ji" matters too: calling a woman "Sir" is a real failure in Indian calls, and the agent never assumes gender.

Language matters outside metros

Many new COD buyers are in smaller towns, where a call in the buyer's language is easier to follow than an English SMS. Our agents speak Hindi, English, Hinglish, Kannada, Marathi, Tamil, Telugu and Bengali, and switch only when the buyer speaks a full sentence in another language, not on a stray "haan".

How does NDR calling save failed deliveries?

When a courier marks a delivery attempt as failed, it raises a non-delivery report (NDR). NDR calling means phoning the buyer quickly after that, finding out what went wrong, fixing the address or number, and agreeing a re-attempt date. The window is short, because unresolved NDRs are sent back to origin after the courier's re-attempts run out.

Typical reasons the call uncovers are practical: the buyer was out, the rider could not find the house, the phone was switched off, or the buyer wanted a different day. Each has a fix the courier can act on if someone tells them in time. The call records the reason and the agreed re-attempt date in your sheet, and your team or an integration passes it to the courier. If the buyer no longer wants the order, you learn that early instead of waiting for the parcel to come back.

How do you set up COD order verification step by step?

Connect your order feed, decide which orders get a call, write a short script, test it, then run it inside calling hours and read the results daily. The point of COD order verification is a decision before packing, so the results must land where your warehouse team looks, not in a separate report nobody opens.

1. Connect the order feed. A Google Sheet your store exports to, a webhook from your store or order system, or a CSV (see integrations). Include order ID, name, phone, product, amount, address and pincode.
2. Set the calling rules. Which orders get called (for example, first-time COD buyers or orders above a value you choose), how many retries, and what happens on no answer.
3. Write and approve the script. Keep it to the six lines above. Add your cancellation and prepaid options only if you actually offer them.
4. Set calling windows and filters. Calling-hour windows, DND checks and India-only number filters are built in.
5. Test with your own team. Place test orders, answer in different languages, give a wrong address, say "I didn't order this", and check every outcome lands in the right column.
6. Run and review daily. Recordings, transcripts and a daily email report show which outcomes are growing. Adjust the rules weekly.

Is confirmation calling worth the cost?

It depends on your own RTO cost and RTO rate, so do the sum before you commit. A confirmation call costs roughly ₹3–8 on our plans. If one call in every few dozen prevents a parcel that would have come back, the calls usually pay for themselves.

Here is a hypothetical calculation. Say each RTO costs your brand ₹200 all-in once you add forward freight, return freight and repackaging (use your own figure; it varies by courier, weight and zone). At ₹8 per call, 25 calls cost ₹200. So the calls break even if they stop one RTO in every 25 confirmed orders. If your COD RTO is anywhere near the 20–25% average GoKwik cited, you have a lot of room. If your RTO is already very low, call only the riskiest segments.

Plans start at a monthly minimum of 3,000 minutes, so check volumes against our pricing before you start. Unanswered calls are not billed.

Common mistakes when confirming COD orders

Most wasted calls come from calling too late, saying too much, pressuring hesitant buyers, or not deciding in advance what each outcome means for the warehouse. The call itself is simple; the rules and timing around it are where most brands slip, so settle those before scaling up.

• Calling after dispatch. You have already paid forward freight. Call before packing.
• Reading the whole invoice. SKU codes, GST and delivery partner names in one breath. Say the product and the amount, nothing else.
• Pushing a hesitant buyer to say yes. A forced yes often becomes a refusal at the door.
• No rule for "no answer". Decide in advance whether to ship, hold or cancel.
• Calling every repeat customer. Buyers with a clean history find it irritating. Use your own data to skip them.
• Hanging up mid-sentence. Our platform holds the hang-up until the goodbye has played.

AI calling is the wrong tool for disputes, refund arguments or angry buyers. Those go to your support team, and a manager can listen in or take over a live call.

Making confirmation calls part of your order flow

To reduce RTO in India you need several levers working together: a better checkout, smarter courier allocation and prepaid nudges. A call before packing is one of the cheapest, and NDR calls catch some of what slips through after dispatch. None of them works alone.

A COD confirmation call is a small, cheap check placed before money is spent on freight. See AI calling for D2C and e-commerce, AI calling for logistics and our AI calling playbook for real estate and other industries. Book a 20-minute demo and we'll call your phone with an agent set up for your business.

Written by the DigitalCallers Team

We build and run AI calling agents for Indian businesses from Gurugram, in Hindi, English and regional languages. Our articles draw on calls we have run ourselves and link to primary sources such as TRAI, DoT and MeitY for anything regulatory. Spotted something out of date? Write to support@digitalcallers.com.