Quick Start
The quickest reliable path is to add an OpenAI key, create one assistant, synchronize a small knowledge set, test privately, and only then widen visibility.
Quick Start deliberately configures the smallest complete path: a working OpenAI credential, one active assistant, a small synchronized knowledge set, restricted test access, and one verified public conversation. Optional tools, WhatsApp, broad visibility, and detailed visual customization come later because they add more failure points and, in some cases, external side effects.
A reliable setup moves from open setup wizard and save a regular openai api key to the point where you configure security before changing access to everyone. The controls below explain the decisions along that path, including settings that support the conversation without changing the model’s answer directly.
What this feature does and when to use it
Section titled “What this feature does and when to use it”Use this checklist for a first working conversation without configuring every optional feature.
Use this feature in the following situations:
- You have just activated the plugin and want the first reliable test conversation.
- You inherited an incomplete installation and need to establish a known-good baseline.
- You want a repeatable staging checklist before enabling the widget for the public.
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 Setup Wizard and save a regular OpenAI API key.
- Create an assistant with a clear display name, welcome message, instructions, and a Responses-compatible model.
- Select two or three published pages and use Save Selection & Sync.
- Skip tools unless you can test their data or side effects safely.
- Finish the wizard and open Settings → Access; restrict the widget to a test role or user.
- Visit the public site in a separate browser, ask one question whose answer is in the synchronized content, and review Analytics → Chat History.
- Configure Security before changing access to Everyone.
Fields, controls, and important values
Section titled “Fields, controls, and important values”Each item in this short path removes a different reason for a poor first conversation. The OpenAI connection makes responses possible, the assistant profile gives them direction, synchronized content gives them site-specific facts, and the frontend test shows whether visitors can actually use the result. Optional steps can wait, but skipping knowledge means the AI has less website information to work with.
| Field, control, or status | What SmartSite Assistant does with it | How to use it and why it matters |
|---|---|---|
| Skip for now | Advances past optional Knowledge Base and Tools steps; they remain available later. | “Skip for now” represents this part of the setup: Advances past optional Knowledge Base and Tools steps; they remain available later. Its importance becomes clear in the complete workflow—connect it to the next configuration step and test the visitor result instead of treating the item as a stand-alone checkbox. |
| Save Selection & Sync | Saves selected IDs, then starts the actual vector-store sync request. | “Save Selection & Sync” commits the values or advances the workflow; it is not the final proof that everything works. Follow it with the page’s success check, especially when OpenAI, Meta, email, knowledge indexing, or frontend caching is involved. |
| Finish Setup | Marks the wizard completed and opens the plugin dashboard. | Choose “Finish Setup” after checking dependent values and any warning on the screen. A saved configuration can still be incomplete, so confirm the observable result in a fresh session rather than stopping at the green notice. |
How to confirm it is working
Section titled “How to confirm it is working”The reliable proof for Quick Start is the observable result described above. Reproduce it with a realistic example; if only the admin screen changed, continue tracing the workflow until the visitor or connected system sees the intended effect.
Practical example
Section titled “Practical example”For a restaurant, start with the menu, location, and reservations pages before adding files or action tools.
Recommended practice
Section titled “Recommended practice”- Change one part of Quick Start 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 |
|---|---|
| Quick Start 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 Quick Start 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
- Show the completed wizard checklist immediately before selecting Finish Setup, using sanitized assistant and page names.
- Show
- Wizard progress, completed steps, Finish Setup button
- 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