Skip to content

Bananaflow MCP is live.

Read the docs

Use case: abandoned cart calls

Abandoned cart recovery calls: an AI agent that phones the shopper who left

When a cart is left behind, your store, n8n or Zapier starts a Bananaflow call through the API. The agent asks what stopped the order, in the shopper's language, and sends the answer back to your system.

Line diagram in white over a soft, out-of-focus alstroemeria in muted rose, with peach and pink veils at the edges around a calm rose centre: a cart panel labelled cart left behind runs into a phone panel labelled recovery call; from the call a solid line rises to a shopping bag panel with a tick, labelled back to checkout, and a dashed line falls to a pill reading needs a person. The call either brings the shopper back to checkout or hands them to your team.

What is an abandoned cart recovery call?

An abandoned cart recovery call is a phone call to a shopper who left items in an online cart without paying, made to find out what stopped the order and help them finish it.

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

Why a fast first call matters for any lead: speed to lead.

The wider job on e-commerce calls: AI voice agents for e-commerce.

Sources for the key facts: Baymard Institute's cart abandonment rate statistics and the Standard Webhooks overview, read on 15 November 2026.

How does an abandoned cart call go, step by step?

In five steps: a cart is left behind, your store starts the call, the agent greets the shopper with the items, answers what is in the way and the outcome goes back by webhook.

  1. A cart is left behind

    Your store, or an n8n or Zapier flow you run, sees a shopper leave without paying and decides when to ask for a call.

  2. Your store starts the call

    It calls the Bananaflow API with the shopper's phone number and the cart: name, items and any detail you want the agent to use.

  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 cart does not ring the shopper twice.

  4. The agent greets with the cart

    It names the items in the shopper's language and asks what stopped the order, whether a question, a worry or just a busy moment.

  5. The agent answers and notes the outcome

    It answers from your product details, can look up a product in your own system through an HTTP tool, and records whether the shopper wants to buy, needs help or is not interested.

  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 CRM, n8n or Zapier for your team to follow up.

An example call

Agent
Namaste Priya ji, Gharana Home se bol rahe hain. Aapne soy candle ka gift set cart mein rakha tha, par order complete nahi hua. Kya kuch poochna tha?
Priya
Haan, mujhe pata nahi tha ki ye Pune mein kitne din mein pahunchega.
Agent
Pune ke liye delivery ka estimate order page par dikhta hai, aur main aapko wahi bata sakta hoon jo hamare system mein hai. Kya aap order complete karna chahengi?
Priya
Haan, aaj raat tak kar dungi.
Agent
Theek hai, maine note kar liya ki aap aaj raat tak order complete karengi. Aur kuch poochna hai?
Priya
Nahi, bas. Thank you.

Priya, the store and the cart are made up for this example.

One recovery call in five steps. Your store or automation tool starts the call when a cart is left behind. The agent does the plum steps: it greets the shopper with the items in the cart, answers what is in the way and notes what they want. The outcome goes back by webhook.

What does the agent need to make recovery calls?

A way for your store to start calls by API, a short workflow for the call, product answers it can use, the languages your shoppers speak and a webhook for the outcome.

Where do the results of a recovery call go?

During the call the agent can look up a product through an HTTP tool, and after it a webhook sends the outcome and what the shopper said to your CRM, n8n or Zapier.

  • A shopper who will buy

    The outcome code says so, with what stopped the order, and your system can start your own follow-up while the shopper is still interested.

  • A question to answer

    When the shopper asks something the agent cannot settle, the question is saved in the transcript and sent with the outcome for your team.

  • A reason you can count

    Because every call carries an outcome code, you can count the reasons shoppers give, such as delivery time, price or a second thought, week by week.

  • 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 carts still need a person.

Where the result of a recovery call lands. During the call the agent can look up a product in your store system through an HTTP tool. After it, a webhook sends the outcome and what the shopper said to your CRM, or to an n8n or Zapier flow your team already runs.

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 abandoned cart calls cost in rupees?

For the example's 3,900 recovery calls of 2 minutes each, 7,800 minutes cost Rs 31,200 on pay as you go, before GST.

  • Calls a month

    150 a day on 26 working days: 3,900 calls

  • Minutes per call

    2 minutes

  • Minutes a month

    7,800 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 a recovery call in your shoppers' language first? Build one in the browser and call it yourself.

Industries: AI voice agents for e-commerce.

Solutions: AI outbound calls.

Playbooks: speed to lead and COD order confirmation calls.

Failed deliveries by phone: NDR calls.

Every job the agent does on calls: AI voice agent use cases.

FAQ

What do teams ask about abandoned cart calls?

  • What is an abandoned cart recovery call?

    An abandoned cart recovery call is a phone call to a shopper who left items in the cart without paying, to find out what stopped the order and help them finish it.

  • How does the call start from our store?

    Your store, or an n8n or Zapier flow, calls the Bananaflow API with the shopper's phone number and the cart details. The agent uses the name and the items in what it says.

  • Who decides when the call is made?

    Your store or automation tool. The call starts when your system sends the request, so you choose the moment, and the call keeps your calling hours.

  • Could a shopper get two calls for one cart?

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

  • Where does the shopper's answer go?

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

  • Can the agent answer product questions?

    Yes. Give it your product, shipping and returns answers in a knowledge base, and it can look up a product in your own system through an HTTP tool during the 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 shopper's language from their first clear sentence and can switch mid-call.

  • What do abandoned cart 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