E-commerce NDR Calling Services in India (2026): Reduce RTO & Failed Deliveries

Quick answer: E-commerce NDR calling is a structured process for contacting customers after a courier records a Non-Delivery Report (NDR), confirming whether they still want the order, resolving the delivery issue, and requesting a valid reattempt before the shipment becomes Return to Origin (RTO). The strongest programmes combine fast customer contact, accurate reason codes, courier coordination and measurement of actual delivery outcomes—not just calls made.

For Indian D2C brands and online retailers, an NDR is a time-sensitive exception. A customer may be unavailable, the address may be incomplete, the phone may be unreachable, or the buyer may no longer want a Cash on Delivery (COD) order. Each reason needs a different response. A generic “your order could not be delivered” call rarely solves all of them.

What is NDR calling in e-commerce?

A Non-Delivery Report (NDR) is a courier-reported exception created when a delivery attempt does not result in the parcel reaching the customer. NDR calling means contacting the recipient to understand the reason, confirm delivery intent, correct actionable details where permitted, and coordinate a suitable next attempt with the courier partner.

NDR and RTO are not the same. NDR is the exception or failed-attempt status; RTO (Return to Origin) is the shipment’s return to the seller after delivery fails or the shipment is otherwise marked for return. A timely, accurate intervention may save some shipments, but not every NDR is recoverable.

For a practical overview of NDR status and response workflows, see Amazon Shipping’s guide to Non-Delivery Reports in India.

Why NDR management matters to Indian e-commerce brands

RTO consumes more than a courier fee. A failed COD order can tie up inventory, trigger forward and reverse logistics costs, create extra customer-service work and delay the next sale of the item. The business may also have already paid for acquisition, packaging, fulfilment and payment or marketplace processing.

A January 2026 SEBI-hosted prospectus describes RTO as a shipment that was not delivered and is returned to origin, involving both a forward and return leg. It also cites an estimated 4.9–5.3 billion e-commerce logistics shipments in India in FY2025 (excluding grocery), illustrating the scale of the delivery ecosystem. These are market-level figures, not a prediction of any individual brand’s NDR or RTO rate. Read the prospectus.

The operational implication is straightforward: brands should treat NDR as a queue of time-sensitive exceptions with ownership and measurable outcomes, rather than as a report to review after the courier has already initiated a return.

Common NDR reasons and the right response

NDR reason	Useful customer action	Operational follow-up
Customer unavailable	Confirm a realistic date or delivery window.	Submit the reattempt request through the approved courier workflow.
Phone unreachable	Try the permitted alternate contact channel and verify the number where appropriate.	Record each attempt and use the courier’s allowed escalation process.
Incomplete address or landmark	Confirm the missing address detail with the customer.	Update only the fields the courier process permits; avoid collecting unnecessary personal data.
Customer refused COD	Ask neutrally whether the customer still wants the order and clarify any genuine confusion.	Do not pressure the buyer or misrepresent payment, product or return terms.
Delivery attempted but customer disputes it	Capture the customer’s account without promising an outcome.	Escalate the disputed attempt to the seller or courier team for verification.
Customer requests cancellation	Confirm the request and explain the applicable policy accurately.	Follow the seller’s cancellation and courier-instruction process; do not disguise a cancellation as a successful recovery.

How an effective NDR calling workflow works

1. Ingest the NDR quickly. Receive the exception from the courier portal, order-management system, shipping aggregator or approved API. Capture the order ID, tracking ID, NDR reason, timestamp and permitted contact details.
2. Prioritise by time and recoverability. Give attention to fresh NDRs with a viable reattempt window. Use order value, prior delivery history and reason codes as prioritisation signals only where the data is lawful, reliable and appropriate.
3. Contact the customer with context. Identify the brand and order clearly, explain that the courier could not complete delivery, and ask what would help. Avoid vague scripts that do not mention the actual issue.
4. Resolve the reason, not just the call. Confirm availability, validate a missing landmark, clarify a payment misunderstanding or record a genuine refusal. Do not mark a shipment “saved” merely because the customer answered.
5. Submit the correct instruction. Pass the verified reattempt request, address correction or other authorised instruction into the courier workflow. A call without a corresponding operational update may have no impact on delivery.
6. Confirm the outcome. Track whether the courier accepted the request, attempted delivery again, delivered the parcel, or ultimately marked it RTO. Close the case only when the agreed status is available.
7. Review patterns weekly. Compare NDR reasons by courier, pincode, product category, payment mode, time of day and customer-contact outcome. Use the findings to improve checkout, address capture, courier allocation and customer communication.

Human calling, automation or a hybrid model?

There is no single best channel for every NDR. The right model depends on shipment volume, the complexity of the exception, customer preferences, available integrations and the time remaining before a shipment is returned.

