The short answer
Standard abandonment analysis attributes carts to price, shipping cost and checkout friction, because those are the things analytics can see. A meaningful share is an unanswered question - sizing, delivery to a pincode, COD availability, return eligibility - asked at a moment when nobody was available to answer it. Those carts are recoverable in seconds, not with a discount.
Every abandonment report you have read blames the same things: unexpected shipping cost, a long checkout, forced account creation, a payment method that failed. Those are real, and they have a useful property for analysts - they leave traces. A cart abandoned because nobody answered a question leaves no trace at all, which is why it almost never appears on the list.
The moment the cart dies
Watch one customer through it. She has added a kurta to the cart at 9:40pm. Before paying she wants to know one thing: whether it will reach Nagpur before the 20th, because it is a gift. Your shipping page says 'metro cities 2-4 days, rest of India 4-7 days', which does not answer her question about the 20th and she is not going to do the arithmetic on your behalf.
So she opens the chat and asks. If an answer comes back in four seconds - here is the timeline for your pincode, order by tomorrow and it arrives on the 18th - she pays. If nothing comes back, she does not sit with the tab open until morning. She closes it, and by the time your reply arrives at 9:30am the decision was made twelve hours ago.
In your analytics this is an abandoned cart at 9:41pm. It gets attributed to whatever bucket your tool defaults to. Nothing in the data says a question was asked and not answered.
A discount is what you offer when you do not know why they left. Most of the time they left because nobody answered.
The questions that actually block a purchase
They are not exotic, and they are remarkably consistent across Indian stores. What they share is that each one is genuinely blocking - the customer cannot sensibly buy until it is resolved.
| The blocking question | Why it stops the purchase | Where the answer already lives |
|---|---|---|
| Will it reach my pincode by a date? | The purchase has a deadline | Shipping policy, if written by region |
| Is this actually in stock in my size? | A cancellation later is worse than not ordering | Catalogue or size chart |
| Can I return it if it doesn't fit? | Fit risk is the main reason apparel carts stall | Returns policy |
| Is COD available on this order? | Card-shy buyers will not proceed without it | Payments FAQ |
| Can I get a GST invoice? | B2B buyers cannot expense it otherwise | Payments FAQ |
| Does the sale price apply to this item? | Nobody pays full price by accident | Sale terms document |
Every answer in that right-hand column is something you have already written or could write in ten minutes. The failure is not that you lack the answer. It is that the answer was not available at 9:40pm in the customer's own words.
Why the FAQ page does not cover this
The reflex fix is to write a better FAQ page and link it from the cart. It helps a little and it does not solve the problem, for two reasons.
The first is that a customer with a specific question does not want a document, they want an answer. 'Metro cities 2-4 days' is a policy; 'it reaches Nagpur on the 18th if you order tomorrow' is an answer. The gap between those two is exactly the work the customer has to do themselves, and at 9:40pm they will not.
The second is that FAQ pages are written to reassure browsers, not to answer queries. They accumulate marketing sediment - phrases like 'we pride ourselves on fast delivery' that state nothing checkable. Rewriting them into retrievable facts is worth doing regardless, and it is what makes the instant answer accurate.
Estimating what this costs you
You cannot measure the unasked question directly, but there is a usable proxy sitting in your own inbox.
- Export a month of support messages and keep only pre-purchase questions - sizing, delivery, returns eligibility, payment.
- Split them by time of day. The share arriving after 8pm is the share nobody was available for.
- Compare that against your abandonment rate in the same hours. If evening abandonment runs higher than daytime, the difference is your unanswered-question tax.
- Multiply by average order value. That number is usually large enough to end the discussion about whether this is worth fixing.
What answering in seconds actually changes
Three things, and only the first is the obvious one. Carts that would have died convert, because the blocking question stopped blocking. Your morning inbox stops opening with thirty pre-purchase questions that are now irrelevant, since the customers who asked them have already decided one way or the other. And the questions the agent could not answer become a list of exactly which facts your product pages are missing - which is a far better content roadmap than guessing.
The placement that matters is the product page and the cart, because that is where blocking questions occur. Leaving the widget on the policies page helps too: a customer reading your returns policy has a returns question, and answering it in their words beats making them parse yours.
The e-commerce walkthrough lists the five documents that cover this, the Shopify setup guide is the fifteen-minute version, and the free plan is enough to test whether evening carts behave differently once someone is answering.
Frequently asked questions
What share of abandoned carts are caused by unanswered questions?
It is not directly measurable, because an unasked question leaves no trace. The usable proxy is your own support inbox: count how many pre-purchase questions arrive outside business hours, then compare that against your abandonment rate in the same window.
Which questions block a purchase most often?
Delivery to a specific pincode, whether a size or variant is genuinely in stock, COD availability and limits, return eligibility on sale items, and whether a GST invoice is available for business buyers.
Does a chat widget hurt page speed or SEO?
It should not. The VaaniAPI widget is under 50KB and loads asynchronously, so it does not block rendering and does not affect crawlable content.
Where should the widget appear?
Product pages and the cart, which is where blocking questions occur. Leaving it on the policies page also helps - a customer reading your returns page has a returns question.
