Oli AI Chatbot

Oli AI Chatbot is a lightweight on-site chat for WordPress. By default it is 100 % local: it indexes your published pages, posts, public custom post types and WooCommerce products, then answers with the best matching passages and their links. There is no account, no proxy and no service run by the plugin author.

com

com/olivierbigras

Optional AI is off by default. If you turn it on, you enter your own API key (OpenAI, Mistral, or a custom OpenAI-compatible base URL) on your site. The key is stored encrypted.

Nothing is sent anywhere until you enable AI explicitly. See External services.

Local answers

• FULLTEXT index of passages (about 120–200 words, split on H2/H3 headings)

• Automatic fallback to LIKE + BM25 when FULLTEXT is unavailable

• Small-talk replies (hi / bonjour, thanks / merci, goodbye, who are you, help) before search — editable per language under Settings → Basic replies

• Friendlier no-result state with suggestion chips (FAQ / support, dealers, shop, contact) plus the contact form

• Light FR/EN stemming, editable synonyms, and typo tolerance against the terms table; relevance threshold is a setting ( oliaichat_min_score filter)

• Each FAQ question/answer (accordions, Yoast/Rank Math blocks, FAQPage JSON-LD) is indexed on its own; definition questions show the answer first, product names and buy/price queries still rank products first

• Reindex on save and delete, plus WP-Cron batches of 25

• Language filter (Polylang, WPML, TranslatePress, or the site locale)

• WooCommerce products: title, short and long description, SKU, price, attributes

• Appearance tab: live preview, theme colours, launcher icons or a media image, desktop/mobile offsets, FR/EN copy, and show/hide rules

Optional AI (off by default)

• Provider select: OpenAI, Mistral, or a custom OpenAI-compatible URL

• Encrypted API key, never shown again after save

• Caps: 10 AI replies per session and 200 per day for the whole site (defaults)

• Test button on Settings → AI answers (admin only). It sends nothing until AI is enabled and a readable key is saved

Conversations and email

• A launcher opens an accessible chat panel; JavaScript and CSS load on hover, focus, click or idle

• The widget stores only sessionStorage (no cookies)

• Conversations are listed in the admin

• Transcripts are emailed (HTML + plain text) to the site owner when a visitor ends the chat (if the chat had messages) and after 15 minutes of inactivity. The visitor can optionally enter their email on End to receive the same transcript.

• “Send my question by email” appears when local search finds nothing

• Log retention defaults to 30 days (0 = do not store message bodies; open session rows are kept until the chat ends)

Multilingual

Works with Polylang, WPML and TranslatePress (and a single-language site). org.

Privacy

• Anonymized questions and votes. Questions asked in the chat may be stored in a learning log after emails, phone numbers and obvious names are stripped. Only the question text, language, outcome (answered / unanswered / emailed), an optional “Was this helpful?” vote, a count and the last date are kept. No IP, email or page URL is stored in that log.

• 30-day purge by default. Raw questions, votes and conversation message bodies follow Settings → Privacy retention (default 30 days). Set 0 to store no logs. Open session rows are kept until the chat ends.

• Learned FAQs are kept. Answers the site owner writes under Settings → Answers are not purged with the question log.

• Transcripts by email to the admin. When a visitor ends a chat that had at least one message, or after 15 minutes of inactivity, a transcript is emailed to the site owner. Opening the launcher without chatting emails nobody.

• Optional visitor email. On End, the visitor may enter an address to receive the same transcript. That address is used only for that copy. The contact form emails the owner with Reply-To set to the visitor.

• Front widget. sessionStorage only; no cookies, no localStorage, no tracker. Treat the script as functional in Complianz (no tracking cookies).

• Rate limits. Public REST limits use a hashed IP in a WordPress transient. The learning log still stores no IP.

• WordPress export and erase tools cover conversations tied to an email from the contact form or the optional End transcript field.

• Keep-data option on uninstall (off by default). Suggested privacy-policy text is added under Settings → Privacy.

External services

com, Google, Cloudflare Turnstile, maps, spreadsheets or webfonts. There is no proxy, no telemetry and no account with the plugin author. Outbound HTTP happens only when a site administrator enables AI answers (opt-in) or clicks a Donate link (opt-in).

When AI is enabled, visitor questions and the matching local passages are sent to the selected provider so it can draft an answer. Typical data: the question text, retrieved passage excerpts, the configured model name, and the site language. The Test key button sends only a short ping (“pong”) from the admin screen — no visitor text.

No WordPress passwords or API keys of other plugins are sent.

OpenAI

• Used when the provider is set to OpenAI (or a custom URL that points to OpenAI).

• When: after the site owner enables AI answers and saves their own OpenAI API key; also when they click Test key.

• Endpoint: https://api.openai.com/v1/chat/completions

• Data sent: the question and retrieved passages (or “pong” for Test key), plus the configured model name and site language.

• Terms of use: https://openai.com/policies/terms-of-use

• Privacy policy: https://openai.com/policies/privacy-policy

Mistral

• Used when the provider is set to Mistral.

• When: after the site owner enables AI answers and saves their own Mistral API key; also when they click Test key.

• Endpoint: https://api.mistral.ai/v1/chat/completions

• Data sent: the question and retrieved passages (or “pong” for Test key), plus the configured model name and site language.

• Terms of service: https://mistral.ai/terms/

• Privacy policy: https://mistral.ai/terms/#privacy-policy

Custom OpenAI-compatible endpoint

• Used when the provider is set to a custom base URL.

• When: after the site owner enables AI answers, saves their key, and (optionally) clicks Test key.

• Data sent: the same payload as above, to the URL the site owner entered.

• Terms and privacy: those of the service behind that URL (the site owner is responsible for reviewing them).

PayPal (Donate)

• Used only when a site administrator clicks Donate / Buy me a coffee in the plugin list or on Settings → Oli AI Chatbot. The plugin never contacts PayPal in the background.

• Endpoint: https://www.paypal.com/donate/?hosted_button_id=29SAPKFAHMTNW

• Data sent: whatever PayPal collects on that hosted button page after the click (the plugin itself sends nothing).

• Terms: https://www.paypal.com/us/legalhub/paypal/useragreement-full

• Privacy: https://www.paypal.com/us/legalhub/privacy-full

com) is listed as Author URI and in a local staging mail-guard rewrite. The plugin does not request that site over HTTP.

The Test key button is the only admin-triggered outbound AI call besides live answers. Both require AI answers to be enabled; otherwise the plugin reports that nothing was sent.