ThemeVix AI Chat Wordpress Plugin - Rating, Reviews, Demo & Download

ThemeVix AI Chat Preview Wordpress Plugin - Rating, Reviews, Demo & Download

No ratings yet

Free

Follow for free plugins, new theme releases and theme news

Plugin Description

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.

Support: contact.themevix@gmail.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: https://themevix.com/privacy-policy/ · https://themevix.com/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):
Privacy policy: https://themevix.com/privacy-policy/
Terms of service: https://themevix.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. The browser requests the stylesheet from fonts.googleapis.com (and font files from fonts.gstatic.com). Google may receive the visitor or admin IP address and user-agent as part of a normal font request.

Service URL: https://fonts.google.com/
Terms of use: https://policies.google.com/terms
Privacy policy: https://policies.google.com/privacy

OpenAI

What it is used for: AI chat replies, optional image understanding, knowledge-base embeddings (api.openai.com/v1/embeddings), and optional voice transcription (api.openai.com/v1/audio/transcriptions) when you select OpenAI and save an API key.

What is sent and when: When OpenAI is your active chat provider and a visitor sends a message: message text, conversation context, system instructions, and optional image data go to api.openai.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.

Service URL: https://openai.com/
Terms of use: https://openai.com/policies/terms-of-use
Privacy policy: https://openai.com/policies/privacy-policy

Anthropic (Claude)

What it is used for: AI chat replies and optional image understanding via api.anthropic.com when you select Claude and save an API key.

What is sent and when: When Claude is configured and a visitor sends a chat message, the message text, conversation context, system instructions, and optional image data are sent to api.anthropic.com.

Service URL: https://www.anthropic.com/
Terms of use: https://www.anthropic.com/legal/terms
Privacy policy: https://www.anthropic.com/legal/privacy

Google Gemini

What it is used for: AI chat replies, optional image understanding, optional embeddings, and optional speech understanding via generativelanguage.googleapis.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.

Service URL: https://ai.google.dev/
Terms of use: https://policies.google.com/terms
Privacy policy: https://policies.google.com/privacy

Groq

What it is used for: AI chat replies via api.groq.com when you select Groq and save an API key. Optional voice transcription uses api.groq.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.

Service URL: https://groq.com/
Terms of use: https://console.groq.com/docs/legal/services-agreement
Privacy policy: https://groq.com/privacy-policy

DeepSeek

What it is used for: AI chat replies via api.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.

Service URL: https://www.deepseek.com/
Terms of use: https://cdn.deepseek.com/policies/en-US/deepseek-terms-of-use.html
Privacy policy: https://cdn.deepseek.com/policies/en-US/deepseek-privacy-policy.html

WhatsApp Business Cloud API (Meta)

What it is used for: Optional WhatsApp inbox: AI replies, notifications, and live handoff through graph.facebook.com (WhatsApp Cloud API). Optional click-to-chat buttons may open wa.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. When a customer sends an attachment, the plugin first requests the media record from graph.facebook.com and then downloads the file from the temporary Meta-owned CDN URL that Meta returns (for example lookaside.fbsbx.com or a fbcdn.net host); that download carries your WhatsApp access token to Meta.

Service URL: https://business.whatsapp.com/
Terms of use: https://www.whatsapp.com/legal/business-terms
Privacy policy: https://www.whatsapp.com/legal/business-policy

Facebook Messenger (Meta)

What it is used for: Optional Messenger inbox via graph.facebook.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.

Service URL: https://www.messenger.com/
Terms of use: https://www.facebook.com/legal/terms
Privacy policy: https://www.facebook.com/privacy/policy

Instagram Direct (Meta)

What it is used for: Optional Instagram Direct inbox via graph.facebook.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.

Service URL: https://www.instagram.com/
Terms of use: https://help.instagram.com/581066165581870
Privacy policy: https://privacycenter.instagram.com/policy

Telegram Bot API

What it is used for: Optional Telegram inbox via api.telegram.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.

Service URL: https://telegram.org/
Terms of use: https://telegram.org/tos
Privacy policy: https://telegram.org/privacy

Slack

