Avatar, Landing Screen, Suggestions, and Chat Text
Settings controls the landing screen and input experience; assistant Display Name and Welcome Message remain on the Assistants tab.
This area controls the words and visual identity surrounding the conversation before and while the visitor types. Landing-screen fields introduce the service, suggestions provide one-click example questions, status text explains that the assistant is working, and the disclaimer communicates limitations. These fields are separate from the active assistant’s Display Name and Welcome Message.
Start with the smallest safe step: open chat content and edit landing title/subtitle and conversation card text. Do not consider the task finished before you test every suggestion; selecting one sends it as a message; 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 these fields to set expectations, offer useful entry questions, and align the visible widget with site language.
Use this feature in the following situations:
- You need the landing screen to explain the assistant’s purpose in the website’s own language.
- You want a small set of useful starter questions that the assistant can actually answer.
- You need to change the input hint, response status, disclaimer, or bundled avatar.
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 Chat Content and edit landing title/subtitle and conversation card text.
- Set the input placeholder, responding text, and Suggested questions label.
- Add up to 12 useful suggested questions.
- Review the Markdown disclaimer.
- Save, then open Appearance and choose a bundled avatar.
- Open the frontend landing screen and a conversation to verify all text.
- Test every suggestion; selecting one sends it as a message.
Fields, controls, and important values
Section titled “Fields, controls, and important values”These fields help visitors understand what the assistant is for before they write. Clear landing copy and tested suggestions encourage questions the knowledge base can answer, while the responding text and disclaimer set honest expectations. They do not add knowledge to the model, but good wording reduces vague prompts and can therefore lead to more relevant responses.
| Field, control, or status | What SmartSite Assistant does with it | How to use it and why it matters |
|---|---|---|
| Landing Title | Main greeting on the landing screen. Default Hi! 👋; the UI accepts up to 60 characters. | Use this as the short greeting visitors see before opening a conversation. It should identify the experience immediately without promising that the assistant can answer every question. |
| Landing Subtitle | Supporting line below the landing title. Default How can we help you today?; up to 120 characters. | Use this line to explain the assistant’s scope in one plain sentence, such as the subjects it can help with. Visitors use it to decide whether chat is the right support route. |
| Conversation Card Title | Primary call to action on the card that starts chat. Default Start conversation; up to 60 characters. | Write a short action label that makes opening chat unambiguous. It starts the transition from the landing screen into the conversation; it is not the assistant’s public display name. |
| Conversation Card Subtitle | Explains what the visitor can do before opening chat. Default Ask us anything...; up to 120 characters. | Explain what will happen after the visitor opens the card and what kind of question to ask. Keep it consistent with the synchronized knowledge and enabled tools. |
| Input Placeholder | Hint displayed in the empty message field. Default How can I help you?; saved value is limited to 120 characters. | Use this empty-field hint to show the form of a useful question before the visitor types. It disappears during input, so place lasting limitations in the disclaimer instead. |
| AI Responding Text | Status wording shown while the plugin waits for a response. Default Analyzing your request...; limited to 120 characters. | Use this temporary status to tell visitors that their message is still being processed. Keep it factual and brief; it does not indicate that an answer has been verified or completed. |
| Suggested Questions Label | Heading above the suggestion list. Default Suggested questions; limited to 80 characters. | Use this heading to introduce the clickable starter questions. Choose wording that makes clear they are examples, then keep the label in the same language as the questions and surrounding interface. |
| Suggested Question | One clickable starter question. Up to 12 suggestions can be saved and each is limited to 160 characters. | Each saved item becomes a one-click visitor message, not passive help text. Add only questions the current knowledge or tools can handle, and test all of them because a click can invoke an enabled tool. |
| Disclaimer | Visitor-facing limitations text below the chat. Default states that AI responses may be inaccurate; up to 2,000 characters with basic Markdown. | Use the disclaimer for durable visitor-facing limitations, privacy direction, or a route to human help. Keep Markdown simple, check every link, and do not rely on this notice as consent or an access-control mechanism. |
| Avatar | Selects a bundled PNG, JPG/JPEG, GIF, WebP, or SVG file for the assistant. Invalid or missing selections fall back to an available asset. | Choose a bundled image that remains recognizable at the small header and launcher sizes. Verify its actual fallback and rendering on the public site; this selector does not upload a new custom image. |
How to confirm it is working
Section titled “How to confirm it is working”Use a separate test session to confirm Avatar, Landing Screen, Suggestions, and Chat Text. 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”Offer “What are your opening hours?” only when a synchronized source or safe tool can answer it.
Recommended practice
Section titled “Recommended practice”- Change one part of Avatar, Landing Screen, Suggestions, and Chat Text at a time and keep a short record of the previous value and test result.
- Check the public widget with keyboard, touch, light, dark, desktop, and mobile conditions relevant to the site.
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 |
|---|---|
| Avatar, Landing Screen, Suggestions, and Chat Text is missing or does not match this guide. | Confirm the plugin is active and the account can manage WordPress options. Compare the saved public widget with the preview and account for caching, theme CSS, and viewport width. |
| A change on Avatar, Landing Screen, Suggestions, and Chat Text does not produce the expected result. | Keep the exact notice and test case, then review the browser console and WordPress/PHP log. Compare the saved public widget with the preview and account for caching, theme CSS, and viewport width. |
Screen reference
Section titled “Screen reference”- Capture
- Show Settings → Chat Content with landing fields, three fictional suggestions, and the disclaimer; no personal data.
- Show
- Landing text, input/status text, suggestion list and label, disclaimer, Save
- 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