Customizing the chat widget
Appearance, welcome experience, tone, language, and voice — per website.
Chat configuration is per website: the look, the greeting, the geometry and the behaviour of the widget that greets your visitors. You edit it in Dashboard → Chat Configuration, and saved changes reach your site on its next page load — no redeploy, no code change, no re-pasting the embed snippet.
The screen is a two-column workspace: your settings on the left, a live preview of the widget on the right that updates as you type — so you can check the result before you save.
Picking which website you're editing
Each website has an independent configuration, so a law firm's widget can look and speak differently from a SaaS product's — even under the same account. To edit a different site, pick it in the workspace switcher at the top of the left-hand navigation, under the logo. For a paid site of your own, the switcher also shows the plan badge that tells you which plan that site is on (which decides what you can customize — see Plan availability below).
If a site isn't active yet, the configuration screen is replaced by a "This workspace isn't active yet" card with a Complete payment button that takes you to that site's plan card (a teammate sees the card without the button). Once payment goes through, the full editor opens up (with the plan-gated sections unlocked according to the plan you chose).
The live preview
The right-hand pane is a faithful mock of the embedded widget: a theme with no values of its own shows that theme's defaults, as the widget does. It re-renders reactively as you change a control:
- Colours, logo, avatar, and background come from your Theme Appearance tokens.
- Bubble size, position, and text come from the Bubble settings.
- The greeting and suggested questions come from your Welcome Message.
- Toggling Remove "Powered by" hides the brand footer in the preview instantly.
A Preview pill, with "Reflects unsaved changes" beside it, makes clear this is a mock rather than the real widget.
Which theme it draws in follows your Default Theme setting below: pin it to Light or Dark and the preview shows that, whatever your dashboard is set to. Only on Auto-detect does the preview follow your dashboard's own light/dark setting — which is the case where flipping the dashboard theme lets you check how your colours read both ways.
Saving and going live
A sticky bar at the bottom shows "You have unsaved changes" whenever something differs from what's saved. Save changes saves your edits together; Reset discards your edits and returns to the last saved state. Saved changes reach your live site on its next page load — the embed script tag stays the same. Visitors who already have the chat open see them after they refresh.
Plan availability
What you can customize depends on the plan the selected website is on. Some sections are not plan-gated; the rest unlock as you move up. A locked section shows a padlock, a short explainer of what it does, and an upgrade shortcut that jumps to that site's plan card.
| Section | What it controls | Plans |
|---|---|---|
| Welcome Message | Greeting + suggested questions, per language | Not plan-gated |
| Enable Live Agent | Whether visitors can reach a person | Named under its heading |
| Voice | Text-to-Speech and Speech-to-Text toggles | Named under its heading |
| Transcript storage | How much chat text is kept, and for how long | Not plan-gated |
| Behavior | Default language, default theme | Not plan-gated |
| Bubble Text | Launcher label + show/hide | Not plan-gated |
| Bubble Geometry | Position, size, and bottom and side pixel offsets | Pro and Business |
| Engagement | Auto-open (proactive greeting) | Pro and Business |
| Proactive Messages | Rules for when the agent speaks first | Allowance by plan, under What your plan includes |
| Theme Appearance | Colours, logo, avatar, icons, background image | Named under its heading |
| White Label | Remove the "Powered by" badge | Named under its heading |
Transcript storage is not plan-gated, by design. It is a privacy control, and a privacy control that a downgrade could take away would not be one.
A section is editable only when your plan grants every control in it. Bubble Geometry therefore unlocks as one section on Pro, as does Engagement: Starter grants position and size but not the two pixel offsets, so the section stays locked on Starter and the launcher keeps its default position and size. Theme Appearance likewise unlocks as one section — colours and brand imagery, including the background image. See Billing & plans for how upgrades work.
Welcome Message
(Not plan-gated)
The first thing a visitor sees when they open the chat: a greeting and a short list of suggested questions (shown as tappable chips, the "popular questions").
How the copy gets there — you don't write it. After you activate a site and the first crawl finishes, NovixAgent AI generates the welcome message and suggested questions from your site's own content, then translates them into the languages your site is configured for. No language picking or translating is needed before you launch. The section flips to the filled-in editor live the moment generation completes, no reload needed. You can then edit the text by hand.
Translation is best-effort, per language. The languages are translated in batches, and a batch that fails is not retried indefinitely — so a site can finish generation with most of its languages filled and a few still empty. A visitor whose language did not come back sees the English greeting instead. A later crawl does not fill the gap while your set stays approved (see the note on removing a language below), so if a language matters to you commercially, open its tab once after the first crawl and confirm the text is there; if it is empty, type it in.
The questions are written and checked once, in your site's own language (detected during the crawl), and the other languages are translations of that one approved set. That's why the languages agree with each other: a Spanish visitor and a Japanese visitor are offered the same questions, not two independently invented lists.
Per-language editing
The welcome experience is multilingual by default. When you add a website, the full list of languages NovixAgent AI supports starts switched on — you opt out rather than in.
The tabs arrive with the words, not before. On a site that hasn't been through its first crawl there are no per-language tabs yet: a short notice stands in their place, saying the greeting and suggested questions are generated automatically after payment and the first crawl. The row of language tabs appears once that generation completes, already filled in. The configured-languages list above the notice is live from the start, so you can prune the language set before the first translation.
That's deliberate: the agent already answers visitors in their own language, so leaving the greeting in English would be the only part lagging behind. An extra language has no cost to you — it's a translation of a set that was already written and checked.
At the top of the section you manage your configured languages:
- English is the default: it carries a "Default" badge and has no remove control.
- The other language tabs each have a small ✕. Click it to remove that language — the tab disappears and visitors in that language fall back to English.
- The "Add Language" button appears only when a supported language is missing from your list — on a site whose list was left untouched, it is absent. It offers the missing languages; click one and its tab returns — empty.
Removing a language is not reliably reversible, so treat it as a decision rather than a toggle. Once your welcome set has been generated and approved, it is deliberately frozen against being regenerated — that is what stops a later crawl from silently rewriting copy you have edited. The side effect is that a language you remove and then add back comes back as a blank tab: there is no "regenerate" control, and re-crawling hits the same freeze — a crawl generates a new set only when too many of your suggested questions stop being answered by your site. You can type the greeting and questions into the tab yourself, and that works normally. If you are only pruning to tidy the list, consider leaving the language in place — an unused language has no cost.
Each language tab has its own Welcome Message field and its own Suggested Questions list — add a question with Add, edit inline, remove with the trash icon. Editing one language does not change the others, so a hand-written tweak to your English greeting stays English-only.
You can also switch languages off earlier, in the Add a new website dialog, where the same full list starts selected. Either moment works, and neither is required — a site whose list you leave alone launches fully multilingual.
Keep suggestions honest. The welcome text and suggested questions are what visitors see, but the AI answers from what was crawled from your site. Keep your suggested questions aligned with real page content so a visitor who taps one gets a confident, grounded answer. To fill gaps, add content — see Adding Content.
If you're deciding what to prune, the Languages breakdown in Website Analytics shows the language mix your visitors actually arrive with.
Behavior
(Not plan-gated)
Two settings that control how the widget presents itself on first load:
Language — the widget's interface language: its buttons, labels and the greeting. With Auto (visitor language) the widget checks the browser's ordered language preferences and uses the first one it supports, falling back to English. Pinning a language fixes the interface to that language instead.
It does not decide what language the assistant replies in. The assistant is instructed to match the language the visitor is writing in, turn by turn, whatever this setting says — so a visitor who writes in Portuguese to a widget pinned to English gets a Portuguese answer inside an English interface, and switching language mid-conversation is followed without the buttons changing under them. Only the few fixed replies the system writes itself, such as the short message sent when the model returns an empty reply, follow the pinned language.
Default Theme — whether the widget opens in Light, Dark, or Auto-detect (matches the visitor's system light/dark preference).
The interface includes translations for both left-to-right and right-to-left languages, but the current widget does not guarantee full RTL layout mirroring. If right-to-left presentation is a launch requirement, test the embedded widget on your own pages and devices rather than treating language detection as an RTL certification.
Bubble Text
(Not plan-gated)
An optional label shown next to the floating launcher to invite visitors to start a chat (for example, "Questions? Chat with us").
- Bubble Text — the label text. Leave it empty to show just the bubble.
- Show Bubble Text — a toggle to show or hide the label without deleting it.
One exception, and it's temporary. If the website reaches its monthly message quota, the widget switches to contact-only mode and this label is replaced with a short contact prompt for the duration — including a custom one you wrote — so the button doesn't invite a chat the agent is not taking right now. It returns on its own once the quota has room again, and if Show Bubble Text is off, no label is shown in either case. See What happens when you run out.
Bubble Geometry
(Which plans include it: see the table above)
Where the floating launcher sits and how big it is:
- Bubble Position — whether the launcher anchors to the Bottom Right or Bottom Left.
- Bubble Size — Small, Medium, or Large.
- Bubble Offset Bottom — distance in pixels from the bottom edge.
- Bubble Offset Side — distance in pixels from the side edge.
The section unlocks as one, so on Starter the four fields are locked and the launcher keeps its defaults.
The offsets are handy when the launcher would otherwise overlap a cookie banner, a "back to top" button, or your own floating controls.
Engagement (auto-open)
(Which plans include it: see the table above)
Proactively open the chat to greet visitors before they ask — useful for promotions and support.
- Auto Show Chat — a toggle to auto-open the chat after the page loads.
- Auto Show Delay (s) — how many seconds to wait before auto-opening. An integer from 0 to 60 seconds. Type more and the field shows a range error, and saving stays blocked until the value is fixed.
It's shown in the live preview so you can gauge how eager it feels; a short delay tends to convert without feeling pushy.
Proactive Messages
(allowance by plan — see below)
Rules for when the agent should start the conversation instead of waiting to be clicked. When a rule fires, a second bubble appears above the launcher with a short invitation. The rule shows the invitation; the visitor opens the chat by clicking it.
Each rule has:
- Show it — the trigger.
- After reading for a while — fires once the visitor has spent N seconds on the page. It counts visible time: the timer pauses while the tab is in the background, so a page left open for an hour does not count as an hour of reading. Works on phones too.
- When about to leave the page — fires when the pointer crosses the top edge of the page, towards the tab bar or address bar. Desktop only — a touch screen has no cursor, so this trigger never fires on one. If most of your visitors are on phones, use the reading trigger.
- After (seconds) — 10 to 600, for the reading trigger.
- Message — up to 120 characters. Leave it empty and the visitor sees a standard invitation written in the language configured for the site — which, with the language left on Auto, means English.
- A switch to turn the rule off without deleting it, and a bin to remove it. The default rule a new site starts with stays — its bin is disabled until you first save a change to it, and deleting the site's last rule brings that default back, switched on; the switch is how you silence it.
The limits that keep it an invitation
These are fixed and not configurable, on purpose:
- At most one invitation per day in a visitor's browser — across every rule and every page. If the browser blocks site storage, the limit is one per page load.
- Never after they have already opened the chat in that browser tab. If the browser blocks site storage, that holds only for the page they opened it on.
- Only one rule fires per visit. If several qualify, the first one wins and the rest stay quiet for that visitor.
What your plan includes
| Starter | Pro | Business | |
|---|---|---|---|
| Active rules | 1 | 3 | Unlimited |
| Your own wording | — | ✓ | ✓ |
Where the table above shows no tick for Your own wording, the message field is locked and visitors see the standard invitation in the site's configured language. Where it shows one, you can write your own — it is shown as you typed it, so keep it short and human.
A new website on a plan that allows at least one rule starts with one rule already set up (reading trigger, 45 seconds, standard wording) so the agent is useful from day one. Switch it off if you would rather it stayed silent — that rule is permanent, so switching off is the way to retire it rather than deleting it.
Saved changes reach live widgets on their next page load; a visitor already on a page keeps the previous rules until they reload.
Theme Appearance
(Business)
Brand the widget's colours and imagery. The settings here write into one per-theme design system, and each token has independent Light and Dark variants — an empty value falls back to the widget's own default for that theme, never to the opposite variant.
The section unlocks as one — it becomes editable once your plan grants every token in it (colours and the brand-asset URLs, including the background image). Because the background image is part of the section, Theme Appearance becomes fully available only on the plans named under the heading; on the others it shows a single plan-lock plate over the (dimmed) grid.
Light / Dark tabs
Switch between the Light and Dark variant tabs to set values for each theme separately. A small dot on a tab means that variant has at least one custom value. On Auto-detect visitors see whichever theme matches their system preference, so set both if your brand colours differ between modes.
Apply to both — the Both button beside a token copies the current tab's value into the other theme, so you don't have to enter the same value twice.
Brand assets (URLs)
Paste a publicly reachable HTTPS URL for each asset. The customizer does not upload or host these files; the live widget requests them from the URL you provide. If the browser fails to reach or decode an image, the custom image may not appear: a surface with built-in artwork may continue to show its default, while an unavailable background image leaves the background unset. Check the preview and the live embedded widget after saving.
- Widget Logo — the logo shown in the widget header.
- Bot Avatar — the avatar shown alongside the assistant.
- Bubble Icon — a custom icon for the floating launcher (instead of the default brand mark).
- Background Image — a background image for the chat panel.
Colours
- Bubble Color — the launcher's fill.
- Background Color, Accent Color, Text Color, Header Color, User Message Color, Bot Message Color — the rest of the palette, each a colour picker with a matching hex field.
White Label
(Business)
- Remove "Powered by" — hides only the NovixAgent AI branding footer at the bottom of the widget so it reads as native to your brand. Toggling it updates the live preview immediately. It does not remove AI disclosures: the explicit "You are chatting with an AI, not a person." notice, per-message "AI assistant" labels, and the AI-error disclaimer stay visible; no setting hides them.
For deeper branding options — the full structured appearance-token set (no free-form CSS) — see Advanced Customization.
Voice
(Pro and Business)
Two toggles decide whether your widget offers voice — both default to on when your plan includes it:
- Text-to-Speech — visitors can have replies read aloud. Turn it off to hide the listen control.
- Speech-to-Text — visitors can talk to the agent with their microphone (voice input and "Voice mode"). Turn it off to hide the microphone button.
Turning a toggle off and saving removes that control from the widget on its next load; the live preview updates as you switch. Voice is gated by plan (the plans that include it are named under the heading); the languages, browser support, and the Text-to-Speech character budget are covered in Voice Features.
Enable Live Agent
(Pro and Business)
A single switch — Enable Live Agent — that lets visitors reach a person when one of your operators is online, on your website widget and on the messaging channels you connect.
It is the same switch as the one in Live Chat → Settings, offered here as well so you can turn it on where you're previewing the widget and see the effect straight away. There is no second setting to keep in sync. Availability, working hours, operators and the rest of live-chat staffing stay in Live Chat → Settings — see Live Agent.
On a plan without Live Agent the switch carries a plan pill and is locked.
Transcript storage
(Not plan-gated)
How much of the assistant's own chat text is kept for this website, and for how long. Two controls:
- Store chat text — Do not store bot chat text, Only turns the bot did not answer confidently (the default), or Store every bot chat turn.
- Keep text for (days) — a retention window picked from a short list, or Default to inherit the installation default. The choices and the maximum are shown on the control itself; the retention periods are published in the Data Retention Policy.
Two scope limits worth knowing before you rely on it:
- It covers the assistant's own chat text only. Messenger channels and live-operator chats are stored separately and Store chat text does not apply to them, though a closed live-operator chat is also deleted once it is older than the retention window set here.
- Changing what is stored affects new conversations only. Turning storage up recovers no past text; turning it down doesn't erase what's already stored — the retention window does that. A new retention window, by contrast, applies to text already stored as well as to new text.
Whatever you keep is readable under Analytics → Conversations on the plans that include that tab (see Website Analytics), while storage itself is not plan-gated. The full explanation of that asymmetry, and how to pick a window, is in Managing your account.
Accessibility
Accessibility behaviour is built into the widget and is not plan-gated; there is no setting to turn it on:
- Interactive controls are keyboard-operable and show visible keyboard focus. Dialogs such as the policies view move focus inside, keep Tab focus within the dialog, close with Escape, and restore focus when they close.
- On your website, Escape on the main chat view closes the widget, like its close button. An open dialog or menu takes the key first, so that Escape closes only the dialog or menu. While a visitor is talking to a live agent, Escape does not close the widget, so a stray key press cannot end that conversation. When the widget closes, keyboard focus returns to the launcher, unless the visitor has already moved it elsewhere on your page.
- New chat messages use a polite live region, while warnings and time-sensitive failures use status or alert announcements so screen-reader users receive changes that are not caused by page navigation.
- The widget respects the visitor's operating-system Reduce motion preference by shortening or stopping its animations, and the welcome animation also checks that preference directly.
These are implemented accessibility features, not a claim that the widget or the website embedding it has passed a particular WCAG conformance level or third-party certification. Your page, colour choices, surrounding controls, and integration still affect the accessibility of the complete experience.
What's configured elsewhere
One thing that shapes the chat experience lives on its own screen, not here:
- Tone and persona — the widget's look lives here; the agent's voice — its persona, tone, guardrails, and how formal or friendly it is — comes from your AI Template. See AI Templates.
Tips
- Keep the welcome message short and outcome-focused — "Ask me about pricing, demos, or integrations" beats a paragraph.
- Pick a bubble colour that contrasts with your site so the launcher is easy to find (Theme Appearance).
- Preview in both light and dark before you ship — on Auto-detect the widget follows the visitor's system setting, not yours.
- Leave the language list alone unless you have a reason to prune it — the full list is on from the start, so a multilingual audience is covered without extra work.
Stuck on a look? Email support@novixagent.ai — we're happy to help you dial it in.