What is an ecommerce chatbot?

A widget on your store that answers common questions from uploaded documents or structured content, then hands off to a human when the answer is missing or the issue needs judgment. It deflects repeat FAQs. It does not replace reviews, checkout fixes, or staffed WhatsApp.

What should an ecommerce chatbot handle first?

Shipping timelines, return windows, sizing or materials, order status wording, and product care. Those repeat across sessions. Custom builds, chargebacks, and angry refunds should escalate.

Do I need AI for an ecommerce chatbot?

Many stores use document-backed AI so shoppers can ask in plain language. The model reads your PDF, CSV, or TXT files. If your files are wrong, the bot will be wrong. Accuracy beats fancy prompts.

Can a chatbot recommend products?

Some tools try. For most stores, product discovery belongs on the product page and in search. A bot that guesses SKUs creates wrong orders. Pick tools that stay in policy and FAQ territory unless you have a catalog you trust the model with.

When should I not add an ecommerce chatbot?

Skip it when policies are unfinished, nobody monitors escalations, or every sale needs human judgment. Wix-specific skip list: /blog/when-not-to-use-ai-chatbot-wix/.

How is AI chat different from WhatsApp on a store?

AI chat deflects documented FAQs. WhatsApp is staffed click-to-chat on a channel customers already use. They solve different problems. Do not install both as primary paths without a clear rule for which wins.

Ecommerce Chatbot Guide for Online Stores

An ecommerce chatbot answers repeat questions on your store from a knowledge base and escalates to a human when the answer is missing or the issue needs judgment. It pays off when shipping, returns, sizing, and product care are written down and someone watches handoffs. It fails when policies are half-finished or nobody replies after escalation. This page is the category hub across platforms.

Wix product page: Wix AI chatbot. Wix pick: best AI chatbot for Wix. Model path: AI chatbot Gemini. Files: AI chatbot with knowledge base. Skip cases: when not to use an AI chatbot on Wix. Product FAQs: chatbot product questions on Wix.

What an ecommerce chatbot is for

The job is support deflection, not sales theater. Shoppers ask the same pre-purchase and post-purchase questions every week. A bot that reads your documents can answer those without tying up email or DMs.

Pre-purchase: shipping cost logic, delivery windows, materials, sizing notes
Post-purchase: return steps, warranty wording, how to track
Store policy: privacy, subscriptions, international duties when documented
Not a fit: custom quotes, medical claims, high-risk refunds without a human

Research on self-service support consistently shows customers prefer fast answers for simple issues when the answers are accurate. That is the bar. A wrong bot is worse than a FAQ page.

Use cases that pay off

Scenario	Bot fit	Notes
Repeat shipping and returns questions	Strong	Keep one canonical policy doc
Sizing and materials on apparel or gear	Strong	Update when SKUs change
Where is my order	Medium	Link to tracking; do not invent statuses
Which product should I buy	Weak	Use product pages and filters instead
Chargeback or angry refund	Escalate	Human judgment required

Knowledge base setup

Document-backed bots answer from files you upload. Treat the knowledge base like inventory: stale files produce stale answers.

Files that work

PDF: policies, care guides, long FAQ exports
CSV: SKU tables with size, material, weight, lead time
TXT: short canonical answers you want repeated verbatim

Rules that keep answers honest

One source of truth per topic. Do not upload three conflicting return policies.
Date your files or version them when seasons change.
Remove discontinued products from CSV knowledge.
Test ten real shopper questions before you go live.

File structure for product FAQs: AI chatbot with knowledge base. Product-question prep: chatbot product questions on Wix.

Human escalation

Every ecommerce chatbot needs a clean handoff. Escalation is not failure. It is how you keep refunds and edge cases out of automation.

Define triggers: missing KB answer, angry tone, custom order, payment dispute
Assign an owner during buying hours
Mark conversations resolved when done so queues stay honest
Review escalations weekly and feed fixes back into documents

Important

A bot with no escalation owner trains customers to distrust every answer. Monitor the queue or keep the widget off.

Bot vs staffed chat

Staffed chat (live agents, WhatsApp, SMS) wins when speed and empathy matter more than scale. Document-backed AI wins when the same factual questions repeat and your files are current.

Bot first: high FAQ volume, stable policies, limited support hours
Human first: bespoke products, high AOV, complex fit or compliance
Hybrid: bot for policy, human for exceptions (most mature stores land here)

What to compare when you shop

Knowledge formats: PDF, CSV, TXT vs manual FAQ only
Who supplies the AI key (merchant BYOK vs bundled credits)
Escalation workflow and teammate access
Optional voice inside the widget vs a real phone line
Script weight on product pages
What the product does not do (product recommendations, WhatsApp inside the widget, OpenAI-only runtimes if you standardize on another model)

Ichonic chatbot on Wix

On Wix, Live Chat and AI Chatbot is the Ichonic path when you want document-backed answers plus escalation. It uses Gemini 2.5 Pro with a merchant-supplied API key, reads PDF, CSV, and TXT uploads, supports escalate and resolve flows, teammate invites, and optional Vapi AI voice inside the widget.

It does not run on OpenAI at runtime, does not recommend products from catalog, does not embed WhatsApp inside the chatbot, and Vapi is not a PSTN phone transfer. For staffed WhatsApp, use WhatsApp Button or Chatz separately.

Wix-focused setup: best AI chatbot for Wix. App listing: confirm features on the Live Chat and AI Chatbot App Market page.

Live Chat and AI Chatbot

Document-backed AI chat with human escalation for Wix stores.

Open App Market

Setup mistakes

Launching with an empty knowledge base
Uploading marketing copy instead of operational answers
Stacking chat widgets beside a heavy product page
Promising live humans in the widget but staffing nobody
Using AI voice as if it were a staffed call center

What to measure

Share of sessions where the bot resolves without escalation
Escalation volume by topic (signals bad docs)
Time to first human reply after escalation
Refund or complaint rate on bot-handled threads vs baseline
Page weight after the widget loads

When not to use one

Policies are still being rewritten every week
Every order is custom and needs a human quote
You need staffed WhatsApp more than FAQ deflection
Reviews and trust copy are missing (fix Proofy first on Wix)
Nobody will own the escalation queue during buying hours

Full skip checklist for Wix: when not to use an AI chatbot on Wix. External context on support expectations: Google's guidance on helpful content applies to on-site help too. If answers are thin, fix the content before you automate it.

Ecommerce Chatbot: What It Does and When to Skip It