About this plugin
ThemeVix AI Chat adds an AI storefront chatbot to your WooCommerce shop. Shoppers can ask about products, check order status, compare items, and request a human agent — all from a customizable chat widget on your site.
You provide your own AI API key. This plugin does not include paid AI access and does not send store data to ThemeVix servers.
Key features
- React admin dashboard with conversation inbox and usage statistics
- AI providers: OpenAI, Anthropic Claude, DeepSeek, Google Gemini, and Groq
- Product search, recommendations, comparison, upsells, and wishlist
- Order status and tracking help for logged-in customers; guest lookup with billing email verification
- Live chat handoff with agent assignment and offline message capture
- Knowledge base (RAG): index products, pages, posts, and upload PDF, DOCX, TXT, or CSV files
- Voice input (browser speech-to-text) and image understanding (OpenAI, Claude, Gemini)
- Customizable colors, position, bot name, welcome message, and display rules
- Compatible with WooCommerce HPOS (custom order tables)
Requirements
- WordPress 6.5 or later (uses the Requires Plugins dependency header)
- WooCommerce 7.0 or later (required; tested up to 9.8)
- PHP 7.4 or later
- An API key from at least one supported AI provider (free tiers available from Gemini and Groq)
Important notes
- API keys are encrypted in your WordPress database when OpenSSL is available.
- Visitor messages (and optional images) are sent only to the AI provider you configure.
- Google Fonts are disabled by default. Enable them under Appearance settings or with the themevix_ai_chat_enqueue_google_fonts filter.
- Source code: the unminified source for every bundled admin script and stylesheet ships inside this plugin, in admin/src/. See the Source Code section below for build instructions.
com
Privacy Policy
ThemeVix AI Chat stores chat data on your WordPress site and may send visitor messages to third-party AI providers you configure. ThemeVix does not collect store data on its own servers.
Data stored on your site: chat messages, conversation metadata, optional visitor name/email, session identifiers, wishlist data, knowledge-base uploads, and plugin settings (including API keys).
Data sent externally (when configured): chat message text and optional images or audio to your chosen AI provider; optional channel, CRM, and notification payloads to services you enable; Google Fonts stylesheet requests when enabled; optional browser speech-to-text when the visitor uses voice input.
Your responsibility: Add this plugin’s data practices to your store privacy policy and cookie notice. See External Services below for each provider’s privacy policy.
ThemeVix legal pages: Privacy Policy · Terms of Service
External Services
This plugin may connect to third-party services that you enable and configure. No data is sent to any service below until you turn it on and provide credentials (or, for Google Fonts, until you enable the setting). ThemeVix does not operate these services, does not proxy your API traffic, and does not receive store or chat data.
ThemeVix is not affiliated with Meta, WhatsApp, Instagram, Messenger, Telegram, OpenAI, Anthropic, Google, Groq, DeepSeek, Slack, Discord, HubSpot, Salesforce, Zoho, Pipedrive, Freshworks, Bitrix24, ActiveCampaign, or Mailchimp.
ThemeVix website (author documentation only; this plugin does not call ThemeVix servers:
com/privacy-policy/
com/terms-of-service/
Google Fonts (optional)
What it is used for: Optional “Plus Jakarta Sans” webfont in the admin dashboard and storefront widget.
What is sent and when: Only if Google Fonts are enabled in Appearance settings. com). Google may receive the visitor or admin IP address and user-agent as part of a normal font request.
com/
com/terms/
com/privacy
OpenAI
com/v1/audio/transcriptions) when you select OpenAI and save an API key.
com. When the knowledge base uses OpenAI embeddings, indexed text chunks are sent to create vectors. When server-side speech-to-text uses OpenAI, uploaded audio is sent for transcription.
com/
com/policies/terms-of-use/
com/policies/privacy-policy/
Anthropic (Claude)
com when you select Claude and save an API key.
com.
com/
com/legal/terms/
com/legal/privacy
Google Gemini
com when you select Gemini and save an API key.
What is sent and when: When Gemini is configured and a visitor sends a chat message, the message text, conversation context, system instructions, and optional image or audio data are sent to Google’s Gemini API.
dev/
com/terms/
com/privacy/
Groq
com when you select Groq and save an API key. com/openai/v1/audio/transcriptions when Groq is the speech backend.
What is sent and when: When Groq is configured and a visitor sends a chat message, the message text and conversation context are sent to the Groq Cloud API. When Groq speech-to-text is used, uploaded audio is sent for transcription.
com/
com/docs/legal/services-agreement/
com/privacy-policy/
DeepSeek
com when you select DeepSeek and save an API key.
What is sent and when: When DeepSeek is configured and a visitor sends a chat message, the message text and conversation context are sent to the DeepSeek API.
com/
html/
html/
WhatsApp Business Cloud API Meta
com (WhatsApp Cloud API). me links.
What is sent and when: When WhatsApp is enabled and configured, inbound and outbound message text, media metadata, and customer phone identifiers are sent between your site and Meta’s WhatsApp Cloud API. net host); that download carries your WhatsApp access token to Meta.
com/
com/legal/business-terms/
com/legal/business-policy/
Facebook Messenger Meta
com.
What is sent and when: When Messenger is enabled and configured, message text and Page-scoped user identifiers are sent to Meta’s Messenger Platform API for AI replies and agent handoff.
com/
com/legal/terms/
com/privacy/policy/
Instagram Direct Meta
com.
What is sent and when: When Instagram is enabled and configured, Direct Message text and Instagram-scoped user identifiers are sent to Meta’s Instagram Messaging API for AI replies and agent handoff.
com/
com/581066165581870
com/policy/
Telegram Bot API
org.
What is sent and when: When Telegram is enabled and configured, message text and Telegram chat/user identifiers are sent to Telegram’s Bot API for AI replies and agent handoff.
org/
org/tos/
org/privacy/
Slack
com).
What is sent and when: When Slack notifications are enabled and you save a Slack webhook URL, conversation summaries and handoff alerts are POSTed to that URL.
com/
com/terms-of-service/
com/privacy-policy-updated/
Discord
com/api/webhooks).
What is sent and when: When Discord notifications are enabled and you save a Discord webhook URL, conversation summaries and handoff alerts are POSTed to that URL.
com/
com/terms/
com/privacy/
Zapier / Make / custom webhooks
What it is used for: Optional automation when you paste your own HTTPS webhook URL (for example Zapier or Make).
What is sent and when: When you configure an automation or lead webhook URL, JSON payloads about new conversations, human handoff, and/or captured leads are POSTed to the URL you provide.
Service URL: Depends on the URL you configure.
Terms of use: Depends on the service you connect.
Privacy policy: Depends on the service you connect.
HubSpot CRM
com/ to sync contacts, deals, tickets, notes, and tasks when you enable HubSpot and save a private app token.
com/ only after you turn HubSpot sync on.
com/privacy-policy/.
com/
com/
com/terms-of-service/
com/api-terms/
com/privacy-policy/
Salesforce CRM
com).
What is sent and when: When Salesforce sync is enabled, mapped lead and conversation fields are sent to your Salesforce instance.
com/
com/company/legal/agreements/
com/company/privacy/
Zoho CRM
eu).
What is sent and when: When Zoho CRM sync is enabled, mapped lead and conversation fields are sent to your Zoho CRM account.
com/crm/
html/
html/
Pipedrive CRM
com/api/v1 when you enable Pipedrive and save credentials.
What is sent and when: When Pipedrive sync is enabled, mapped lead and deal fields are sent to your Pipedrive account.
com/
com/en/terms-of-service/
com/en/privacy/
Freshsales CRM
What it is used for: Optional CRM sync to your Freshsales / Freshworks CRM API (domain you provide).
What is sent and when: When Freshsales sync is enabled, mapped lead and contact fields are sent to your Freshsales account.
com/crm/
com/terms/
com/privacy/
Bitrix24 CRM
com).
What is sent and when: When Bitrix24 sync is enabled, mapped lead and contact fields are sent to your Bitrix24 portal.
com/
com/terms/
com/privacy/
ActiveCampaign
What it is used for: Optional contact and tag sync to the ActiveCampaign API URL you provide.
What is sent and when: When ActiveCampaign sync is enabled, mapped contact fields and tags are sent to your ActiveCampaign account.
com/
com/legal/terms-of-service/
com/legal/privacy-policy/
Mailchimp
com when you enable Mailchimp and save an API key.
What is sent and when: When Mailchimp sync is enabled, mapped audience/contact fields are sent to your Mailchimp account.
com/
com/legal/terms/
com/privacy/statement/
Browser speech recognition (optional)
What it is used for: Optional voice input in the storefront widget.
What is sent and when: If the visitor uses voice input and the browser supports the Web Speech API, audio may be processed by the browser vendor’s speech-to-text service (for example Chrome/Google). That path is controlled by the visitor’s browser, not by ThemeVix. Server-side transcription (when used) is documented under OpenAI, Groq, or Gemini above.
Source Code
The storefront widget is already human-readable:
- public/js/chat-widget.js
- public/css/chat-widget.css
- public/css/whatsapp-button.css
The WordPress admin dashboard is a React app. css ). The complete unminified source for those files is included in this plugin zip:
- Plugin UI source: admin/src/ (entry file admin/src/main.jsx )
- npm manifest: package.json (and package-lock.json when present)
- Vite build config: vite.config.js
- Built-file map: assets/asset-manifest.php
To rebuild the admin bundles from the included source:
- Install Node.js 18 or later
- Open the plugin folder
- Run npm install
- Run npm run build
No build step is required to use the plugin. npm install downloads the libraries listed below into node_modules/ and Vite writes the production files back to assets/.
Bundled third-party libraries (admin only; not loaded on the storefront):
- React 18 — MIT — source https://github.com/facebook/react/
- React DOM 18 — MIT — source https://github.com/facebook/react/
- Recharts 2 — MIT — source https://github.com/recharts/recharts/
-
com/WordPress/gutenberg/tree/trunk/packages/i18n)
js is the built React / React DOM runtime. js is the built Recharts runtime. js page chunks are compiled from the matching files in admin/src/pages/.