Skip to content

Bananaflow MCP is live.

Read the docs

Use case: NDR calls

NDR calls: an AI agent that phones the customer after a failed delivery

When a delivery attempt fails, your store starts a Bananaflow call with the order details. The agent asks the customer what to do, in their language, and sends the outcome back to your system.

Line diagram in white over a soft, out-of-focus protea in muted rose, with aqua and pink veils at the edges around a calm rose centre: a parcel panel marked with a cross, labelled failed delivery, runs into a phone panel labelled NDR call; from the call a solid line runs to the highlighted pill deliver tomorrow, and dashed lines to the pills new address and return it. The customer decides on the call what happens to the parcel.

What is an NDR call?

An NDR call is a phone call to a customer whose delivery attempt failed, made to find out why and agree what happens next: deliver again, change the address or send the parcel back. The name comes from the courier's non-delivery report, which is raised when an attempt fails.

A Bananaflow agent makes the call the moment your store, n8n or Zapier asks for it through the API, with the customer's name, the order and the reason in the call. When it ends, the outcome and what the customer said go back to your system by webhook.

What NDR stands for, the usual reasons and what a return costs you: NDR in e-commerce, explained.

What happens to the parcel when the customer cannot be reached: RTO in e-commerce.

Sources for the key facts: Delhivery's help centre page on the Non-Delivery Report and the Standard Webhooks overview, read on 15 November 2026.

How does an NDR call go, step by step?

In six steps: a delivery fails, your system starts the call, the agent greets the customer with the order, asks what to do, updates your system and the outcome goes back by webhook.

  1. A delivery attempt fails

    Your store, or an n8n or Zapier flow you run, receives the failed attempt, with the courier's reason, from the tools you already use.

  2. Your system starts the call

    It calls the Bananaflow API with the customer's phone number and the order details: name, order, items and the courier's reason.

  3. The call waits for a free line

    The call queues until a line is free, keeps the calling hours you set, and a repeated request for the same failed delivery does not ring the customer twice.

  4. The agent greets by name

    It names the order and the reason in the customer's language, and asks what they want: deliver again, a new address or a return.

  5. The agent updates your system

    It writes down the new day or the new address, and an HTTP tool can record the change in your own store system while the customer is on the line.

  6. The outcome goes back by webhook

    The call ends with an outcome code, the transcript and the details gathered, and a webhook sends them to your system for your team or courier workflow to act on.

An example call

Agent
Namaste Sunita ji, Neelam Threads ki taraf se. Aapka kurta set kal deliver nahi ho paya, kyunki ghar par koi nahi tha. Kya main aapse kuch minute baat kar sakta hoon?
Sunita
Haan boliye.
Agent
Hum kal dobara deliver kar sakte hain. Kal kis time par koi ghar par hoga?
Sunita
Kal shaam ko 6 baje ke baad theek rahega.
Agent
Theek hai, kal shaam 6 baje ke baad ka note kar liya. Address wahi rahega, Nagpur, Dharampeth wala?
Sunita
Haan, wahi hai. Thank you.

Sunita, the store and the order are made up for this example.

One NDR call in six steps. Your system starts the call when a delivery fails. The agent does the plum steps: it greets the customer with the order and the courier's reason, asks what to do and updates your own system. The outcome goes back by webhook.

What does the agent need to make NDR calls?

A way for your store to start calls by API, a short workflow for the call, the languages your customers speak, a phone number on your carrier and a webhook for the outcome.

Where do the results of an NDR call go?

During the call the agent can update your own store system through an HTTP tool, and after it a webhook sends the outcome and the details the customer gave to your CRM, n8n or Zapier.

  • A new delivery day

    When the customer picks another day, the agent records it as a value the webhook carries, and your team or courier workflow books the reattempt.

  • A corrected address

    When the address was wrong, the agent asks for the right one, reads it back and sends it with the outcome.

  • A return the customer chooses

    When the customer no longer wants the order, the outcome code says so, and your system starts the return before the parcel goes round again.

  • Calls nobody answers

    Your system can ask for a status update on each call, including when it was not answered or the line was busy, so your team sees which failed deliveries still need a person.

Where the result of an NDR call lands. The agent updates your own store system during the call through an HTTP tool, and a webhook after it sends the outcome to your CRM, an n8n flow or any system that takes a webhook.

How the outcome codes, transcripts and reports work: Call outcomes, webhooks and reports.

What the agent can connect to during a call: Apps and tools the agent connects to.

What would NDR calls cost in rupees?

For the example's 5,200 NDR calls of 2 minutes each, 10,400 minutes cost Rs 41,600 on pay as you go, before GST.

  • Calls a month

    200 a day on 26 working days: 5,200 calls

  • Minutes per call

    2 minutes

  • Minutes a month

    10,400 minutes

This is an example of minutes, not a quote: the number of calls and their length are the example's assumptions. All prices are in rupees, before 18% GST. The rate covers speech-to-text, the language model and the voice, and your carrier bills calls separately. Every plan is on Bananaflow pricing in rupees.

Want to hear an NDR call in your customers' language first? Build one in the browser and call it yourself.

FAQ

What do teams ask about NDR calls?

  • What is an NDR call?

    An NDR call is a phone call to a customer after a failed delivery attempt, to find out why and agree whether to deliver again, change the address or return the order. NDR is short for non-delivery report.

  • How does a failed delivery start the call?

    Your store, or an n8n or Zapier flow you run, calls the Bananaflow API with the customer's phone number and the order details. The agent uses the name, the order and the courier's reason in what it says.

  • Could the customer get two calls for one failed delivery?

    No. A repeated request for the same call does not ring the customer twice, and calls wait for a free line and keep the calling hours you set.

  • Where does the answer the customer gives go?

    To your system, by webhook. When the call ends, the outcome code and the details the agent gathered, such as the new day or the new address, are posted to your CRM, n8n or Zapier.

  • Can the agent change the order in our system during the call?

    Yes, through an HTTP tool pointed at your own system's API with your key, for example to record a new delivery time. Anything your API accepts, the agent can call.

  • Which languages can it call in?

    English and 10 Indian languages: Hindi, Bengali, Gujarati, Kannada, Malayalam, Marathi, Odia, Punjabi, Tamil and Telugu. It follows the customer's language from their first clear sentence and can switch mid-call.

  • Can we call a list of failed deliveries at once?

    Yes. Upload the list as a CSV and run it as a campaign within the calling hours you set, with retries when nobody picks up.

  • What do NDR calls cost in India?

    Bananaflow costs Rs 4.00 a minute pay as you go, Rs 3.50 on Growth, Rs 3.00 on Scale and from Rs 2.50 on Enterprise. All prices are in rupees, before 18% GST. The rate covers speech-to-text, the language model and the voice, and your carrier bills calls separately.

Bring us one process. We'll pilot it on your real calls, with your team as the fallback.

Plan a pilot