Most carts are abandoned. The figures quoted in ecommerce hover around seven in ten, and the standard response is to treat it as a checkout problem: fewer fields, more payment methods, a reminder email an hour later.
Some of it is a checkout problem. A good part of it is not. It is a question that arrived on the product page, went unanswered, and turned a buying decision into a maybe. The cart is where that shows up in the report, which is why it keeps getting fixed in the wrong place.
Four places a question arrives
The same product page, four moments of doubt. Each one has an answer that already exists somewhere on your site.
Notice what none of those four are. None is a complaint about price, and none is a checkout field. They are all requests for a fact you already published somewhere else on the site.
Why the page cannot answer them on its own
A product page is written once, for everybody. The questions arrive one at a time, from one person, about their situation: their size, their date, their country, their previous order.
You can add more copy, and shops do, until the page becomes an essay nobody reads and the answer is buried in paragraph nine. The size guide is two clicks away, the returns policy is in the footer, the shipping cut-off is on a different page entirely. Each of those clicks is an exit.
The information is not missing. It is one page away, at the exact moment somebody stopped being willing to look for it.
What changes when the page can answer
An assistant on a product page is not there to sell. It is there to close the gap between a question and the sentence in your own material that answers it, without the shopper leaving the page.
Three things follow from that, and they matter more than the chat window itself.
- The answer arrives in the same place the doubt did. No new tab, no search, no footer.
- It cites where it came from, so a shopper who wants the exact policy can open it.
- It says when it does not know, which on a shop means it does not invent a delivery date or a stock level it was never given.
That last one is the boundary worth being explicit about. An assistant answers from your published material: descriptions, policies, shipping tables, the questions you have already answered by email a hundred times. It does not see live stock or a specific order unless it has been given that connection, and a shop that pretends otherwise creates a worse problem than the one it solved.
welcomeai.devAI chatbot for ecommerce, answering on the product pageThe eight answers to write first
Not a content project. Eight short answers, most of which exist as sentences you have already typed into a support reply.
- Is the price the final price, and what is added at checkout?
- What is the delivery cut-off for arriving by a given date?
- Where do you ship, and what does it cost from each threshold?
- Does it run large or small, and what do the measurements mean?
- Who pays for a return, and how long does the refund take?
- What is the warranty, and what voids it?
- Is it in stock in this variant, or when does it come back?
- What comes in the box?
Write them plainly, each under its own heading, each self-contained. That is useful to shoppers who never open a chat window, and it is what makes an assistant accurate when they do.
After two weeks, the list of questions your assistant could not answer is the most valuable page in the admin. In a shop it is usually short, specific and embarrassing: one sizing question, one shipping country, one variant nobody documented.
Questions people ask
Take last month's abandoned carts and ask a different question of them: not what people failed to complete, but what they were trying to find out. The list is usually four or five facts long, and you have written every one of them already.
welcomeai.devHow to build an AI knowledge base for your business
