Frequently Asked Questions
These answers summarize the behavior found in the current plugin; use the linked guides for procedures and limits.
The FAQ resolves the implementation details most likely to be misunderstood: local assistants versus OpenAI Assistant objects, selection versus sync, available channels and file types, retained data, log cleanup, and current security action behavior. Each answer is a routing point to a complete procedure rather than a substitute for it.
Start with the smallest safe step: identify the closest question in the controls table. Do not consider the task finished before you record any mismatch for the documentation maintenance workflow; this is where the configuration is tested in the context that truly consumes it.
What this feature does and when to use it
Section titled “What this feature does and when to use it”Use this page for quick orientation before opening a deeper workflow.
Use this feature in the following situations:
- You need a quick source-checked answer before choosing the correct detailed guide.
- A README or UI label appears to conflict with the behavior of the current plugin.
- You are onboarding an administrator and want to correct common mental models early.
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”- Identify the closest question in the controls table.
- Open the related workflow.
- Confirm that the deployed plugin matches the documentation before relying on exact labels or defaults.
- Run a safe test rather than assuming a setting is live.
- Record any mismatch for the documentation maintenance workflow.
Fields, controls, and important values
Section titled “Fields, controls, and important values”These answers clarify product boundaries that commonly lead administrators to configure the wrong area. Knowing what is local, what is remote, and what is automatic helps direct quality work to the right place—for example, improving shared knowledge rather than creating another profile, or synchronizing a supported file instead of assuming upload alone makes it searchable.
| Field, control, or status | What SmartSite Assistant does with it | How to use it and why it matters |
|---|---|---|
| Are assistants OpenAI Assistant objects? | No. Profiles are stored locally and used with the OpenAI Responses API. | No. They are local WordPress profiles used with the Responses API. This matters because changing a profile affects runtime instructions and presentation locally, while knowledge remains in the site’s shared vector store. |
| Does selecting a page synchronize it? | Not by itself. Save/sync operations must complete; the wizard button performs both stages. | Read “Does selecting a page synchronize it?” as evidence that a particular workflow stage did or did not finish. A completed badge cannot tell whether content is relevant, instructions are clear, or delivery works end to end, so pair it with a realistic test. |
| Which files are supported? | PDF, DOCX, PPTX, and TXT, each under the WordPress maximum upload size. | Use PDF, DOCX, PPTX, or TXT below the WordPress upload limit. A supported extension only permits processing; the document improves answers after indexing succeeds and its structure and content retrieve well. |
| Which channels exist? | WhatsApp is the only available external channel. | WhatsApp is the available external messaging channel. It reuses the active assistant, knowledge, tools, security, and logs, so configuring the channel does not create a separate answer style or knowledge set. |
| Does deactivation erase settings/logs? | No; it removes copied frontend assets. | No. Deactivation removes copied frontend assets while preserving configuration and stored data. This supports recovery, but it also means deactivation alone is not a privacy deletion or complete uninstall procedure. |
| Is there automatic local log retention? | No automatic cleanup was found; manual 30/90/180/365-day cleanup is available. | No scheduled cleanup was found. Administrators choose manual age cutoffs, which means retention remains an operational responsibility and old conversations will not disappear simply because newer ones are being recorded. |
| Can warn and flag differ? | For blocked words/automated threshold, only Block denies; Warn and Flag currently both allow and flag. | For blocked-word and automated-threshold handling, Warn and Flag both allow the request and record flags; only Block denies it. Choose labels with that behavior in mind rather than expecting a separate visitor warning. |
How to confirm it is working
Section titled “How to confirm it is working”Use a separate test session to confirm Frequently Asked Questions. This keeps existing login, browser storage, and response history from hiding the change, and it shows whether the result reaches the complete workflow rather than stopping at WordPress storage.
Practical example
Section titled “Practical example”For a missing updated answer, follow Sync Statuses before changing the assistant model.
Recommended practice
Section titled “Recommended practice”- Change one part of Frequently Asked Questions 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 |
|---|---|
| Frequently Asked Questions is missing or does not match this guide. | Confirm the plugin is active and the account can manage WordPress options. Preserve logs and configuration evidence before changing files, caches, update state, or stored data. |
| A change on Frequently Asked Questions does not produce the expected result. | Keep the exact notice and test case, then review the browser console and WordPress/PHP log. Preserve logs and configuration evidence before changing files, caches, update state, or stored data. |
Screen reference
Section titled “Screen reference”- Capture
- Show the main AI Website Chat tabs with numbered callouts matching common tasks in this FAQ.
- Show
- Knowledge Base, Assistants, Tools, Channels, Analytics, Security, Settings
- 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