Skip to main content
Widget Setup is where you prepare the chatbot that appears on your website. Use this page after you have selected the domain you want to work on. The setup is organized into four tabs:
  • Content: the messages and language behavior visitors see in the chat
  • Agent: the assistant role and response behavior
  • Style: the visual appearance of the chat widget
  • Embed: the website installation code and widget status
  1. Complete the Content tab so the first visitor experience is clear.
  2. Configure the Agent tab so the assistant matches your support or sales goal.
  3. Adjust the Style tab so the widget fits your brand.
  4. Use the Embed tab to enable the widget and add it to your website.
  5. Test the widget on desktop and mobile before sending traffic to it.

Content tab

The Content tab controls the visitor-facing text inside the chatbot.

Chat mode

Use chat mode to choose whether visitors talk to the AI assistant or to live operators.
  • AI Chat: visitors interact with the assistant you configured in Uppzy
  • Live Chat: visitors are directed to the live operator inbox
Choose AI Chat when you want the assistant to answer based on your Reference Documents. Choose Live Chat when your team wants operators to handle the conversation directly.

Display name

Use the display name field for the assistant name visitors will see. Choose a short, recognizable name such as your company name plus “Assistant” or “Support”. Good display names are:
  • Clear enough for visitors to understand who they are chatting with
  • Short enough to fit comfortably in the widget header
  • Consistent with the rest of your website language

Initial message

The initial message is the first message visitors see when they open the chat. Keep it direct and useful. Good examples:
  • “Hi, how can I help you today?”
  • “Ask me about our products, pricing, or support options.”
  • “I can help you find the right information on this site.”
Avoid messages that promise the assistant can do everything. The assistant should set a clear expectation based on the content you have provided.

Suggested questions

Suggested questions help visitors start a conversation with one click. Add questions that match the most common visitor goals. Use suggested questions for:
  • Product or service questions
  • Pricing or plan questions
  • Support and setup questions
  • Delivery, returns, appointment, or policy questions
Write each question as a visitor would naturally ask it. For example, use “How do I change my plan?” instead of a team label like “Billing workflow”.

Live Chat offline message

Use the Live Chat offline message when chat mode is set to Live Chat and your operators are not available. Write a short message that tells visitors what to expect, such as:
  • “We are offline right now. Leave your message and we will get back to you.”
  • “Our team is currently unavailable. Please leave your question and contact details.”
Keep the message practical and clear. The footer message appears near the bottom of the chat experience. Use it for a short expectation or reminder. Common uses:
  • “Answers are based on the information available on this site.”
  • “For account-specific help, contact our support team.”
  • “Do not share sensitive personal information in chat.”

Launcher bubble messages

Launcher bubble messages appear near the chat button before the visitor opens the widget. Use them to invite visitors into the conversation without distracting them. Keep launcher messages short:
  • “Need help?”
  • “Ask a question”
  • “We can help”

Feedback collection

Enable feedback collection when you want visitors to rate or react to answers. This helps your team identify which answers are useful and which content may need improvement. If your team is not reviewing feedback yet, leave this disabled until you have a review routine.

Daily user message limit

Use the daily user message limit to control how many messages a visitor can send in a day. Set a limit that supports normal browsing while reducing repeated or low-quality usage. Review real visitor behavior before making the limit too restrictive.

Response language mode

Use response language mode to control how the assistant chooses its answer language.
  • Auto: the assistant follows the visitor’s language when possible.
  • Forced: the assistant replies in the default language you choose.
Use Auto for multilingual websites. Use Forced when your support content and support team operate in one language.

Default language

Choose the language that should be used when the assistant needs a default. This is especially important when response language mode is set to Forced.

Agent tab

The Agent tab controls the assistant’s role and response behavior.

Assistant role

Choose the role that best matches how visitors should use the chatbot.
  • General AI: broad website assistance
  • Customer support: help with service, product, and support questions
  • Sales and presales: help visitors compare options and understand plans
  • Documentation and technical guidance: help visitors navigate detailed product instructions
  • Insight and topic analysis: help summarize and explain larger information sets
  • Custom: use your own instructions when the standard roles do not match your goal
Choose one role per domain. If you need different behavior for different sites or brands, configure each domain separately.

Custom instructions

Use custom instructions to guide the assistant’s tone and boundaries. Keep the instructions practical and visitor-focused. Good custom instructions include:
  • What the assistant should help with
  • When the assistant should suggest contacting your team
  • Any wording preferences for your brand
  • Topics the assistant should avoid answering directly
Avoid placing sensitive business information, private credentials, or customer data in custom instructions.

Model

Use the model selector to choose the response model available for the assistant. If you are not sure which option to use, keep the current selection and evaluate answer quality with real sample questions.

Creativity

The creativity setting changes how flexible the assistant is when writing answers.
  • Lower values are better for stable, consistent answers.
  • Higher values can feel more flexible, but may be less predictable.
For support and policy questions, start lower. For discovery or brainstorming use cases, a slightly higher setting may be appropriate.

Style tab

The Style tab controls how the widget looks on your website.

Theme

Choose how the widget handles light and dark appearance.
  • Light: always use the light theme
  • Dark: always use the dark theme
  • System: follow the visitor’s device or browser preference
Use System if your website already adapts to the visitor’s theme.

Profile picture

Upload a profile picture when you want the chat header or assistant identity to use a branded image. Use a clean image that remains readable at small sizes. Supported formats:
  • PNG
  • JPG or JPEG
  • WEBP
  • SVG
Maximum file size: 100KB.

Chat bubble icon

Upload a chat bubble icon when you want to customize the floating launcher button. Use a simple icon with clear contrast against your chosen button color. Supported formats:
  • PNG
  • JPG or JPEG
  • WEBP
  • SVG
Maximum file size: 100KB.

Primary color

Primary color controls the main brand color used by the widget. Choose a color that is readable on your website background and consistent with your brand.

Icon color

Icon color controls the color of the icon inside the chat bubble. Make sure it contrasts with the primary color.

Bubble position

Choose whether the chat bubble appears on the left or right side of the page. Select the side that does not block important website controls such as checkout buttons, consent banners, or navigation.

Embed tab

The Embed tab is used when you are ready to place the widget on your website.

Widget status

Use the widget status switch to enable or disable the chatbot for the selected domain.
  • Enabled: the widget can appear on your website after the embed code is installed.
  • Disabled: the widget should not appear to visitors.
Keep the widget disabled while you are still preparing content, style, or assistant behavior. Enable it when your team is ready to test or launch.

Embed code

Copy the embed code from the Embed tab and add it to your website. If someone else manages your website, send them the copied code and ask them to place it in the shared website layout so the widget can appear on the pages you want. After the code is added, open your website in a new browser window and confirm that the widget appears in the expected position.

Final test checklist

Before launch, test the widget with this checklist:
  1. The widget opens and closes correctly.
  2. The display name and initial message are correct.
  3. Suggested questions match real visitor needs.
  4. Answers use the expected language.
  5. The assistant role matches the goal of the website.
  6. The colors and icons are readable on desktop and mobile.
  7. The chat bubble does not block important page controls.
  8. Feedback controls appear only if your team wants to collect feedback.
  9. The daily message limit is appropriate for expected visitor usage.
  10. The widget status is enabled only when the team is ready.