Description
Turn your WordPress content into an AI knowledge base that can answer visitors around the clock.
Lumowp Visitor Chat is an AI chatbot and website chat widget for WordPress. It indexes the posts and pages you select, searches that knowledge when a visitor asks a question, and uses OpenAI to write a clear answer grounded in your content. Answers can include a direct link to the relevant source page, helping visitors find the full information instead of receiving an unsupported guess.
Connect your own OpenAI API key and pay OpenAI directly for usage. There are no chat credits sold by the plugin and no request is made merely by activating it.
How the WordPress AI chatbot works
- Choose the posts and pages that should become the chatbot knowledge base.
- Run the indexing queue so the plugin can prepare that content for search.
- A visitor asks a question in the chat widget.
- The plugin finds the most relevant indexed content and sends the question and relevant text to OpenAI.
- The visitor receives a focused answer, with a source link when available.
Features included
- Content-based answers: Build the knowledge base from the WordPress posts and pages you choose.
- Category and tag targeting: Limit each selected content type to specific categories or tags. Child categories are included.
- Your own OpenAI API key: Use your own account without buying a separate package of chatbot credits.
- Source links: Help visitors verify an answer and continue reading on the relevant page.
- Custom chat appearance: Change the assistant name, welcome message, colors, avatar, launcher image, font, widget size, and position.
- RTL-ready interface: The widget layout supports right-to-left WordPress sites.
- Conversation history: Review chats from the WordPress dashboard.
- Flexible retention: Automatically remove old conversations after a chosen number of days, or enter 0 to keep them until you delete them.
- Export and email: Export an individual conversation or send its transcript by email.
- Multiple placement options: Use the site-wide launcher, shortcode, Gutenberg block, or Elementor widget.
- Rate limiting: Control how many messages a visitor can submit during a time window.
- Diagnostics: Review connection, indexing, and chat health when troubleshooting.
- Optional footer credit: The credit is hidden by default and appears only if you enable it.
Designed for useful self-service support
Use Lumowp Visitor Chat to answer recurring questions from documentation, service pages, policies, tutorials, and other published content. Because you control the indexed sources, the knowledge base can stay focused on the information that belongs to your website.
Privacy and data handling
Conversation records are stored in your WordPress database according to the retention period you select. Chat messages and relevant indexed text are sent to OpenAI only when needed to build the index or answer a question. API credentials are stored in WordPress and encrypted when OpenSSL is available. The plugin also registers WordPress personal-data export and erasure tools for conversation data.
Need a chatbot for WooCommerce?
A separate shop edition adds product-focused answers, contact capture, and human handoff. Those commerce and lead tools are not included in Lumowp Visitor Chat.
See Lumo AI Chatbot for WordPress and WooCommerce
External services
This plugin connects to the OpenAI API to create embeddings for the knowledge-base index and to generate chat answers.
- Service: OpenAI API (
https://api.openai.com/v1). - What is sent for indexing: text extracted from the posts and pages you selected.
- What is sent for chat: the visitor’s message, relevant content found in the index, and instructions configured for the assistant.
- Authentication: requests include the OpenAI API key saved by the site administrator.
- When it is sent: when an administrator starts indexing or when a visitor sends a chat message. Activation alone does not send content.
This service is provided by OpenAI: Terms of Use, Privacy Policy, API data usage policies.
Pre-chat acceptance and optional verification
Terms & Consent is enabled by default, including on upgrade. Visitors actively accept an editable notice before sending messages or contact details. Configure your site terms URL; a published WooCommerce terms page and WordPress privacy page are used when available. These notices do not guarantee immunity from legal liability or replace applicable consumer rights.
An expiring receipt is stored in the visitor browser for the same conversation, bot and language. Changing the notice, links, policy version or linked local terms page requires acceptance again. Minimal server records contain the displayed notice, linked URLs, policy version, time and a hashed conversation ID (and WordPress user ID when available). They do not add an IP address or prove real-world identity. Security retention settings apply; identifiable records are included in WordPress personal-data export and erasure.
Optional Cloudflare Turnstile requires the owner’s site and secret keys. Only when enabled, the browser loads https://challenges.cloudflare.com/turnstile/v0/api.js and the server sends the verification token and secret to https://challenges.cloudflare.com/turnstile/v0/siteverify at acceptance. No remote verification is performed for each chat message. Cloudflare terms: https://www.cloudflare.com/website-terms/ ; privacy: https://www.cloudflare.com/privacypolicy/ . A checkbox with the default lightweight abuse controls is not a substitute for stronger bot verification.
Blocks
This plugin provides 1 block.
- Lumowp Visitor Chat
Installation
- In WordPress, open Plugins > Add New, search for “Lumowp Visitor Chat”, and click Install Now. You can also upload the plugin ZIP and activate it.
- After activation, open Lumo WP > Visitor Chat. The setup wizard will guide you through the initial configuration.
- Open Settings > API Settings, paste your OpenAI API key, choose an available model, and use Test to confirm the connection.
- Open Settings > Content Sources and select the posts and pages the chatbot is allowed to use. Add category or tag limits if required.
- Open Indexing and click Start Indexing. Keep the page open while the first indexing queue finishes.
- Open Settings > Appearance to set the assistant name, welcome message, colors, avatar, launcher, font, size, and position.
- Visit the front end and ask questions that are answered in your indexed content. Confirm that the answers and source links are correct.
- Optional: place an inline chat with the
[lumo_smartchat inline="true"]shortcode, the Lumowp Visitor Chat Gutenberg block, or the Elementor widget.
If an answer is missing, confirm that its source is selected, run indexing again, and review the Diagnostics screen for connection or queue errors.
FAQ
-
What is Lumowp Visitor Chat?
-
It is an AI chatbot for WordPress that turns selected posts and pages into a searchable knowledge base. Visitors use a chat widget to ask questions, and OpenAI writes an answer using relevant content found by the plugin.
-
Where do chatbot answers come from?
-
From the posts and pages you index. The widget does not browse the open web. A reply can link the page it used.
-
Do I need an OpenAI API key?
-
Yes. You paste your own OpenAI API key in the plugin settings. OpenAI bills that key. Nothing is sent until the key is saved and a visitor uses the chat, or you start indexing.
-
How do I install and set up the chatbot?
-
Activate the plugin, connect and test your OpenAI key, select content sources, run the first indexing queue, customize the widget, and ask a test question on the front end. The included setup wizard covers the same basic flow.
-
Yes. Each content type can be limited to chosen categories or tags. Child categories are included. Items outside that limit are left out of the index.
-
Does the chatbot answer from the internet?
-
No. Its knowledge search uses the WordPress content you selected and indexed. OpenAI generates the response from the question and the relevant context supplied by the plugin.
-
Where are conversations stored and how long are they kept?
-
Conversation records are kept in your WordPress database. You set the number of retention days. Set 0 to keep conversations until you delete them. You can export an individual conversation or email its transcript.
-
Can I customize the WordPress chat widget?
-
Yes. The appearance controls cover the assistant name, welcome message, colors, avatar, launcher image, font, size, and position. The layout also supports RTL sites.
-
Can I embed the AI chatbot in a page?
-
Yes. Use the shortcode, Gutenberg block, or Elementor widget for inline placement. The standard floating launcher can also appear across the site.
-
Does the chat widget show a Lumowp credit?
-
The footer credit stays hidden until you turn it on. When it is on, it follows the site language.
-
Does this include product answers, lead forms, or human handoff?
-
No. Product answers, contact capture, and handing a chat to a person are in the separate shop plugin: Lumo AI Chatbot for WordPress.
-
How can I troubleshoot an answer or indexing problem?
-
Check that the source is selected, run indexing again, and open Diagnostics to review API, model, knowledge-base, queue, and recent error information.
-
What happens if I activate the full plugin later?
-
This plugin pauses and shows a notice. Keep only one of the two plugins active.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“AI Chatbot for WordPress – Visitor Chat & Knowledge Base by Lumowp” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “AI Chatbot for WordPress – Visitor Chat & Knowledge Base by Lumowp” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.33 – 2026-10-10
- Improved – Reduce repeated AI requests with evidence-aware reply caching, compact planning, bounded request timeouts, and reliable local retrieval fallbacks.
- Fixed – Preserve page-builder content and distinct service plans during indexing, and retain the working index when a replacement fails.
- Fixed – Recover expired security tokens without blocking visitors whose device clocks differ from the server.
- Improved – Preserve natural replies and source links while checking facts, numeric values, and uncertain answers more accurately.
- Added – Default-on site terms acceptance, editable policy links, privacy-aware acceptance records, and optional Cloudflare Turnstile verification.
- Improved – Keep gradual typing, clarify diagnostic outcomes, and use theme or system fonts without additional font downloads.
1.0.32
- Category and tag limit controls sit in the same layout as the other settings.
1.0.29
- Each content type can be limited to chosen categories or tags. Child categories are included, and items outside the limit are left out of the knowledge base.
1.0.28
- The chat footer credit follows the site language.
1.0.27
- The credit notice loads its stylesheet and script through WordPress, and the Elementor chat block escapes its size when it is printed.
1.0.26
- Credit notice strings are registered for translation.
1.0.25
- Appearance upload and font buttons load their script on the Appearance page itself, so they work even if the first asset pass skipped them.
1.0.24
- Appearance upload and font controls load on the settings screen instead of staying disconnected from the buttons.
1.0.23
- The avatar and launcher image buttons open the computer’s file window, instead of a dark screen.
1.0.22
- On a right-to-left site, the chat header name and status sit next to the avatar. The Appearance upload and font picker open when clicked.
1.0.21
- Source links stay under the reply when the answer is typed out on screen.
1.0.20
- A page named in the reply is linked even when that name is written in quotation marks, not only in a list.
1.0.19
- A follow-up no longer goes back to answer an earlier greeting, and a named item still gets its page link when that page was missed by the first search.
1.0.18
- A later reply no longer starts by introducing the assistant again, and a source link is shown when the reply names that item.
1.0.17
- After a refresh, the written reply stays on screen. Source links sit under that text.
1.0.16
- A saved learning button shows only when the visitor asked about that note, not on a greeting.
1.0.15
- Source links under a reply show a link icon and stay as compact links when the page is reloaded.
1.0.14
- A follow-up stays on the subject already being discussed, instead of starting the introduction again. When the visitor asks for the link, the reply uses the address already on that item.
1.0.13
- The empty-balance notice stays in the admin only, and it can be closed.
1.0.12
- A red notice at the top of the admin when the chat token balance is empty. It rechecks every few hours, and a Test button hides it once the balance is back.
1.0.11
- The header character sits on its own, without the square tile, and is larger.
1.0.10
- Products are indexed when WooCommerce is active and you include them as a content source.
- Conversation export and transcript email are included.
- Chat replies use the current marked library for formatting.
1.0.7
- The plugin answers from posts and pages with your own OpenAI key, and every included tool is available without a lock.
- Conversation retention follows the number of days you set. Set 0 to keep conversations until you delete them.
- The footer credit stays off until you choose to show it.
- A free-form CSS box was removed. Use the appearance controls instead.
- On small screens the launcher button no longer sits on top of the open chat.
- A real question no longer starts with a second hello after the welcome message.
- A bare thank-you no longer repeats the previous answer.
- Asking which services are available now names those services instead of stopping before the list.
- The answer-style control is labeled Creativity and starts at 1.
1.0.0
- First release. Posts, pages, and your own OpenAI key.
