NeedToMe AI Chat

Description

NeedToMe AI Chat puts an AI consultant on your WordPress site. It answers visitors around the clock from what you teach it: the pages of your site, documents, price lists and your own answers. It speaks the visitor’s language, asks for a name, phone or e-mail when a visitor wants to order or be called back, and sends the lead to you by e-mail, Telegram, Slack, Microsoft Teams, Discord, Google Sheets, Notion, a CRM or a webhook. When a question needs a person, the dialog is handed over to you.

An account at kra.name is required. The chat, its knowledge base, its answers and your leads live there; this plugin connects your site to that chat with the chat’s public key. Without an account and a chat set up at kra.name the plugin shows nothing to visitors.

Connect several chats to the same site, each with its own appearance, page rules, knowledge selection, catalog sync, setup wizard and statistics. For example, an AI nutritionist can use articles while a recipe finder uses recipe posts.

What you set in WordPress:

• Chats: add public keys manually or choose chats from your AI Worker account, one click per chat. A connection error is shown next to that chat.
• Look: theme, colour scheme (light, dim, dark or the visitor’s system setting), every colour of the window, position of the button.
• Loading: at once, after a delay, on the first scroll or on interaction — the chat does not slow your pages down.
• Language: fixed or automatic (URL prefix, language subdomain, HTML lang, browser).
• Pages: on every page, only on the pages you list, or everywhere except them (paths like /contacts/ or /shop/*).
• Inline chat: the [aiworker_chat] shortcode puts the chat into a block of a page.
• The consultant and the chat texts in every language: greeting, quick questions, name and caption, with one-click translation into the chat’s other languages.
• The AI notice under the input and the AI’s greeting next to the chat button when a page opens.
• Leads: where they go (e-mail, Telegram, Slack, Microsoft Teams, Discord, Google Sheets, Notion, a CRM or a webhook), with a delivery test.
• Knowledge base: the site’s posts, pages, WooCommerce products, ACF fields and text widgets are sent to the chat and kept up to date; sources (sites, pages, Google Docs, texts) and questions and answers are added and edited right in the plugin.
• Connect with one button through an AI Worker account; a setup wizard (with voice input), usage limits and statistics.
• Voice input, dialog rating and a link to your privacy policy inside the chat.
• A live preview of the chat on the settings page. Before a key is saved, click “Load live preview” to load the sample widget from kra.name; with a saved key the preview loads automatically. The connection check says exactly what to fix (key, allowed domain, finished setup, Content-Security-Policy).

When the chat is shown, the plugin merges its required sources into Content-Security-Policy headers sent by PHP. Server-level headers are outside WordPress and must be updated separately. Add the aiworker_chat_merge_csp filter and return false to turn off this automatic merge.

Paid add-ons (documents and photos from visitors, voice and others) are enabled for each chat at kra.name.

External services

This plugin connects to kra.name, a hosted AI chat service. An account and a configured chat are required.

When the chat is enabled on a page, the visitor’s browser loads the chat widget from kra.name. The live preview on the Settings screen also loads widget.js from kra.name in the administrator’s browser: it loads automatically when a chat key is saved, or after the administrator clicks “Load live preview” when there is no saved key. Messages and any contact details the visitor chooses to provide are sent to kra.name so the service can generate replies, keep the conversation and deliver leads to the site owner. If enabled for the chat, visitor voice recordings, documents, photos and other files are also sent to kra.name. The visitor’s browser sends the site’s address and the public chat key needed to select the configured chat.

If the site owner enables knowledge-base sync and chooses post types and fields, the plugin sends the selected published WordPress content to kra.name. This happens after the owner enables sync, when selected posts or fields change, during the scheduled refresh, or when the owner requests a full sync. If the owner also enables the product catalog (WooCommerce only), the plugin sends the published products that are visible in the shop: name, SKU, link, prices, currency, stock, categories, tags, attributes, the chosen descriptions and extra fields, the image link and the variations. Requests use the connected AI Worker account’s OAuth access token; a sync token saved by an older version can remain in use until the owner removes it. Opening the plugin settings with a saved chat key, or choosing “Check again”, also contacts kra.name to check the chat and the site’s allowed domain.

If the site owner connects an AI Worker account with the «Connect» button, the owner signs in at kra.name and allows access (OAuth 2.1 with PKCE; no password or API key is stored in WordPress). The plugin then stores the access and refresh tokens on the site, encrypted with the site’s salts, and from the server sends to kra.name: the site’s address and name when it registers the connection; the requests the owner types or dictates into the setup wizard (a voice request is sent as a short audio recording to be transcribed) and the owner’s «Apply» or «Cancel» choices; the chat settings the owner changes (consultant, chat texts, the AI notice and greeting, the chat button icon, lead collection and delivery with its channel settings, knowledge mode), an image the owner uploads as the chat button icon, texts to translate, delivery tests, knowledge sources and questions and answers the owner adds, refreshes, edits or deletes; and requests for the account, the chat list, the connected channels, usage limits and statistics. When a chat is enabled, a front-end page view can schedule a background GET /plugin/me request at most hourly to check for a new widget version. Background requests can also refresh an expired OAuth access token and send selected knowledge-base or catalog changes to kra.name. «Disconnect» revokes the access at kra.name and deletes the tokens; the access covers only the account’s online chats and personas.

For a displayed chat, the plugin automatically merges the required sources into Content-Security-Policy headers set by PHP. This behavior is on by default; the aiworker_chat_merge_csp filter can return false to disable it. A CSP sent by the web server cannot be changed by the plugin.

The service’s terms are at kra.name/offer and its privacy policy is available at kra.name/privacy. Data handled by the service is subject to that policy.