Understand and Create Assistants
An assistant is a profile stored in the WordPress option ai_chat_assistants. Its ID begins with asst_, but creating the profile does not create an OpenAI Assistants API object.
An assistant profile is SmartSite’s local set of instructions and visitor-facing identity. Although its generated ID starts with asst_, the profile is stored in WordPress and is used to build OpenAI Responses API requests; it is not an object you manage in the OpenAI Assistants dashboard. Creating a profile also makes it the active profile immediately.
A reliable setup moves from confirm the regular openai key is configured to the point where you open the public widget under restricted access and test it. 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”Create at least one profile to define the model, public identity, welcome message, and system instructions used by the Responses API.
Use this feature in the following situations:
- You need the first active assistant after installing the plugin.
- You need a separate tested profile for a different tone, model, or instruction set.
- You want to understand which identity fields visitors see and which fields are only for administrators.
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”- Confirm the regular OpenAI key is configured.
- Open Assistants and select Create New Assistant.
- Enter an internal Name and visitor-facing Display Name.
- Write a Welcome Message and focused Instructions.
- Choose a Responses-compatible model.
- Save. The new profile becomes the active assistant.
- Open the public widget under restricted access and test it.
Fields, controls, and important values
Section titled “Fields, controls, and important values”These fields work together to tell the AI who it is, what it should help with, how it should speak, and which model should produce the reply. The internal Name keeps profiles organized, while Display Name and Welcome Message are mainly presentation. Instructions and Model have the strongest direct effect on responses, although neither can supply facts that are missing from the knowledge base.
| Field, control, or status | What SmartSite Assistant does with it | How to use it and why it matters |
|---|---|---|
| Name | Administrator-facing label for distinguishing profiles. | Give each local profile a unique administrator-facing name that explains its site, audience, or purpose. Visitors do not see this value, but clear names prevent editing or activating the wrong assistant when several profiles exist. |
| Display Name | Shown in the public chat header. | Enter the name visitors should see in the public chat header. It affects presentation rather than model behavior, so keep behavioral rules in Instructions and verify the name fits on both desktop and mobile. |
| Welcome Message | Initial assistant message in the conversation. | Write the first assistant message shown when a conversation begins. Use it to state scope and invite a useful question, but do not place rules here that must consistently govern later model responses. |
| Instructions | System behavior guidance; the admin UI supports Markdown formatting. | Describe the assistant’s role, allowed subject matter, answer style, uncertainty behavior, and when to use enabled tools. These instructions guide the model but do not replace server-side permissions, data validation, or security checks. |
| Model | Fetched from OpenAI; new forms default to gpt-4o-mini. | Choose an available OpenAI model for this profile’s runtime responses. The model affects capability, latency, and cost; save the profile and test representative knowledge and tool questions before making it active. |
How to confirm it is working
Section titled “How to confirm it is working”The reliable proof for Understand and Create Assistants 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”Create “Support - Production” internally and show “Acme Support” to visitors.
Recommended practice
Section titled “Recommended practice”- Change one part of Understand and Create Assistants at a time and keep a short record of the previous value and test result.
- Compare the same representative prompts before and after the edit so changes in tone, scope, and tool choice are visible.
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 |
|---|---|
| Understand and Create Assistants is missing or does not match this guide. | Confirm the plugin is active and the account can manage WordPress options. Confirm which local profile is active before editing instructions or blaming the knowledge base. |
| A change on Understand and Create Assistants does not produce the expected result. | Keep the exact notice and test case, then review the browser console and WordPress/PHP log. Confirm which local profile is active before editing instructions or blaming the knowledge base. |
Screen reference
Section titled “Screen reference”- Capture
- Show a completed Create New Assistant form using fictional content, with the model selector closed and no secrets visible.
- Show
- Name, Display Name, Welcome Message, Instructions, Model, Save 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