Introduction
SmartSite Assistant adds an AI chat widget to a WordPress site and gives administrators controls for assistants, site knowledge, tools, channels, appearance, access, analytics, and security.
The plugin is not a single “chat on/off” setting. A visitor message passes through access rules and security checks, uses the active assistant’s instructions and model, may search synchronized knowledge or call an enabled tool, and is then recorded for operational review. Understanding those parts prevents common setup mistakes, such as publishing the widget before its sources and actions have been tested.
Work through this page by starting when you open ai website chat in wordpress. Finish by making sure you add knowledge, test a conversation, then configure access and security for production; if that check fails, the field descriptions help identify whether the problem belongs to content, behavior, transport, or operations.
What this feature does and when to use it
Section titled “What this feature does and when to use it”Read this first to understand the operating model: a locally configured assistant sends visitor requests to OpenAI, can search a synchronized vector store, may call enabled tools, and writes operational logs in WordPress.
Use this feature in the following situations:
- You are evaluating whether the plugin fits a website and need to understand the complete data and request flow.
- You are responsible for setup but different people own content, privacy, security, or third-party integrations.
- You need a map of which SmartSite screen controls a visitor-facing result before changing settings.
Where to find it
Section titled “Where to find it”Before you begin
Section titled “Before you begin”- SmartSite Assistant is installed and activated.
- You are signed in with an account that can manage WordPress options.
Set it up step by step
Section titled “Set it up step by step”- Open AI Website Chat in WordPress.
- Review the tabs from left to right; no setting is changed by opening a tab.
- Complete the OpenAI and assistant setup before publishing the widget.
- Add knowledge, test a conversation, then configure access and security for production.
Fields, controls, and important values
Section titled “Fields, controls, and important values”These are the building blocks that turn a general chat window into an assistant that is useful for your particular website. Assistants shape how replies are written, the knowledge base gives the AI reliable material to draw from, and tools let it retrieve information or complete approved actions. Appearance, access, analytics, and security support that experience without teaching the AI new facts.
| Field, control, or status | What SmartSite Assistant does with it | How to use it and why it matters |
|---|---|---|
| Knowledge Base | Selects WordPress pages/posts, stores metadata, uploads documents, and synchronizes content to an OpenAI vector store. | This is where website pages and approved documents become searchable context for the assistant. Time spent here usually has the clearest effect on factual relevance because the model can ground an answer in material specific to the site. |
| Assistants | Stores local assistant profiles and selects the one used at runtime. | Profiles define the voice, scope, model, welcome message, and instructions used for future conversations. They shape how knowledge is explained, but they do not create separate knowledge libraries or correct missing source material. |
| Tools / Channels | Adds controlled actions or external messaging. WhatsApp is the available external channel. | Tools add controlled data or actions; Channels carry the same assistant into another messaging service. A useful tool can make an answer timely or actionable, while a channel changes delivery rather than the intelligence behind the reply. |
| Design / Settings | Controls widget presentation, text, language, avatar, and visitor access. | “Design / Settings” affects newly generated output rather than rewriting content that is already saved. Choose a supported value, test representative questions, and have a qualified reviewer check language, terminology, latency, and cost where those differences matter. |
| Analytics / Security | Reviews usage and conversations, identifies knowledge gaps, and applies message safeguards. | Analytics shows where visitors struggle and Security controls risky or excessive input. Neither teaches the model automatically: improvement happens when evidence leads to better sources or instructions, while safeguards keep that work available and appropriately bounded. |
How to confirm it is working
Section titled “How to confirm it is working”Confirm Introduction with the smallest representative end-to-end test. When the result differs from the success description, keep the exact input and state so troubleshooting can identify the responsible layer without changing unrelated AI settings.
Practical example
Section titled “Practical example”A support site can sync its help pages, assign an assistant instructed to answer from those sources, and enable a contact-request email tool for questions that require a person.
Recommended practice
Section titled “Recommended practice”- Change one part of Introduction at a time and keep a short record of the previous value and test result.
- Verify the saved result in the screen, visitor session, or connected service that actually consumes the setting.
Important warnings
Section titled “Important warnings”Common problems and focused checks
Section titled “Common problems and focused checks”| Problem | What to check and what to do next |
|---|---|
| Introduction is missing or does not match this guide. | Confirm the plugin is active and the account can manage WordPress options. Confirm activation, administrator access, and that the setup workflow was not completed in another session. |
| A change on Introduction does not produce the expected result. | Keep the exact notice and test case, then review the browser console and WordPress/PHP log. Confirm activation, administrator access, and that the setup workflow was not completed in another session. |
Screen reference
Section titled “Screen reference”- Capture
- Open the main AI Website Chat page with the top tab row visible and Knowledge Base selected. Do not open a record containing real customer data.
- Show
- Plugin title, all main tabs, Knowledge Base summary area
- Viewport
- Desktop, 1440 × 900
- Annotate
- Use numbered callouts only for controls referenced in the procedure.
- Redact
- OpenAI keys, tokens, secrets, personal information, private URLs, IP addresses, and conversation text