The best AI chatbot for a Wix store in this stack is Live Chat and AI Chatbot: Gemini-powered answers from your PDF, CSV, or TXT files, with human escalation and teammate invites. It wins when your FAQs are documented. It fails when the knowledge base is empty or wrong.
Related: Wix AI chatbot, chatbot product questions, when not to use AI chatbot. Stack context: best Wix apps.
The pick
| Need | Use | Skip if |
|---|---|---|
| Repeat FAQ deflection | Live Chat and AI Chatbot | You have no written policies yet |
| Staffed WhatsApp | WhatsApp Button: Ichonic | Nobody will reply |
| Multi-channel launcher | Chatz | You only need WhatsApp |
| Product reviews | Proofy Reviews | You expected the chatbot to replace reviews |
Real features
- Merchant Gemini API key powers AI replies
- Knowledge base from uploaded PDF, CSV, or TXT
- Conversation states: unresolved, escalated, resolved
- Teammate invites so agents can take over
- Optional Vapi AI voice inside the widget
- Widget controls: greet message, default suggestions, header and logo, colors, left or right position, desktop and mobile visibility
Install from the Live Chat and AI Chatbot App Market listing.
Pricing and plan notes
Listing context at last publish: US$1.94 per month on monthly billing, or US$1.60 per month when billed yearly; 4.5 from 8 reviews. Confirm the live price block. On a free plan path, the storefront widget does not render until you are on a paid plan. Gemini API usage is billed by Google to the key owner.
Setup that works
- Write or export shipping, sizing, materials, and returns into PDF, CSV, or TXT.
- Install the app and connect your Gemini API key.
- Upload knowledge files. Start with the documents customers ask about most.
- Set greet message and a few default suggestions that match real questions.
- Invite at least one teammate for escalations.
- Test ten real questions on mobile and desktop before advertising the widget.
- Turn on AI voice only after text answers are accurate.
Knowledge base rules
- Prefer short, factual sections over marketing fluff
- Put SKU-specific rules in structured CSV when sizes or variants differ
- Update files when shipping rates or return windows change
- Do not upload contradictory drafts
- If the bot invents an answer, treat it as a missing document, not a personality problem
Tip
The chatbot is only as good as the last file you uploaded. Stale policies create refunds.
Escalation and teammates
Conversation states include unresolved, escalated, and resolved. Escalation is the safety valve for edge cases: custom orders, damaged goods, payment disputes. Invite teammates so someone can take over. If nobody watches escalations, turn the widget off until you can.
Vapi AI voice (optional)
Optional Vapi support adds AI voice chat inside the widget. That is not a phone number customers dial to reach a human. Do not sell it as a call center. Enable it only after text quality is solid and you still want a voice path.
AI chat vs WhatsApp buttons
AI chat and WhatsApp solve different jobs. AI chat deflects documented FAQs. WhatsApp Button or Chatz opens a staffed messaging app. Running both can work if roles are clear: bot for FAQ, WhatsApp for human negotiation. Running both with no ownership creates noise and script weight.
Common mistakes
- Going live with an empty knowledge base
- Leaving escalations unmonitored
- Promising phone support when you only have Vapi AI voice
- Stacking chatbot + Chatz + WhatsApp Button with no primary path
- Expecting the bot to replace Proofy reviews
What to measure
- Chat starts per session
- Escalation rate
- Wrong-answer tickets or refunds tied to bot replies
- Time-to-first-human on escalations
- Conversion rate on pages where the widget is visible vs hidden (if you test that)
When not to use it
- Policies are unfinished or change daily without document updates
- Every order needs human judgment (made-to-order, B2B quoting)
- Nobody will monitor escalations
- You only need a staffed WhatsApp button
- Full detail: when not to use AI chatbot on Wix
Reviews still belong in Proofy: Wix review app. Speed after widgets: Wix site speed test.
Widget UX that does not fight checkout
Use left or right position deliberately. On mobile, confirm the launcher does not cover Add to Cart or the Wix checkout button. Limit default suggestions to questions your files actually answer. A greet message should set expectations: store hours, what the bot can answer, and that humans handle escalations.
- Hide or soften the widget on checkout if it steals taps
- Keep branding consistent with the theme (header, logo, colors)
- Desktop and mobile visibility can differ if mobile is too crowded
Weekly operations
- Skim escalated conversations.
- Patch PDF/CSV/TXT for every wrong answer.
- Remove contradictory old files.
- Check Gemini key billing and quotas.
- Confirm teammates still receive escalations.
- Retest five top product questions after any catalog change.
If wrong-answer rate stays high after two weeks of patches, pause the bot and staff WhatsApp until documents catch up. See when not to use AI chatbot.
How it fits the Ichonic stack
- Proofy: social proof, not FAQ answers
- Live Chat and AI Chatbot: documented product and policy questions
- WhatsApp Button / Chatz: human messaging
- Speed Booster: only after widget weight is justified and measured
New sites should not install the chatbot on day one unless policies already exist. Follow best ecommerce Wix apps for new sites. Product question packaging: chatbot product questions.
Gemini key ownership
The merchant owns the Gemini API key and the Google billing on that key. That is intentional: AI token use should be visible to the store, not hidden inside a mystery meter you cannot audit. Rotate keys if staff leave. Do not paste keys into public docs. If the key hits quota, the bot will fail until you fix billing.
- Create the key under a Google account the business controls
- Monitor usage the first week after launch
- Keep a non-AI fallback (FAQ page or WhatsApp) if the key fails
Go-live QA matrix
| Check | Pass criteria |
|---|---|
| Top 10 FAQ answers | Match the uploaded files exactly on policy numbers |
| Unknown question | Escalates instead of inventing a shipping promise |
| Mobile placement | Does not cover Add to Cart |
| Teammate invite | Human can take over an escalated chat |
| Plan gate | Widget renders on the published storefront |
| Voice (if enabled) | Clearly AI voice, not marketed as a phone line |
Fail any row and keep the widget off until it passes. Product-question packaging help: chatbot product questions.
FAQ
What is the best AI chatbot for Wix?+
For Ichonic's stack: Live Chat and AI Chatbot. It answers from uploaded PDF/CSV/TXT using a merchant Gemini API key, escalates to humans, and supports teammate invites. Optional Vapi AI voice is inside the widget, not a phone line.
Do I need a Gemini API key?+
Yes for AI replies. The merchant supplies the Gemini API key. Without it, you do not get the AI answering path the product is built around.
What files can the knowledge base use?+
PDF, CSV, and TXT uploads. Keep shipping, sizing, materials, and returns accurate and current.
Does the chatbot replace WhatsApp?+
No. AI chat deflects repeat FAQs. WhatsApp Button or Chatz is for staffed click-to-chat. Pick a primary path. See /blog/wix-whatsapp-button/ and /blog/whatsapp-chat-buttons-chatz-wix/.
Is Vapi a phone number for customers to call?+
No. Vapi is optional AI voice chat inside the widget. Do not market it as a staffed phone center.
When should I not use an AI chatbot on Wix?+
When policies are unfinished, answers must be human judgment, or nobody will monitor escalations. Full guide: /blog/when-not-to-use-ai-chatbot-wix/.
How do I train it for product questions?+
See /blog/chatbot-product-questions-wix/ for catalog and FAQ document structure.
Still deciding what fits your store?
Tell us what you are running today and we will tell you what to add, swap, or skip.
