Chatbot That Answers Product Questions on Wix

A chatbot that answers product questions on Wix works when Live Chat and AI Chatbot can read accurate files: sizing, materials, shipping, and returns in PDF, CSV, or TXT, powered by your Gemini API key. Without those documents, it cannot answer product questions reliably.

App overview: best AI chatbot for Wix. Skip cases: when not to use AI chatbot. Listing: Live Chat and AI Chatbot.

How product Q&A works

1. You upload knowledge files (PDF, CSV, TXT).
2. You connect a Gemini API key.
3. Shoppers ask sizing, shipping, materials, or compatibility questions in the widget.
4. The bot answers from the files when the content exists.
5. Edge cases escalate to a teammate (unresolved / escalated / resolved states).

What to upload

When to use CSV

Use CSV when answers differ by product or variant. Columns might include SKU, title, size notes, shipping restriction, and FAQ snippet. Keep one row per sellable unit when rules diverge. Avoid stuffing marketing slogans into CSV cells.

PDF and TXT for policies

Store-wide policies belong in PDF or TXT: returns, shipping, warranty. Use clear headings. Delete outdated versions from the knowledge base when you upload a replacement so the bot does not mix old and new windows.

End-to-end setup

1. List the top 20 product questions from inbox, WhatsApp, or past tickets.
2. Write answers into PDF/TXT for policies and CSV for SKU-specific rules.
3. Install Live Chat and AI Chatbot. Connect Gemini.
4. Upload files. Set greet message and default suggestions from the real top questions.
5. Invite teammates for escalation.
6. Run the test script below on mobile.
7. Publish. Review wrong answers weekly and patch files.

Default suggestions that match real questions

• What size should I order?
• How long does shipping take?
• What is your return window?
• What materials is this made from?
• Does this work with [common accessory]?

Replace placeholders with your catalog language. Suggestions that do not match uploaded content create failed chats.

Test script before go-live

1. Ask a size question for a product with a chart in CSV/PDF.
2. Ask a shipping question covered in policy TXT/PDF.
3. Ask a return question with a clear window.
4. Ask something not in the files and confirm escalation works.
5. Ask a contradictory or outdated question you already removed from files.
6. Repeat on a phone-width screen.

Escalate product edge cases

Escalate custom orders, damage claims, payment issues, and anything that needs judgment. Teammate invites exist so a human can take over. If escalation is ignored, shoppers will stop trusting both the bot and the store.

Product questions vs reviews

Factual Q&A is the chatbot. Social proof is Proofy Reviews: widgets, email review requests, photo/video, imports. Do not expect the bot to replace reviews. Install Proofy for that job: how to add product reviews on Wix, Wix review app.

Mistakes

• Uploading a brand story PDF with no size chart
• Leaving old return windows in the KB
• Enabling Vapi AI voice before text product answers are accurate
• Hiding WhatsApp when high-intent buyers need a human
• Never retesting after a catalog change

When not to rely on the bot

• Catalog changes faster than you update files
• Every SKU needs a custom quote
• Nobody owns escalations
• Full skip list: when not to use AI chatbot on Wix

Staffed alternative: Wix WhatsApp button or Chatz. Listing price context at last publish for the chatbot: about US$1.94/mo monthly or US$1.60/mo yearly; 4.5 from 8 reviews. Confirm live. Widget may require a paid plan path to render on the storefront.

Example knowledge snippets

Write like support, not like a brochure. Examples of the tone and structure that work in TXT/PDF:

• Shipping: Orders placed before 2pm local ship same business day. Standard delivery is 3-5 business days inside the contiguous US. Express options show at checkout when available.
• Returns: Unworn items can be returned within 30 days of delivery. Sale items are final sale. Buyer pays return shipping unless the item is defective.
• Sizing: This jacket fits true to size. If you are between sizes, size up for layering. See the cm chart in the size CSV for chest and length.

For CSV, keep columns boring and exact: sku, product_name, fit_note, ship_restriction, care_note. The bot cannot invent a size chart you did not provide.

Keeping answers current

1. When a SKU ships from a new warehouse, update shipping TXT/PDF the same day.
2. When a size chart changes, replace the CSV row and delete the old file from the KB.
3. When a product is discontinued, remove or mark it so the bot does not promise stock.
4. Re-run the ten-question test after every major catalog update.

Hand off to WhatsApp cleanly

Some buyers will still want a human for product questions. That is fine. Keep WhatsApp Button or Chatz available for negotiation and custom orders, and tell the bot greet message that humans handle those cases. Do not run three launchers with identical greetings. Pick roles.

• Wix WhatsApp button
• Chatz
• When not to use AI chatbot

Mapping SKUs to answers

Product questions fail when the bot cannot tell SKUs apart. If size rules differ by product line, the CSV must say so. If only some SKUs ship internationally, the restriction column must say so. Generic store policy TXT is not enough for a catalog with exceptions.

• Group SKUs with identical rules to keep the file short
• Call out exceptions in plain language
• Include discontinued flags so the bot does not promise availability
• Align CSV titles with the names shoppers see on the Wix product page

Measuring product Q&A quality

• Percent of chats resolved without escalation
• Percent of escalations that were truly judgment calls vs missing docs
• Return reasons that mention wrong size or wrong shipping info after bot contact
• Repeat questions that never got a file patch

If missing docs dominate escalations, stop blaming the model and update files. If judgment calls dominate, keep humans in WhatsApp and narrow the bot to policy FAQs only.