Model	Best suited to	Main limitation
Human NDR calling	Ambiguous reasons, address clarification, customer concerns and sensitive conversations.	Requires staffing, training, quality monitoring and reliable case updates.
Automated voice or messaging	Simple confirmations, reminders and standard rescheduling prompts where the courier workflow supports them.	May not resolve complex objections or disputed delivery attempts; channel reach is not guaranteed.
Hybrid NDR operations	High-volume brands that can automate routine steps and route exceptions to trained agents.	Requires clear hand-off rules, integration testing and ownership of unresolved cases.

Automation should not be judged by the number of messages or calls sent. It should be judged by whether it creates a correct, timely action and improves final delivery outcomes without increasing complaints or customer friction.

How to measure NDR calling performance

Build a measurement model that follows the shipment from exception to final outcome. Keep the denominator explicit: rates calculated on all orders, all shipped orders, COD orders or only NDR cases are not interchangeable.

• Contact rate: unique NDR cases where a customer was successfully reached ÷ eligible NDR cases attempted.
• Customer confirmation rate: cases where the customer confirms a delivery action ÷ cases successfully reached.
• Reattempt acceptance rate: eligible cases for which the courier accepts a reattempt request ÷ eligible cases where a reattempt was requested.
• NDR-to-delivery recovery rate: NDR shipments subsequently delivered ÷ NDR shipments in the defined cohort.
• NDR-to-RTO rate: NDR shipments that ultimately return to origin ÷ NDR shipments in the same cohort.
• Cost per recovered shipment: total NDR intervention cost ÷ shipments actually delivered after intervention.
• Complaint and opt-out rate: track alongside recovery to identify aggressive, confusing or excessive contact.

Use a consistent cohort and allow enough time for the courier’s final status to mature. Compare like-for-like groups and, where practical, use a holdout group or phased rollout. Otherwise, a seasonal change or a courier’s improved performance may be incorrectly attributed to the calling team.

Illustrative example: what is a recovered shipment worth?

Illustrative example only—not MasCallNet performance data and not an industry benchmark.

Suppose a store has 1,000 NDR cases in a month. A controlled pilot leads to 80 additional completed deliveries compared with a comparable baseline group. If the store estimates that each additional completed delivery contributes ₹250 after product and variable fulfilment costs, the incremental contribution is ₹20,000 (80 × ₹250). If the intervention costs ₹12,000, the estimated net contribution after intervention cost is ₹8,000.

This is not the same as counting 80 customer confirmations. Use actual delivered orders, contribution margin and full intervention costs. Include agent time, telephony, messaging, integration, supervision, refunds or compensation where relevant, and any extra courier charges. If the saved orders would have been delivered anyway, they are not incremental recoveries.

What affects the cost of NDR calling services in India?

Pricing depends on the operating model and scope. Providers may quote per agent or seat, per attempted call, per successfully handled case, or through a hybrid arrangement. Compare the unit definition carefully: a low per-call rate may exclude repeat attempts, follow-up messages, courier portal updates, reporting, quality assurance and supervision.

Before comparing proposals, ask each provider to specify:

• What counts as a billable case, call or productive hour.
• How many attempts and channels are included, and what happens when a customer is unreachable.
• Whether courier status updates and case closure are included or remain the merchant’s responsibility.
• Operating hours, language coverage, escalation ownership and expected response windows.
• Integration, onboarding, training, reporting, quality checks and any minimum monthly commitment.
• Data access, retention, security controls, subcontracting and exit arrangements.

Do not select a provider solely on price per call. A cheaper service that records customer intent but does not complete the courier action can cost more per recovered shipment than a better-integrated workflow.

When should an e-commerce brand outsource NDR calling?

Outsourcing may be worth evaluating when NDR volume fluctuates sharply, internal agents cannot work cases within the available recovery window, language coverage is difficult to maintain, or operations leaders need more consistent follow-up and reporting. It may be less attractive when volume is small, courier workflows are not accessible, order data is unreliable, or the economics cannot support a managed service.

A practical starting point is a bounded pilot across a defined set of products, pincodes or courier lanes. Agree on eligibility rules, scripts, permitted actions, escalation paths, data handling, measurement definitions and a review date before launch. Establish a baseline first; do not promise a fixed RTO reduction before the data demonstrates what is recoverable.

For broader customer communication and delivery-support operations, define the scope against your actual order flow, courier systems, contact volumes and escalation requirements rather than assuming a generic service description will fit.

Vendor checklist for NDR calling services

