An AI agent that answers product questions before purchase is not a support cost, it is a conversion channel. The customer standing on your product page with a specific question about sizing, compatibility, or stock is closer to a sale than any retargeted ad will bring back. Answer the question in seconds and a chunk of them buy. Leave them hanging for two hours by email and most quietly move on.
The pre-purchase question is a buying signal
The most common use of live chat is not returns or complaints. It is pre-purchase product questions. Tidio's live-chat data puts pre-sales queries at about 43% of chat volume across ecommerce sites, well above post-purchase support. That matches the shape of the funnel: more browsers than buyers, more questions than complaints.
Forrester research widely cited across ecommerce studies puts the abandonment cost bluntly: 53% of US online adults are likely to abandon a purchase if they cannot find a quick answer to their question. Half your undecided shoppers walk away because a specific question, one that a member of your team could answer in a sentence, went unanswered.
Baymard Institute's 2026 cart abandonment tracker sits the average online abandonment rate at 70.22%, with the top actionable causes being extra costs too high (48%), forced account creation (26%), a checkout that is too long or complicated (22%), and untrustworthy payment presentation (18%). Unanswered questions do not always show up in the "top reason" list because the shopper leaves before they can be surveyed. But every store operator knows the pattern from session recordings: hover on the size chart, hover on the shipping estimate, leave.
Why AI fits this job specifically
Pre-sales questions have a shape that suits automation:
- They repeat. A single product page will attract the same handful of questions from a hundred different shoppers.
- They are timing-sensitive. A three-hour reply is functionally no reply, because the shopper has left.
- They are grounded in known content: your product data, your shipping policy, your stock. The correct answer exists in a database, not in a support agent's head.
- The upside is asymmetric. A fast, correct reply often closes the sale. A slow reply usually loses it.
That is the definition of a task where AI beats human staffing, not on quality but on latency and cost per interaction. And where AI is a bad fit, complex sizing consultations, high-touch B2B qualification, the same agent can hand off to a human with the context intact.
What pre-sales AI actually needs to know
Three sources of truth make or break a pre-sales agent.
Product data, live
The agent should read from your product feed, not a copy pasted into an FAQ. Titles, variants, sizes, materials, weight, dimensions, images, price. When a shopper asks "does the medium fit a 32-inch waist", the agent should answer from the same table your storefront reads from, not from a training document that is six weeks stale.
Stock and availability, live
Nothing damages trust faster than "yes we have that in stock, let me get you the link" followed by an out-of-stock page. If your inventory changes daily, so should the agent's view of it. Same for restock ETA when you offer one.
Policy, current
Shipping cost by country, delivery window, return window, warranty, exchange rules. These change more often than most teams think, and every change should propagate to the agent within the hour, not the quarter.
Ground the agent in these three sources and it can answer nine out of ten pre-sales questions correctly on the storefront. The tenth is where a human takes over.
The five questions to automate first
Not every pre-sales question is worth wiring up on day one. Start where the volume and conversion impact are highest.
- "Do you have this in my size / this variant?" Highest volume, clearest answer, direct link to add-to-cart.
- "How long will shipping take to my country?" Second-highest, and the answer often decides the sale.
- "What is your return policy?" Trust question. A confident, plain answer converts hesitant shoppers.
- "Is this compatible with X?" For accessories, electronics, and parts. Compatibility questions have very high sale value.
- "When will this be back in stock?" Cheapest form of retention: capture the email, notify on restock.
The remaining long tail (fabric care, ingredient sourcing, gifting options) is worth automating after these five are working well and you have a month of data on where they succeed and fail.
Guardrails: what the agent should refuse
An AI that will say anything to close a sale is not a benefit, it is a liability. Pre-sales specifically has three failure modes that need explicit guardrails.
The first is inventing compatibility. If the source data does not confirm a phone case fits a specific model, the agent should say so and offer to check with a human, not guess. This is exactly the hallucination failure mode that grounded retrieval is built to prevent.
The second is quoting outdated prices or promos. Only current data, cited to the source. If a promo has ended, the agent must not carry it forward from stale training.
The third is making delivery promises the fulfilment side cannot keep. "It'll be there by Tuesday" from an agent is a customer expectation, not a guess. If the shipping window is a range, the agent should give the range.
Comparison: three ways to answer pre-sales questions
| Approach | Speed | Accuracy | Cost per answered question | Fits an SMB | |---|---|---|---|---| | Human live chat only | Fast when staffed, slow off hours | High | High: agent time per question | Only if staffed 24/7, which is rare | | Static FAQ page | Instant if the shopper reads it | High if maintained, brittle if not | Very low | Yes, but leaves questions unanswered | | AI agent with live product data and human handoff | Under 10 seconds | High when grounded in your data | Low per reply, scales with volume | Yes, this is the pattern most stores are converging on |
The winning pattern is the third: AI handles the routine pre-sales flood on the storefront, a human picks up when the question needs judgement, the FAQ page still exists but stops being your only line of defence.
What to measure
Pre-sales AI has a different metric set than post-sales support. The interesting numbers are:
- Conversion on chatted sessions vs unchatted. Aggregate live-chat data across ecommerce puts chat-to-conversion in the 10 to 20 percent range, versus 2 to 3 percent for form fills. Your ratio will vary, but the gap should be visible from week one.
- Add-to-cart events attributed to the agent. If the agent surfaces a product link and the shopper adds it to the cart within the session, count it.
- Handoff rate and handoff outcome. How often does the AI defer to a human, and does that conversation still close?
- Time-to-answer distribution. Not average. The 90th percentile matters more; that is where the leaks happen.
- CSAT on pre-sales conversations specifically. Pre-sales CSAT tends to run higher than post-sales because the shopper's expectations are different. Track it separately.
Do not confuse this with a deflection rate target. Deflection is the wrong frame for pre-sales; you want the shopper to interact more, not less. What you want to deflect is the shopper leaving without buying.
The role of the widget itself
An AI agent that lives in a corner of the site, waiting to be clicked, is fine. An agent that proactively surfaces on the product page after a delay, with a specific offer to answer sizing or compatibility questions, converts more. This is not aggressive pop-up behaviour; it is contextual help, the equivalent of a store associate who notices you looking at the shelf for the second time. The chat widget is the surface where this lives.
Every proactive surfacing is a design choice with a cost, though. Bad triggers annoy shoppers into leaving faster. The rules that work are simple: trigger on a specific page after a specific dwell time, offer a specific help, do not chase the cursor around.
Where this connects to the rest of your support stack
Pre-sales AI is not a separate product from post-sales support. The same agent, grounded in the same content, extended with your product and inventory data, answers the "when will this arrive" question before purchase and the "where is my order" question after. Splitting them into two systems means splitting your quality signal, your data, and your team's attention.
For Shopify stores, the connection is direct: the agent reads product, inventory, and order data from the same connected source. See our Shopify support setup guide for the shape this takes on a real store, and our piece on WISMO automation for the post-purchase side.
How Keloa approaches pre-sales AI
Keloa's AI agent reads live product data, inventory, and policy from your store, and answers pre-sales questions on the same widget that handles post-sales support. Grounded retrieval means the answer cites your source content, so the shopper trusts it and your team can audit it.
Handoff to a human keeps the full conversation and page context in a unified inbox, so sales-adjacent conversations do not fall between customer service and sales teams. Per-reply pricing means high-volume pre-sales days do not produce surprise bills, and the AI economics stay honest whether it is a Tuesday or Black Friday.
For teams looking at the wider ecommerce case, our ecommerce solutions page and the sales solutions page map the pattern to specific store types.
Frequently asked questions
Will an AI agent hurt conversion by seeming impersonal? Not when it answers the question quickly and correctly. Data from live-chat platforms consistently shows chat sessions convert several times better than sessions with no chat, whether the reply comes from a human or an AI. The impersonality complaint usually traces back to bad replies, not to the fact of automation.
Should the AI actively recommend products? Cautiously. Recommending in response to a specific question ("which of your two backpacks fits a 15-inch laptop") is welcome. Unprompted upselling is not. Answer what was asked first, and only suggest alternatives when the answer to the original question is no.
What happens if the AI does not know? It should say so and offer a handoff. The failure mode to avoid is confident guessing. A grounded agent will decline rather than invent, then route the conversation to a human with the full context, so the customer only explains themselves once.
How do we measure the sales impact of the AI? Compare conversion on sessions where the shopper engaged the AI to sessions where they did not, controlled for traffic source. Attribute add-to-cart events that follow an AI-surfaced product link. Track the handoff-to-close rate on conversations the AI escalated. Together these give a defensible number for the AI's contribution to revenue.
Can one AI handle both pre-sales and post-sales? Yes, and it should. The knowledge sources overlap heavily (product, policy, delivery), the customer often has both kinds of question in one conversation, and splitting the agent doubles the maintenance load with no benefit. One agent, two intents, one inbox.
Does this work outside Shopify? Yes. The pattern requires a product feed, an inventory source, and a policy library. That exists in almost every store platform. The examples in this piece use Shopify because it is common, but the underlying setup applies to WooCommerce, custom stacks, and headless commerce equally.