What it is used for: Optional staff alerts (new conversations and human handoff) posted to a Slack incoming webhook (hooks.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.

Service URL: https://slack.com/
Terms of use: https://slack.com/terms-of-service
Privacy policy: https://slack.com/privacy-policy-updated

Discord

What it is used for: Optional staff alerts posted to a Discord channel webhook (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.

Service URL: https://discord.com/
Terms of use: https://discord.com/terms
Privacy policy: https://discord.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 (api.hubapi.com)

This plugin connects to the HubSpot CRM API at https://api.hubapi.com/ to sync contacts, deals, tickets, notes, and tasks when you enable HubSpot and save a private app token.

It sends mapped lead and conversation fields (such as name, email, phone, company, deal notes, or tickets) to https://api.hubapi.com/ only after you turn HubSpot sync on.

This service is provided by HubSpot: terms of use https://legal.hubspot.com/terms-of-service , API terms https://legal.hubspot.com/api-terms , privacy policy https://legal.hubspot.com/privacy-policy .

Service URL: https://api.hubapi.com/
Website: https://www.hubspot.com/
Terms of use: https://legal.hubspot.com/terms-of-service
API terms: https://legal.hubspot.com/api-terms
Privacy policy: https://legal.hubspot.com/privacy-policy

Salesforce CRM

What it is used for: Optional CRM sync to your Salesforce org REST API (instance URL you provide, typically *.salesforce.com or *.my.salesforce.com).

What is sent and when: When Salesforce sync is enabled, mapped lead and conversation fields are sent to your Salesforce instance.

Service URL: https://www.salesforce.com/
Terms of use: https://www.salesforce.com/company/legal/agreements/
Privacy policy: https://www.salesforce.com/company/privacy/

Zoho CRM

What it is used for: Optional CRM sync to your Zoho CRM API (domain you provide, typically *.zoho.com / *.zoho.eu).

What is sent and when: When Zoho CRM sync is enabled, mapped lead and conversation fields are sent to your Zoho CRM account.

Service URL: https://www.zoho.com/crm/
Terms of use: https://www.zoho.com/terms.html
Privacy policy: https://www.zoho.com/privacy.html

Pipedrive CRM

What it is used for: Optional CRM sync via *.pipedrive.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.

Service URL: https://www.pipedrive.com/
Terms of use: https://www.pipedrive.com/en/terms-of-service
Privacy policy: https://www.pipedrive.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.

Service URL: https://www.freshworks.com/crm/
Terms of use: https://www.freshworks.com/terms/
Privacy policy: https://www.freshworks.com/privacy/

Bitrix24 CRM

What it is used for: Optional CRM sync via the Bitrix24 REST / inbound webhook URL you provide (typically *.bitrix24.com).

What is sent and when: When Bitrix24 sync is enabled, mapped lead and contact fields are sent to your Bitrix24 portal.

Service URL: https://www.bitrix24.com/
Terms of use: https://www.bitrix24.com/terms/
Privacy policy: https://www.bitrix24.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.

Service URL: https://www.activecampaign.com/
Terms of use: https://www.activecampaign.com/legal/terms-of-service
Privacy policy: https://www.activecampaign.com/legal/privacy-policy

Mailchimp

What it is used for: Optional audience/contact sync via *.api.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.

Service URL: https://mailchimp.com/
Terms of use: https://mailchimp.com/legal/terms/
Privacy policy: https://www.intuit.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. Production (minified) files live in assets/js/ and assets/css/ (admin.js, admin-vendor.js, admin-charts.js, lazy page chunks, admin.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
@wordpress/i18n — GPL-2.0-or-later — source https://github.com/WordPress/gutenberg/tree/trunk/packages/i18n

assets/js/admin-vendor.js is the built React / React DOM runtime. assets/js/admin-charts.js is the built Recharts runtime. assets/js/admin-*.js page chunks are compiled from the matching files in admin/src/pages/.

Screenshots

Admin dashboard — conversation stats, setup status, and recent sessions at a glance
Live Chat inbox — claim, assign, and reply to conversations in real time
Lead Generation — capture, manage, and track leads from chat conversations
CRM integration — connect HubSpot, Salesforce, Zoho, Pipedrive, and more
Channels & Integrations — configure WhatsApp, Messenger, Instagram, Telegram, Slack, Discord, and webhooks
Knowledge Base — index products, pages, posts, and upload PDF, DOCX, TXT, or CSV files for RAG
Privacy & Compliance — GDPR consent, PII masking, data retention, and audit log
AI Settings — choose provider, model, and API key; test and activate in one click
Appearance — customize colors, widget position, and preview live in the dashboard
Storefront chat widget — product cards with price, stock, and image shown inline

Select one or more tags, then press “Search Plugins”

ThemeVix AI Chat Wordpress Plugin - Rating, Reviews, Demo & Download