• Can the provider show how a fresh NDR enters the queue and how a completed action reaches the courier system?
• Are reason-specific scripts available in the languages your customers use?
• Can you audit call attempts, customer instructions, timestamps, agent actions and final shipment outcomes?
• Are recovery, contact, reattempt and RTO metrics defined with clear denominators?
• How are disputed delivery attempts, explicit refusals, cancellations and complaints handled?
• What controls protect customer phone numbers, addresses and order details?
• Can the provider scale up during sale periods without sacrificing contact quality?
• What happens to open cases, recordings, reports and access rights when the contract ends?

How to reduce RTO before an NDR is created

NDR calling is a recovery measure, not a substitute for preventing avoidable delivery failures upstream. Brands that want a sustainable reduction in return-to-origin shipments should review the entire order-to-delivery journey. The most effective improvements often sit across checkout, address quality, customer expectations, courier selection and exception handling.

• Improve address capture at checkout. Ask for the complete address, locality, pincode and a useful landmark where appropriate. Validate formats and pincode coverage before dispatch, and make corrections easy for customers.
• Set clear delivery expectations. Send accurate dispatch and delivery updates, and explain any action the customer may need to take. Avoid unrealistic delivery promises that create frustration or refusal.
• Review COD confirmation carefully. Use proportionate order confirmation for eligible orders, without creating unnecessary friction for genuine customers. Analyse COD and prepaid outcomes separately.
• Use reason codes consistently. Distinguish customer unavailable, incorrect address, refused delivery, phone unreachable and courier-attempt disputes. Combining them into a single “failed delivery” bucket hides the fixes needed.
• Analyse courier and pincode performance. Compare comparable shipment cohorts and review recurring exceptions with logistics partners. A high NDR rate in a lane may require an operational fix rather than more customer calls.
• Close the feedback loop. Send recurring NDR reasons to e-commerce, warehouse, customer experience and logistics owners so the underlying cause can be addressed.

For a wider customer-experience programme, connect NDR handling with the brand’s contact centre operations rather than managing delivery exceptions as an isolated spreadsheet exercise. Also review Mas Callnet’s practical guidance on e-commerce order verification, scaling e-commerce customer support and reducing cart abandonment; these are adjacent parts of the customer journey, not substitutes for NDR outcome tracking.

NDR calling scripts: practical examples

Scripts should identify the brand, explain the delivery exception in plain language and ask for only the information needed to resolve it. Agents should follow the seller’s approved policies and the courier’s supported actions; they should never promise a delivery slot or status they cannot verify.

1. Customer unavailable

“Hello, I’m calling on behalf of [Brand] about order [order reference]. The courier has reported that the delivery could not be completed because nobody was available. Would you still like to receive the order? If yes, what suitable time or date should we request, subject to the courier’s availability?”

2. Address clarification

“The courier has reported a delivery issue with your order. Could you please confirm the relevant address detail or landmark needed to help the courier locate the address? I’ll submit the correction through the approved process, but I can’t guarantee a delivery time until the courier confirms it.”

3. COD order confirmation

“I’m calling about your [Brand] order. The courier has been unable to complete delivery. Do you still want to receive this order and pay the stated amount on delivery? If you no longer want it, I can record that accurately and explain the next step under the seller’s policy.”

4. Disputed delivery attempt

“Thank you for letting us know. I’ll record that you dispute the delivery attempt and send it to the relevant team for checking. I won’t mark the issue resolved until the status has been reviewed.”

These examples are starting points, not scripts to use without review. Adapt them to the brand, language, consent and contact rules, courier process, product category and escalation policy. Keep the tone neutral and avoid pressuring customers into accepting unwanted orders.

Technology and reporting needed for an NDR operation

A reliable NDR calling service needs more than a dialler and a list of phone numbers. The workflow should make the current shipment status, contact history, customer instruction and next operational action visible to authorised staff.

Capability	Why it matters	What to verify
Courier or shipping-platform integration	Prevents agents from working on stale cases and helps record the right next action.	Supported data fields, update permissions, error handling and sync frequency.
Case queue and prioritisation	Helps teams work fresh, eligible NDRs before the recovery window closes.	Ageing, owner, retry rules, escalation and duplicate-case handling.
Disposition and reason codes	Makes it possible to separate contact outcomes from actual shipment outcomes.	Standard definitions, mandatory fields and audit history.
Quality assurance	Reduces inaccurate promises, poor conduct and incomplete case notes.	Sampled call reviews, coaching, complaint flags and corrective action.
Outcome dashboard	Connects intervention effort with delivery and cost results.	Cohort dates, denominator definitions, courier status maturity and export access.
Access and data controls	Protects phone numbers, addresses, order information and recordings.	Role-based access, retention, secure transfer, vendor access review and deletion on exit.

Before a live launch, test edge cases: duplicate NDR events, unreachable customers, a customer who changes their mind, a courier status that updates late, a disputed delivery attempt and an API or portal failure. Define who owns the case when the normal workflow breaks.

How to run a credible NDR pilot

