A COD order confirmation call is a short outbound call, made soon after a cash-on-delivery order is placed, that checks the buyer really wants the order and that the delivery address is complete. An AI voice agent can make these calls in Hindi, Hinglish, or a regional language, record the outcome in your order system, and pass unclear cases to a person. The goal is fewer failed deliveries, not more calls.
This playbook is for D2C and e-commerce operations teams in India. It covers why confirmation matters, how to design the call, how to handle addresses, cancellations, and reschedules, what to check on DLT and consent, and how to define success metrics honestly, without promising results we cannot verify.
Why does COD confirmation matter?
Cash on delivery lowers the barrier to buying online, because the buyer pays only when the parcel arrives. The same feature creates a cost: if the buyer is unreachable, changes their mind, or gave an incomplete address, the courier cannot deliver, and the parcel returns to the seller. In Indian logistics this is called RTO, or return to origin. The seller has paid for outbound shipping, often pays for the return leg, and loses the sale and the time the stock was tied up.
Industry sources describe RTO as a particular problem for COD compared with prepaid orders. Razorpay's guide to cash on delivery in India and Amazon Shipping India's explainer on RTO both describe it as a major cost for Indian sellers. We do not quote an RTO percentage here, because published figures vary widely by category, region, and seller, and most come from logistics vendors using different definitions. Measure your own baseline first (see the measurement plan below).
What should the call achieve?
- Confirm intent: the buyer placed the order and still wants it.
- Confirm the address: house or flat number, street, locality, landmark, and pin code are complete and make sense together.
- Confirm reachability: the phone number answers, and the buyer knows to expect a delivery call.
- Capture the outcome: confirmed, address updated, reschedule requested, cancelled, or no answer, written back to your order system.
- Hand off exceptions: anything the agent cannot resolve reaches a human with context, not a cold transfer.
How should the call flow be designed?
Keep it under a minute for the common case. Callers answer unknown numbers reluctantly, so the first sentence must say who is calling, why, and which order, before asking anything.
- 01Identify: the brand name and a clear reason for the call, such as confirming a cash-on-delivery order, with the product name or a short order reference.
- 02Confirm the buyer: ask if this is a good time and whether they placed the order. If someone else answers, offer to call back and share nothing further.
- 03Confirm intent: ask whether they want the order delivered, with a plain yes or no path.
- 04Confirm the address: read back a summary and ask whether anything needs correcting. Ask for the landmark if none is on file.
- 05Confirm the amount: state the amount payable at delivery so the buyer is not surprised at the door, and ask them to keep the cash or a payment method ready.
- 06Close: state the next step, thank the buyer, and end the call. Do not use the call to upsell.
How should the agent clarify addresses in Hinglish?
Address problems are a main reason COD parcels fail. Indian addresses are often written with a landmark rather than a precise street, and many buyers write them in a hurry on a phone. A confirmation call can catch the gaps while the buyer is still engaged. It works best when the agent asks one specific question at a time, in the buyer's mixed language.
- Missing flat or house number: 'Aapke address mein flat number nahi hai, kya aap bata sakte hain?'
- Vague locality: 'Kaunsa area ya society hai, aur nearest landmark kya hai?'
- Pin code mismatch: read the pin code back digit by digit and ask the buyer to confirm it.
- Gate, floor, or office hours: for offices and gated societies, ask when someone will be present to receive the parcel.
- Alternate contact: ask whether another number can be used if the buyer is unreachable on delivery day.
Always read captured details back for confirmation, and store the buyer's words as well as the cleaned address so a human can review ambiguous cases. For mixed Hindi and English speech, see our guide to testing Hinglish voice agents, which includes a protocol for address, digit, and name capture.
How should reschedules and cancellations be handled?
A confirmation call will surface buyers who no longer want the order. That is a useful outcome, since a cancelled order at this stage costs less than a failed delivery attempt. The agent should make cancelling as easy as confirming and never argue.
- Cancel: confirm the buyer wants to cancel, ask an optional one-line reason from a short list, write the cancellation and reason to the order system, and tell the buyer what happens next. Retain-or-discount offers, if you use them, must be approved by you and offered once at most.
- Reschedule: ask for a preferred day or time window, check it against what your courier partner supports, and confirm the new window. If your logistics setup does not allow it, say so and route to a human.
- Change of address: capture the corrected address, confirm it back, and flag whether the courier can accept the change at this stage.
- Wants to pay online: if your payment flow supports it, offer a payment link by an approved channel; otherwise record the request for a human.
- Angry or confused buyer: end politely and escalate with a short summary.
When should the call be made, and how often?
Call soon enough that the buyer remembers the order but late enough that your system has confirmed the order and address details. A common design is to trigger the call on order creation or after a short delay, and to confirm before the order is handed to the courier. Treat these as design choices to test, not facts we can quote results for.
- Call within hours that respect local norms and your own policy; avoid early morning and late evening.
- Cap attempts: for example, a first attempt, a second attempt at a different time of day, and then a message or a human follow-up. Choose your own cap and stick to it.
- Stop calling the moment a buyer asks you not to, and record that preference.
- Prioritise: if you only call a subset of orders, such as higher-value orders or first-time buyers, define the rule in advance and keep a hold-out group for comparison.
- Respect your courier's cut-off times, because a confirmation that arrives after pickup cannot change the shipment.
What should you check on DLT and consent?
Automated outbound calls to Indian numbers sit inside TRAI's telecom commercial communications rules. Order confirmations are usually transactional or service calls rather than promotions, but how a call is classified depends on its content and your consent basis, so keep the script strictly about the order. Do not add marketing language to a confirmation call, because it can change its classification.
- Register your entity, headers, and call templates on a DLT platform before running campaigns. See our explainer on what DLT registration is, and our page on TRAI and DLT for AI calling.
- Scrub against the DND registry where required. Our page on DND registry rules for AI calls explains how scrubbing applies to different call types.
- Keep a record of consent or the order-related basis for contacting the buyer, and make opting out simple.
- Handle personal data carefully: limit what the agent reads aloud, and set a retention period for recordings and transcripts.
- Take legal advice on your own call classification. This article is information, not legal advice.
How DLT registration and template scrubbing apply to outbound calls to Indian numbers.
How DND scrubbing applies to transactional and promotional AI calls.
How do you measure whether it works?
Decide your metrics and baseline before launch. The most useful design is a controlled comparison: call a random portion of eligible orders and leave a comparable portion uncalled, then compare outcomes over the same period. Without a hold-out group, you cannot tell the effect of the calls from seasonality, courier changes, or product mix.
| Metric | Definition | Why it matters |
|---|---|---|
| Contact rate | Calls answered by the buyer divided by calls attempted | Shows whether timing and number quality are working |
| Confirmation rate | Orders confirmed on the call divided by orders reached | Shows buyer intent after verification |
| Address-correction rate | Orders where the address was changed or completed on the call | Shows how much address quality you are fixing |
| Pre-dispatch cancellation rate | Orders cancelled on the call divided by orders reached | Cancellations here cost less than failed deliveries |
| RTO rate, called versus hold-out | Returned orders divided by dispatched orders, per group | The outcome the programme exists to improve |
| Cost per order confirmed | Call cost divided by confirmed orders | Lets you compare with manual confirmation |
| Escalation rate and reasons | Calls handed to a person, tagged by reason | Shows where the script or data needs work |
Report results by category, order value band, and region, because COD behaviour differs widely between them. Sample a set of recorded calls every week for quality, and review every escalation in the first weeks. Our calculator can help you model call volume and cost, but your own baseline RTO is the number that decides whether this is worthwhile.
Keep a short list of call outcomes that your order system can act on automatically: confirmed, address updated, reschedule requested, cancelled, wrong number, no answer after the cap, and escalated. Every outcome should trigger a defined next step, such as releasing the order to the courier, holding it for address correction, or closing it. A call outcome that nobody acts on is wasted effort, so agree these rules with operations before launch.
When not to use confirmation calls
- Very low-value orders where the call costs more than a failed delivery would.
- Categories or regions where buyers strongly dislike unsolicited calls. Consider a message-based confirmation first.
- Orders already paid online. They do not carry COD risk, though a delivery-time call may still help.
- Teams without a clean path to cancel or amend orders in their order system: a call that cannot change anything just annoys the buyer.
- Courier networks that do not allow address changes after dispatch, unless you call before handover.
See how Vaami runs COD verification calls in Hindi, Hinglish, and regional languages. Book a demo.
Order status, returns, and confirmation calls for online sellers.
If your order data lives in other tools, Vaami connects through integrations such as Zapier, so confirmation outcomes can be written back to systems you already use.
Send call outcomes to the tools your order operations already use.
Sources
- Razorpay, 'Cash on Delivery in India: Benefits, Risks and RTO Tips': razorpay.com/blog/cash-on-delivery/
- Amazon Shipping India, 'RTO Explained: How Indian SMBs Can Reduce It': shipping.amazon.in/blog/what-is-rto-how-to-reduce-return-to-origin
- TRAI telecom commercial communications framework (TCCCPR 2018) as summarised in our DLT explainer: vaami.ai/blog/what-is-dlt-registration