Customize the chat widget's appearance
Set the chat widget's language, theme, font, colors, avatar, launcher, welcome messages, suggested and follow-up questions, source links, previous chats and visitor attachments, open it automatically or in Center Stage, show it to a share of visitors, add visitor tools and campaign tags, or import your logo and colors.
The Appearance tab controls how the chat widget looks and what it says before a visitor types. Your site loads these settings from intoCHAT on every page view, so you never edit the embed code to change them.
Where to find it
Open your agent and select the Appearance tab. The Live preview beside the controls shows the widget as it will render, with the launcher on the side you chose. On smaller screens, tap the Preview button instead.
Edits go live only when you click Save changes at the top of the page. Then reload your website to see them.
Match your website
Under Match your website, enter your domain and click Detect branding. intoCHAT reads your homepage and proposes a logo and four colors. Nothing changes until you apply the result:
- Apply colours & logo sets all four colors and uses the logo as the agent avatar.
- Colours only sets the colors and keeps your current avatar.
If your brand color is too light for white text, the importer darkens it. The logo is cropped to a circle, so a square mark works better than a wide wordmark. The launcher icon is never changed. A lookup doesn't use a crawl credit.
Wording
| Field | What it does |
|---|---|
| Widget language | The language of the widget's own buttons, labels and notices. See Widget language below. |
| Welcome message | The agent's first message in every new chat, up to 500 characters. If empty, visitors see a greeting in the widget's language, in English Hello! How can I help you today? Click Add another message to add up to 3 more of the same length. Each appears as its own bubble after the first. |
| Suggested questions | Buttons above the message box, shown until the visitor sends a first message. A simple list or titled groups; see Suggested questions below. |
| Suggest follow-up questions | A switch. When on, the agent offers short questions under its latest reply; see Follow-up questions below. |
| Show sources under replies | A switch, off by default. When on, links to the website pages a reply drew on appear under it; see Sources under replies below. |
| Rich replies | A switch, on by default. When on, the agent can show a table, cards or quick-reply buttons under its text when they help; see Rich replies. |
| Let visitors reopen earlier chats | A switch, off by default. When on, visitors can reopen their earlier chats on the same device; see Previous chats below. |
| Let visitors attach files | A switch, off by default and saved as soon as you switch it. When on, visitors can send images and PDFs in the chat; see Visitor attachments below. |
| Launcher tooltip | The label next to the launcher. It appears one second after the page loads, hides after three seconds and shows again on hover. If empty, it reads "Chat with" followed by your agent name, such as "Chat with Example Bikes", in the widget's language. |
| Input placeholder | The hint text in the message box. If empty or left as Type your message..., the hint appears in the widget's language. |
| Footer text | Small print under the message box, such as a privacy notice, up to 300 characters. Web addresses starting with http:// or https:// become links that open in a new tab. It sits above the "Powered by intoCHAT" credit. |
Widget language
Widget language sets the language of the text the widget shows by itself. The widget speaks English, German, French, Italian and Spanish. The setting covers:
- the default welcome greeting and the default message box hint
- buttons and their tooltips, such as send, reset and close
- the temporary chat button and the notice that its messages aren't saved
- the message limit notice and error messages
- the notices shown when the chat isn't available, for example "This agent is private."
- the "Powered by intoCHAT" credit
- the rating buttons, Helpful and Not helpful
- product cards, for example "In stock" and "View product"
- the "Sources" label under replies
- the labels of rich replies, such as "More" and "Quick replies"
- the Previous chats button and list
- the paperclip for visitor attachments and its messages
- the "From the web" label under replies that used web search
- the time picker of Booking with Cal.com or Calendly
- the screen reader note that a link opens in a new tab
- the default launcher tooltip
- the lead form
| Option | Language the widget uses |
|---|---|
| Automatic (visitor's language) | The default. First the language of the page the chat is on, taken from the lang attribute of its <html> tag, for example <html lang="de">. If that isn't one of the five, the first of the five among the visitor's browser languages. Otherwise English. |
| English, Deutsch, Français, Italiano, Español | Always this language, for every visitor on every page. |
Only the chat bubble reads the page language: the script tag, the WordPress plugin and the Shopify snippet. The inline iframe and the direct link have no host page, so with Automatic they use the visitor's browser languages.
Visitors are addressed formally: with "Sie" in German, "vous" in French, "usted" in Spanish and polite impersonal phrasing in Italian. The Live preview and the Playground show Automatic in English, and a fixed language in that language.
Text you write is shown exactly as you wrote it, in every language: a welcome message you set, a placeholder you changed, the launcher tooltip, the footer text, suggested questions and group titles, custom button labels, and the message and your own fields in the lead form. On a multilingual site, keep these short and in your main language.
Suggested questions
Suggested questions show above the message box until the visitor sends a first message. Clicking one sends it. Above the field, choose how to show them:
- Simple list: up to 6 questions of up to 120 characters, as buttons. Type a question and press Enter or click Add.
- Groups: up to 4 groups, each with a title of up to 40 characters and up to 5 questions of up to 150 characters. Click Add group for another group, and use the arrows to reorder groups and questions. With two or more groups, the titles show as tabs, and the visitor picks a tab to see its questions. A single group shows its title as a heading above its questions.
A group without a title or without questions isn't shown, and a note under it in the editor says so. When you switch to Groups, your list becomes the first group, or the first two when it has more than 5 questions, and you write the titles. The list itself is kept: switching back to Simple list brings it back, and the widget shows the list whenever no group can be shown.
Follow-up questions
With Suggest follow-up questions on, the agent ends each reply with 2 or 3 short questions the visitor might ask next. They appear as buttons under the latest reply, and clicking one sends it as the visitor's next message.
- The agent writes them for each reply, in the same language as the reply.
- Each is plain text of up to 80 characters and never contains a link. Questions that break these rules are dropped, so a reply can show fewer, or none.
- They show only under the latest reply. They don't appear under a reply that shows the lead form or confirms a hand-off by email.
- They are written together with the reply, so they don't count as an extra message. A visitor who clicks one sends a message, which counts like a typed one.
With the switch on, the Live preview offers Before first message and After a reply. After a reply it shows example questions; the agent writes its own for each answer. The Playground uses the switch as it is on screen, so you can try it before you click Save changes.
Sources under replies
With Show sources under replies on, a line starting with "Sources" appears under the agent's replies, with links to up to 3 website pages the reply drew on. Each link shows the page's name and opens the page in a new tab.
- The links come from the knowledge excerpts intoCHAT gave the agent for that reply, in the order search ranked them. The AI model doesn't choose or write them, so it can't invent a link.
- Only website pages have links. Files, text snippets and Q&A pairs have no address, and Notion pages are never linked, so a reply based only on them shows no sources.
- The word "Sources" follows the widget language. Page names are shown as they appear in your knowledge.
- No sources appear under a reply that confirms a hand-off by email, under a reply in which the agent itself brings up the lead form or shows a chat form, or under a reply without text.
- Pages found by web search appear on their own line starting with "From the web", whether this switch is on or off.
- Sources are saved with each reply. Turning the switch off hides them under earlier replies too. Turning it on doesn't add them to replies written while it was off.
The Playground uses the switch as it is on screen, so you can try it before you click Save changes. The Live preview doesn't show sources.
To see which knowledge a reply used, including files, text and Q&A pairs, open Why this answer under the reply on the Conversations tab; see Conversations and stats.
Previous chats
With Let visitors reopen earlier chats on, visitors can go back to conversations they had before in the same browser.
- When a visitor starts a new chat with the reset button, or opens an earlier chat, the chat they leave is kept in a list. Only chats in which the visitor wrote something are kept.
- A Previous chats button then appears in the chat header. It lists up to 10 earlier chats from the last 90 days, each with the visitor's first message and the time of the last message.
- Clicking a chat reopens it, and the visitor continues the same conversation: new messages are added to it. A line under the header says so and offers Back to current chat.
- Forget these chats on this device clears the list in this browser. The chats themselves aren't deleted and stay on your Conversations tab.
- The button doesn't appear in a temporary chat.
The list is kept only in the visitor's browser, never in an account. With the chat bubble, it belongs to the website the bubble is on and follows the visitor from page to page of that site. The inline iframe and the direct link keep their own list. Anyone who uses the same browser, such as on a shared computer, can see and continue those chats.
Turning the switch off hides the button and the list. The conversations stay on the Conversations tab.
Visitor attachments
With Let visitors attach files on, a paperclip next to the message box lets visitors send images and PDFs with a message, for example a photo of a damaged product or a PDF invoice. The agent reads them together with the message text.
The switch is saved as soon as you flip it, separately from Save changes. What visitors can send:
- Images in PNG, JPEG, WebP or GIF format, and PDFs. The type is checked from the file's content, not its name.
- Up to 4 MB per file and up to 3 files per message. Large photos are scaled down in the visitor's browser first, to at most 2,048 pixels on the long side. GIFs and PDFs are sent as they are.
- Visitors click the paperclip, drag files onto the chat, or paste an image such as a screenshot. Each file uploads as soon as it is added, and the message can be sent once the uploads have finished.
- Each visitor can upload up to 30 files an hour to one agent, and each agent accepts up to 500 files an hour. Beyond that, visitors see "Too many files right now. Please try again later."
How the agent uses them:
- The files are sent with the message, like the message text, to the provider of the model that writes the reply: OpenAI, Anthropic or Google. Every model reads images. PDFs are read by OpenAI's models only: with an Anthropic or Google model, the agent is told that a PDF was attached but can't open it, and answers from what the visitor wrote. See Choose a model. The agent is told to treat the files' content as information from the visitor, not as instructions.
- Only the files of the current message are read in full. In later messages, the agent knows only the files' names, so a visitor who wants to ask about a file again may need to attach it again.
- A message with files counts the same as one without. See Plans and limits.
Where they are kept:
- Files are stored privately with the conversation, without a public link. In the visitor's chat, images show as thumbnails and PDFs as their name and size, also after a reload.
- On the Conversations tab, the transcript shows them in the visitor's message: click an image to open it in a new tab, or a PDF to download it. The CSV export lists the file names. See Conversations and stats.
- Deleting a conversation deletes its files. Files that were uploaded but never sent are deleted after 24 hours.
Attachments work in the chat bubble, the inline iframe and the direct link, the Help Page and the Playground, which uses the saved switch. They aren't offered in temporary chats, because nothing in them is saved. Turning the switch off removes the paperclip; files already sent stay with their conversations.
Images
- Agent avatar appears next to each of the agent's messages, not in the header. Without one, the messages show "AI", or "KI" or "IA" depending on the widget language. Use a square image of at least 64 × 64 pixels.
- Launcher icon replaces the default sparkle icon. A custom icon fills the whole 56-pixel launcher, so the launcher color no longer shows.
Both accept PNG, JPG, GIF or WebP up to 5 MB.
Style
Under Style you set the chat window's theme, font and corners.
| Theme | What visitors see |
|---|---|
| Light | A white window, as the widget has always looked. The default. |
| Dark | A dark window. |
| Auto | Light or dark, following each visitor's device setting. The window switches if the visitor changes the setting while the chat is open. |
In the dark theme, your header, visitor message and launcher colors stay as you set them. The agent's messages turn dark grey only while they still use the default light grey; a color you picked stays. With Auto, the Live preview has Light and Dark buttons to check both. The launcher tooltip and the welcome pop-up follow the theme too: white with dark text, or dark grey with light text.
Font applies to everything inside the chat window: System default, Inter, Roboto, Open Sans, Lato, Poppins or Serif (Georgia). System default and Serif use fonts already on the visitor's device. The web fonts are served by intoCHAT, and visitors only download the one you pick. The launcher tooltip and the welcome pop-up sit on your page, outside the chat window, so intoCHAT can't load fonts for them. They ask for the chosen font by name and use it when your page or the visitor's device has it; otherwise they use the device's system font. With Serif, they use Georgia or another serif font.
Corners sets how round the message bubbles, the message box, the send button, the suggested questions and custom buttons are: Sharp, Soft or Rounded. Soft is the default and matches how the widget looked before the setting existed.
Colors
Start from a preset under Colours (Ink, Ocean, Forest, Plum, Ember), then adjust any field with the color picker or a hex value.
| Color | Used for |
|---|---|
| Header | The top bar of the chat, which shows the agent name |
| Launcher bubble | The round launcher button and the send button |
| Visitor messages | The background of the visitor's messages |
| Agent messages | The background of the agent's messages |
Placement
Under Placement, set Side of the screen to left or right. The launcher sits 20 pixels from that bottom corner. On desktop, the chat opens as a 380 × 600 pixel window above it, unless it opens in Center Stage. On screens 768 pixels wide or narrower, the chat fills the screen. The chat window has a close button in its header, and clicking the launcher again also closes it.
Removing "Powered by intoCHAT"
The Show "Powered by intoCHAT" switch controls the small credit under the message box. On the Free plan the switch is locked on, and the link Remove the intoCHAT credit on any paid plan below it opens your billing settings. On any paid plan you can switch it off. See pricing.
Launcher behaviour
Under Launcher behaviour, two optional invitations bring visitors into the chat without waiting for a click. Each has a switch and a delay of 0 to 300 seconds on the page.
- Show the welcome message above the launcher shows your welcome messages as small bubbles beside the launcher, after 5 seconds unless you change the delay. Your avatar sits next to the first one, and long messages are cut after four lines. Clicking a bubble opens the chat. The × button dismisses them.
- Open the chat automatically opens the chat window by itself, after 10 seconds unless you change the delay. It is skipped on screens 768 pixels wide or narrower, where the chat would cover the whole screen.
A visit lasts until the visitor closes the browser tab. Auto-open runs at most once per visit. The pop-up appears again on each new page until the visitor dismisses it. Neither appears for the rest of the visit once the visitor has opened or closed the chat, dismissed the pop-up, or the chat has opened automatically. If both are on, the shorter delay comes first, and opening the chat removes a pop-up that is showing.
Show the chat to a share of visitors
Under Rollout and opening, Show the chat to a share of visitors shows the launcher to only part of your visitors, for example to try the agent on 20% of your traffic first. Turn it on and enter a share from 1 to 99%. Off, everyone sees it.
- Each browser is placed in or out once per agent and stays that way, so a visitor doesn't see the launcher appear and disappear between pages or visits. The choice is a random number kept in the visitor's browser, in your site's local storage, or in a cookie when local storage is blocked. If the browser blocks both, the choice is made again on each page.
- Raising the share keeps everyone who already sees the launcher and adds more visitors. Lowering it removes some.
- Visitors who are left out see no launcher, no welcome pop-up and no auto-open, and the chat window doesn't load. If your page calls
IntoChat.open(), for example from a "Chat with us" button, the chat still opens for them. - The Playground, preview links and the Help Page always show the chat. So do the inline iframe and the direct link, which have no launcher.
To check how it looks for a visitor who is left out, open your site in a private window a few times; each private window is a new browser.
How the chat opens
Under Rollout and opening, How the chat opens has two choices:
- Corner panel: the 380 × 600 pixel window above the launcher, as before. The default.
- Center Stage: a larger window, up to 760 × 820 pixels, in the middle of the page. The page is dimmed behind it and doesn't scroll. Pressing Esc or clicking the dimmed page closes it, like the close button in the chat header. While it is open, the keyboard stays inside the chat; when it closes, focus goes back to where it was. Screen readers announce it as a dialog.
Center Stage opens the same way as the corner panel: from the launcher, with auto-open, from a welcome pop-up bubble, or with IntoChat.open(). On screens 768 pixels wide or narrower, the chat fills the screen either way. The Live preview always shows the corner panel, and the inline iframe and the direct link don't change.
Visitor tools
Under Visitor tools, three switches add buttons to the chat window. All are off until you turn them on and click Save changes.
Copy a reply
Let visitors copy replies adds a copy button under each of the agent's replies. It copies the reply as plain text, without formatting and without the buttons, product cards, forms or sources under it. Links keep their address in brackets. The button shows "Copied" for a moment, in the widget's language.
Dictation
Let visitors dictate messages adds a microphone button next to the message box. The visitor clicks it, speaks, and the words appear in the message box in the widget's language. Clicking it again stops. Nothing is sent by itself: the visitor reads the text, corrects it if needed and sends it.
- The button appears only in browsers with speech recognition, such as Chrome, Edge and Safari. Firefox doesn't have it, so Firefox users don't see the button.
- The browser asks the visitor for the microphone the first time. If they refuse, the button says the microphone is blocked.
- The recognition is done by the browser, not by intoCHAT. Some browsers send the audio to their maker's servers for this, for example Chrome to Google. intoCHAT receives only the text the visitor sends.
- In an inline iframe on your own site, add
allow="microphone"to the<iframe>tag, or the browser blocks the microphone and the button doesn't appear. The chat bubble does this for you.
Delete my chat
Let visitors delete their chat adds a delete button to the chat header. After the visitor confirms, intoCHAT deletes the conversation with all its messages and the files the visitor attached, and a new, empty chat starts. The confirmation tells them: "This chat and any files you sent will be deleted, and a new chat starts. This can't be undone. Contact details, form answers and bookings you sent stay with the business."
What this means for you:
- The conversation disappears from your Conversations tab and from the conversation counts, as when you delete it yourself. See Conversations and stats. Its messages still count toward your plan's monthly messages.
- Leads, form answers and bookings from that chat stay. A lead shows "Conversation deleted" instead of the chat.
- If the chat was in the visitor's Previous chats list, it leaves the list.
- A question from that chat that was already listed under Questions to improve can still show there as an example.
- The button appears only once the visitor has written something, and never in a temporary chat, which isn't saved anyway.
Keep campaign tags on links
With Keep campaign tags on links on, the chat keeps your campaign tracking when a visitor clicks a link in the chat. When the address of the page the visitor is on has utm_source, utm_medium, utm_campaign, utm_term or utm_content tags, the chat adds them to links in the agent's replies and to custom buttons that lead to the same website.
- The same website means the same domain, subdomains included: on
www.example.com, links toshop.example.comget the tags. Links to other websites never do. - A link that already has any
utm_tag stays exactly as it is. - Only those five tags are read, each up to 100 characters. A longer value is left out. Nothing else from the page address is used.
- The tags stay in the visitor's browser. They are passed from your page to the chat window directly, not sent to intoCHAT's servers, and not stored anywhere. Click counts for custom buttons record the link as you wrote it.
- Only the tags in the address of the current page count. If the visitor moves to a page without tags, links in the chat no longer get them.
Only the chat bubble does this. The inline iframe and the direct link don't know the address of your page.
Common problems
- Changes don't show on your site. Click Save changes, then reload the page. The widget fetches its settings fresh on every page load.
- The widget's buttons and notices are in the wrong language. With Automatic, the widget follows the
langattribute of your page's<html>tag before the visitor's browser. Correct the attribute, or choose a fixed Widget language. Text you wrote yourself stays as written. - Follow-up questions don't appear. Check that Suggest follow-up questions is on and saved. They show only under the latest reply, and never under the lead form or a hand-off confirmation.
- No sources appear under a reply. Check that Show sources under replies is on and saved. Only website pages have links, so replies based on files, text, Q&A pairs or Notion pages show none.
- The launcher color doesn't change. A launcher icon is set and covers the color. Remove the icon to use the color again.
- "Logo could not be imported". The colors were still applied. Upload a logo yourself under Agent avatar.
- The launcher doesn't appear on your site. If Show the chat to a share of visitors is on, your browser may be among the visitors who are left out. Open the site in a private window, or check it on a preview link, which always shows the chat.
- The microphone button doesn't appear. Check that Let visitors dictate messages is on and saved, and use a browser with speech recognition, such as Chrome, Edge or Safari. In an inline iframe, add
allow="microphone"to the iframe tag. - The pop-up or auto-open doesn't appear. Both stop for the rest of the visit once the chat was opened, closed or dismissed, and auto-open also after it has run once. To test again, open your site in a new tab. Auto-open never runs on screens 768 pixels wide or narrower.
Next, install the widget with a script tag or see other platforms.