1. Baseline the current process. Record eligible NDR volume, reason mix, contact rate, final delivery rate, RTO rate, customer complaints and current handling cost over a representative period.
2. Define the target cohort. Select the couriers, pincodes, order categories or reason codes to test. Exclude cases that cannot be actioned or for which contact is not permitted.
3. Agree service rules. Document first-contact timing, number of attempts, working hours, approved channels, script versions, data fields, escalation paths and who can request courier changes.
4. Choose a fair comparison. Where feasible, compare the pilot with a similar holdout group or use a phased rollout. Account for seasonality, courier, pincode, payment mode and product mix.
5. Track final outcomes. Wait for shipment statuses to mature. Count recovered shipments only when the delivery outcome is confirmed, not when the customer answers or agrees to a reattempt.
6. Calculate the full economics. Include staffing, telephony, messaging, technology, supervision, integration, additional delivery charges and the contribution margin of incremental completed orders.
7. Decide using evidence. Scale only if the pilot improves the agreed outcomes without an unacceptable increase in complaints, customer friction, data risk or cost per incremental recovery.

Common mistakes that weaken NDR recovery

• Calling too late: the courier may already have closed the reattempt window or initiated RTO.
• Counting activity instead of outcomes: calls attempted, customers reached and reattempt requests are intermediate measures, not proof of successful delivery.
• Using one script for every reason: a customer unavailable, a wrong address and an explicit refusal require different responses.
• Failing to update the courier: the customer may confirm availability, but the parcel will not necessarily be reattempted unless the supported workflow is completed.
• Over-contacting customers: excessive calls or messages can cause complaints and harm the brand. Apply approved attempt limits and honour valid contact preferences.
• Ignoring false or disputed scans: a call centre cannot solve a courier process problem by persuading the customer to accept blame. Escalate disputed attempts for verification.
• Reporting without a clear denominator: an apparent improvement can be misleading if the team compares different shipment populations or ignores outcomes that have not matured.
• Promising a fixed RTO reduction upfront: recoverability varies by reason, courier, product, location, payment mode and customer intent. Establish a baseline and validate results first.

Frequently asked questions

What does NDR mean in e-commerce?

NDR means Non-Delivery Report. It records that a courier delivery attempt did not result in the parcel being handed to the customer, along with a reason or status that helps determine the next action.

What is the difference between NDR and RTO?

NDR is a failed-delivery exception. RTO means Return to Origin: the undelivered shipment is returned to the seller. An NDR may be resolved with a successful reattempt, but some cases still become RTO.

Can NDR calling guarantee lower RTO?

No. Calling can resolve some preventable failures, such as customer unavailability or missing address details, but it cannot fix every problem. Courier capacity, false or disputed attempt statuses, customer refusal and inventory or policy issues can still prevent delivery.

When should a customer be contacted after an NDR?

As soon as the NDR is received and while a reattempt can still be requested. The correct service window depends on the courier’s process and the shipment’s current status, so brands should agree on an operational SLA rather than assume one universal deadline.

Is NDR calling mainly for COD orders?

COD orders often require special attention because the customer has not prepaid, but prepaid shipments can also fail because of address issues, unavailability or courier exceptions. Segment results by payment mode instead of excluding one group automatically.

Should NDR calling be done by humans or AI?

Simple reminders and confirmations may be automated when the workflow supports it. Human agents are useful for ambiguity, complaints and address clarification. A hybrid model can route routine cases to automation and complex exceptions to agents.

What should be the main KPI for an NDR calling team?

Use NDR-to-delivery recovery rate as a core outcome measure, supported by contact rate, reattempt acceptance, NDR-to-RTO rate, cost per recovered shipment and complaint rate. No single metric explains performance on its own.

How can an e-commerce brand calculate NDR recovery ROI?

Compare incremental completed deliveries against a credible baseline, multiply by contribution margin per completed order, then subtract intervention and additional fulfilment costs. Do not count customer confirmations as recovered revenue until delivery is confirmed.

What data is needed to start an NDR calling programme?

At minimum, use a unique order and tracking reference, current NDR reason and timestamp, customer contact details permitted for the task, courier status, approved scripts and a way to record actions and final outcomes. Restrict access to what agents need.

How should a brand choose an NDR calling provider?

Evaluate workflow integration, speed of first contact, language coverage, quality assurance, final-outcome reporting, security controls, escalation ownership and total cost per recovered shipment. Ask for a pilot with agreed measurement definitions before scaling.

Discuss your e-commerce delivery-support requirements

If failed delivery attempts are creating repeat customer-service work or avoidable logistics cost, start by reviewing your NDR volumes, reason codes, courier mix and final shipment outcomes. MasCallNet can discuss the customer-contact and contact-centre scope that may fit your operation. Discuss your requirements with MasCallNet.