外掛標籤
開發者團隊
原文外掛簡介
AI House answers customer questions using your own website content, with two answer branches:
Quick chat — a direct LLM call for greetings and simple questions.
Deep knowledge — searches a vector database for relevant content, then answers with citations.
On shared hosting the scarce resource is PHP workers, and a chat request that holds one
for several seconds is a real cost. This plugin is built around that limit: every outbound
call has a hard timeout, a circuit breaker, an answer cache, and a quota guard.
Measured cost per chat request: 3 database queries, 1-3 outbound HTTP calls, and zero writes to wp_options.
Providers
LLM: OpenAI, Google Gemini, OpenRouter (including free models)
Vector store: Supabase (pgvector), Pinecone, Qdrant
API keys are stored per provider and encrypted at rest, or supplied as constants in wp-config.php
Knowledge sources
Any public post type you choose: posts, pages, products, custom types
File import — Markdown, CSV, JSON and plain text, with preview before importing
A dedicated Knowledge post type you can edit in wp-admin
Automatic re-index when content changes
Languages
The chat widget ships with Vietnamese and English enabled by default. Twelve languages are built in: Vietnamese, English, Simplified Chinese, Japanese, Korean, Thai, Indonesian, French, German, Spanish, Portuguese and Russian.
Visitors switch language with a button in the widget. The bot answers in the language the visitor actually wrote in — a Vietnamese question typed into a widget sitting on EN comes back in Vietnamese, and the widget follows the visitor’s language. The chosen language is what the answer falls back to when a message carries no signal (“ok”, “iphone”).
Welcome message, placeholder, system prompt and language instruction are configurable per language.
The plugin’s own screens are translated, and you choose which translation to use. Settings → General → Interface language picks the language of the AI House screens — the dashboard, the settings form, the notices — independently of the language of your WordPress profile. The choices are read from the translation files that ship with the plugin (English and Vietnamese today), so a locale added to the plugin shows up there without a code change, and “Follow WordPress” is the default.
Admin dashboard
Overview — messages, sessions, cache hit rate, latency, queue and circuit breaker state
Conversations — browse sessions and read full message threads
Knowledge — import from file, manage items, watch indexing progress
Diagnostics — test connections, inspect the environment and running configuration
Also included
Floating chat widget and [mybot] shortcode, light and dark themes
A AI House shortcut on the WordPress admin toolbar, with quick links to the dashboard, knowledge list and settings
Answer cache keyed per language, with question normalisation
Visitor feedback (helpful / not helpful) stored per message
Source citations returned to the widget so visitors can verify answers
Background queue with automatic retry and backoff
Automatic daily purge of old conversation logs
No jQuery dependency on the front end
External services
AI House has no server of its own. It sends nothing to the plugin authors, and it collects no analytics. It does call services that you configure, with your own accounts, and this section lists every one of them, what is sent, and where to read their terms.
The plugin does nothing until you enter a key. With no key configured there is no outbound request of any kind, other than the two self-tests you can press yourself.
AI model provider — you choose one
OpenRouter — https://openrouter.ai · Terms: https://openrouter.ai/terms · Privacy: https://openrouter.ai/privacy
OpenAI — https://openai.com · Terms: https://openai.com/policies/terms-of-use · Privacy: https://openai.com/policies/privacy-policy
Google Gemini — https://ai.google.dev · Terms: https://ai.google.dev/terms · Privacy: https://policies.google.com/privacy
What is sent: the visitor’s question, the recent turns of that conversation, your system prompt for the current language, and — when the knowledge base has a match — the retrieved text chunks. What is not sent: the visitor’s IP address, any WordPress user data, your other plugin settings, or anything from your admin screens.
Embedding provider — only when you index your own content
The same three providers can supply embeddings (OpenAI, Google and OpenRouter). What is sent: the text of the content you chose to index, split into chunks. This happens only when you press Index knowledge, which you do yourself; nothing is indexed in the background without it.
Vector database — optional
Supabase — https://supabase.com · Terms: https://supabase.com/terms · Privacy: https://supabase.com/privacy
Pinecone — https://www.pinecone.io · Terms: https://www.pinecone.io/terms/ · Privacy: https://www.pinecone.io/privacy/
Qdrant — https://qdrant.tech (self-hosted, or the hosted service; no account is needed for the plugin itself)
What is sent: the text chunks and their vectors, plus the question’s vector when a search runs, so the nearest chunks can be returned. If you turn on the optional conversation mirror, the conversation text is copied there too.
Webhook — optional, off until you set a URL
If you paste a webhook URL (n8n, Zapier, Make, your own endpoint) and switch on the hand-over form, AI House POSTs the visitor’s question and the contact details they typed — name, email, phone and their note — to that URL. You choose the destination; the plugin has no default and sends nothing when the field is empty.
Your responsibilities
You are the data controller for your visitors’ conversations. Before enabling a provider, read its terms, and tell your visitors what you do with their messages in your own privacy policy. WordPress’s own guidance on this is at https://wordpress.org/documentation/article/privacy/.
Shortcodes
Two shortcodes, for two different kinds of page.
[mybot] — the chat widget, inline. Put it on a support page when you want the conversation itself to be the page.
`
[mybot title=”Support” height=”480″ theme=”light” lang=”en”]
`
Attribute
Default
What it does
title
the bot’s name
The heading above the chat. Set by you, so the script leaves it alone.
height
480
Height in pixels of the inline widget.
theme
light
light or dark.
mode
auto
auto (the plugin decides), quick (always the model) or deep (always your content).
lang
the site’s chat language
Which language the chat opens in, when it is one of the twelve.
[mybot_help] — a help-centre block: search over your own pages, then a way to reach a person. This is the shape of a support front page: a heading, a large search box, results as the visitor types, topic links you choose, and a button that opens the assistant. It searches your published pages and posts only — never the knowledge base you imported, which is private on purpose.
`
[mybot_help title=”How can we help?” subtitle=”Search the guides, or ask the assistant.” placeholder=”Search the help pages” button=”Search” ask=”Ask the assistant instead” topics=”Getting started|/getting-started, Billing|/billing”]
`
Attribute
Default
What it does
title
“How can we help?”
The heading.
subtitle
empty
One line under the heading.
placeholder
“Search the help pages”
Text inside the search field.
button
“Search”
The submit button’s label.
label
“Search the help pages”
What a screen reader announces for the field.
ask
“Ask the assistant instead”
The button that opens the chat.
topics
empty
Comma-separated label and URL pairs, drawn as chips under the box. A refused URL scheme is dropped.
Every visible word is an attribute, so the page can be written in your visitors’ language without touching the plugin. No template is needed: paste the shortcode into an ordinary Page and it renders.
