Chat Widget

The chat widget is the bubble your visitors click on your website. It belongs to a brand, and you design it on a split screen with seven tabs and a live preview: Style, Home screen, Chat, Widget tabs, Languages, Install and General.

Where to Find It

Open it at Brand → (your brand) → Chat widget. Its web address is /dashboard/widgets/<widgetId>. The tabs are a menu down the left of the settings (a drop-down on narrower screens), and the brand's own tabs stay in the title bar above.

The screen is split: the settings on the left, a live preview of the widget on the right. On narrower screens Edit and Preview buttons at the bottom swap between the two. Once you change something, the title bar shows Unsaved changes, Discard and Save changes; with nothing to save it shows a quiet Saved. Save changes writes every tab's settings in one go — with one exception: the Inbox access list on the Chat tab saves each switch the moment you flip it and is not part of Save changes.

Editing it needs the Brands & chat widgets permission — the same right that covers Brand settings and creating brands.

Where a Chat Widget Comes From

There is no widget list page and no "New widget" dialog. A chat widget comes into existence together with a brand: New brand — in the brand menu that opens from the brand's name in the title bar, or from the Switch brand button — asks only for a name, with no tick boxes, and creates the brand with a Chat widget, a Knowledge base, Documentation and an AI agent. Each one is created only if your plan includes that feature at all. When your allowance for one is already used up, the dialog names it, for example "Your plan has no room for another Chat widget, so this brand starts without one." The dialog ends with the line "Next, we read your website and set up the widget and AI agent for this brand."

A brand can live without a widget. Deleting the widget leaves its brand alive, so "a brand with no chat bubble" is a normal, permanent state. In that case the brand's Chat widget row opens a short page that explains the situation and offers an Add a chat widget button — which is also grayed out if your plan has no room for another one. A brand never has more than one chat widget.

The Seven Tabs

TabWhat you set there
StyleLogo and widget icon, widget color, brand colors, buttons & messages, cards, corners, the Home screen background layers, the launcher, Starting points, Redesign with AI
Home screenGreeting, welcome message, team avatars, hide branding, and the home-screen cards
ChatStart screen, email capture, conversation ratings, inbox access
Widget tabsHelp, News, Roadmap
LanguagesWhere your own texts stand in each language, and the two language switches
InstallThe embed code for your platform, identity verification, session replays
GeneralThe widget's name, and deleting it

Style

The tab is headed Style — "Make the widget look like your brand. Every change shows in the preview right away." Three buttons sit in its header: a readability check, Starting points and Redesign with AI. Below them are four groups you open and close — Brand & colors, Shape & finish, Home background and Launcher. The first is open, and a closed group shows its current values. The full reference is Appearance & Theming.

Brand & colors

"Your logo, icon and colors." Every color in the widget is derived from these and checked for readability:

  • Logo ("Shown at the top of the Home screen.") and Widget icon ("Shown to your team next to this widget in the inbox and the mobile app. Visitors always see Yaplet.") — both chosen through a shared image picker titled "Your images" — "Everything this organization has uploaded. Pick one to reuse it, or add a new one." Anything you upload joins that library automatically and can be reused anywhere else in the dashboard that asks for an image. With no logo the Home screen shows none. Whatever picture you choose as the widget icon, visitors never see it: the AI's face in the chat is always the Yaplet blob, drawn in your launcher color.
  • Widget color — the widget's own page color: six swatches from Paper to Ink, or any color of your own. It decides whether the widget reads light or dark.
  • Brand colors — one to three, most important first (Main, 2nd, 3rd; Add a color adds the next). The first paints buttons, links and the active tab; the others join the gradients and the Home screen background.
  • Buttons & messages — One color or Gradient: how your brand colors are painted on buttons, on your visitors' own messages and, until you give it colors of its own, on the launcher bubble.

Shape & finish

"How the cards look and how round the corners are."

  • Cards — Neutral, Subtle, Medium or Strong: how much brand color is washed into every card, chip and panel.
  • Corners — Square, Rounded, Soft or Pill: one scale for the panel and everything in it. The launcher bubble has its own shape.

Home background

What sits behind the greeting on the Home screen, painted as four layers over each other — Color, Photo, Glow and Lines — plus Reaches, how far down they go (Top only or Whole screen). Every layer can be switched off and every combination works. Opening this group takes the preview to the Home screen. See Home Screen Background.

Launcher

The floating button on your customer's site that opens the widget: its Position (Bottom Right or Bottom Left), its Icon (Mascot, Message Bubble or AI Icon), its Bubble color — following your brand colors, or set by hand with one to three colors — its Bubble shape (Circle, Soft, Rounded or Square, separate from the widget's Corners setting), its Icon color, picked automatically for contrast or pinned by you, with the measured contrast printed underneath, and an optional Highlight ring that travels around the bubble's edge. The Mascot is the Yaplet blob itself as the button, with no bubble around it, so it hides the Bubble shape and Highlight ring rows. See Launcher Button.

Readability and Starting points

A small icon in the header shows whether every text stays readable; a warning bar appears only when some text falls short, with a Details list of the measured pairs. Starting points opens twelve finished looks — colors, Home background, card finish, corners and bubble — with Undo; every part stays editable afterwards.

Redesign with AI

The button opens the same AI setup dialog used elsewhere in the dashboard. Give it a website address, choose Keep what's there or Replace it if the widget already has a design, and look at the result in the live preview — nothing is written until you press Save changes. With Replace it it sets the colors, Home background, corners, card style and launcher look; it never changes which icon the launcher shows. Either way it writes quick buttons about your business; they are translated into the other languages after you save. It writes no greeting or welcome line. The full description is on Appearance & Theming.

Home screen

Home Screen Settings

The Header Greeting (the large line, e.g. "Hi there 👋"), the Welcome Message beneath it, Show Team (whether agent avatars appear) and Hide Branding (removes the "Powered by Yaplet" badge from the chat widget and your help center; the switch appears only in workspaces that have Your own branding).

You type the greeting and the welcome message in your own language; the other languages are behind the globe button next to each field. A visitor reads their own language when you have written it, otherwise your own text, and an empty field shows Yaplet's built-in wording in the visitor's language. See Widget Languages.

Home Cards

The interactive cards on the home screen. Two of them are fixed and always come first, in this order: the AI Assistant — the "Ask me anything..." box, with the quick action buttons you define under it — and the Active Conversation. Neither can be moved or removed. Below them you arrange the six types you own: Help Articles, Documentation, Form, News & Updates, External Link and Start a Conversation. Card types belonging to features your plan does not include are not hidden: they stay in the picker, grayed out and unclickable, with "Not included in your plan" printed underneath. Help Articles and Documentation are grayed out the same way until the brand publishes one on its public address — the note then reads "Requires Knowledge Base" or "Requires Documentation" instead.

Chat

The chat tab. Starting a chat holds the Start screen — whether the widget opens on the Home screen or straight in the chat — and Ask for an email, whether visitors give their email address before the chat starts. After a chat holds Ask for a rating, whether the widget asks visitors to rate the conversation. There is no reply-time setting: the widget never promises visitors how soon your team replies.

The tab names and the rating question are Yaplet's own: the widget says both in the visitor's own language.

Inbox access

A list of everyone in your organization with a switch each. This grants access to the widget's brand, not to the single widget — switch someone off and they lose the whole brand, including its other screens. It writes exactly the same grant as the Brand access section on the team page (avatar menu → Manage team). Owners and admins always have access and show an "Always has access" badge with the switch disabled. Each switch saves the moment you flip it, so this section has no Save button of its own and the page's Save changes button has nothing to do with it.

Widget tabs

Help

This section does not pick a knowledge base. It reports which one is in use:

A blue notice names the knowledge base currently published on the brand's public address — on screen it is worded "This is the knowledge base on this brand's address (acme.yaplet.help), and it is what this tab shows." — with a Manage on the brand's Knowledge page button. If nothing is published there you get an amber warning instead: "No knowledge base on this brand's address." What you can set here is presentation only: Show on Navbar, whether the tab appears at all, and Link to Documentation, a link to the brand's documentation at the top of the Help tab, above the categories.

News Feed

Show on Navbar — whether the news tab is visible; off for new widgets. Its name is Yaplet's, said in the visitor's language.

Roadmap

Show on Navbar — whether the roadmap tab is visible, off for new widgets — and the Roadmap Board, which feature-request board it shows. This board picker is the one content picker on the widget, because boards belong to the organization rather than to a brand; Disconnect takes the board off again. Changing it reloads the page after you save.

Languages

The two language switches sit here, under How visitors get a language: Follow the visitor's browser language — on for new widgets — opens the widget in the visitor's browser language when it is one of the 38 the widget speaks, and Language selector — visible by default — shows the globe button on the home screen so visitors can change language themselves. Under Your texts in every language the tab also shows, language by language, how many of your own texts are translated, with a Translate all languages button to fill in the missing ones. See Widget Languages.

Install

The Install tab, headed Put Yaplet on your website, is where the embed code lives. It asks Where does your website run? The button for the platform Yaplet recognized on your website when the brand was set up (WordPress, Shopify, Wix, Squarespace, Webflow, UNAS or Shoprenter) is already selected, with the line We think your site runs on and its name. Anything else starts on Other website, and you can pick another platform at any time; one you click yourself is remembered in this browser. You get the code in the form that platform needs, the steps for pasting it, and a link to the full step-by-step guide. For some platforms a switch lets you include or leave out the <script> lines, so you paste exactly the form that platform takes.

For Other website, paste the code into your website just above the closing </body> tag, on every page where the widget should appear. Then reload your website and the chat button appears.

A light above the steps shows a gray Waiting for your website… and turns green, Live on and your site's address, as soon as the chat first loads on your website.

Under the code, My developer does this opens three buttons: Copy link (a page for your developer with the steps, the code and the same light, no Yaplet login needed), Copy message (a ready-made message for any chat app or email) and Email (the same message in your own mail app). Your chat link, at the bottom of the tab, is a page where visitors chat with you with nothing installed, for when you can't reach your site's code right now: share it on your contact page, Instagram bio or Google profile, and press Copy. Every workspace has it, free ones too.

Identity verification sits below the script, on the same tab, because the person pasting the snippet is the person who has to sign user ids on the server. If your site has signed-in users and you plan to call Yaplet.identify(), you need it: calls to identify() are rejected unless they carry a valid userHash, and without one your signed-in users stay anonymous visitors. The panel reveals this widget's own identity secret on demand — every chat widget has its own, and it is not loaded into the page until you ask for it — shows the two code samples (sign the user id on your backend, pass the hash as the third argument to identify()), and lets you rotate the secret. Rotating breaks every identify() call to that widget until you deploy the new secret, so do it deliberately.

SDK Features

Session Replays — whether the widget records visitor sessions, for bug reports and for the Session Replays screen — plus Recording Rules, which limit recording to certain pages or certain visitors. Shown only if your plan includes session replays.

General

Widget name — the internal label you see in the dashboard, nothing the visitor ever reads.

Danger zone

The bottom of the General tab, under Danger zone, holds Delete this chat widget and its Delete widget… button. The dialog it opens ("Delete the chat widget for “…”?") is explicit about both halves:

What dies: the widget and every conversation held in it — the dialog counts them for you ("The widget · 128 conversations"). That means the chats, their messages and events, the visitors, the session replays, and any banner campaigns configured for this widget. There is no undo.What survives: the brand and everything it owns. Your public address and its knowledge base keep working, as do the documentation, the knowledge, the products and the AI agent — the customer's pages simply lose the chat bubble, and you can add a widget back later.Deleting only the widget needs no typing: read the count and press Delete widget. Below the counts sits an unticked box, "Also delete the whole brand “…”", which expands into the full brand-deletion confirmation: real counts of everything that would go, a warning about any phone numbers that would be left unassigned and still billing, and a field where you must type the brand's name. That box is a shortcut, not the only way. Brand settings → Danger zone deletes a brand directly at any time and takes the widget with it. Use this dialog when you want the narrower thing — the chat bubble off a site, with the brand and everything it owns left running.

Live Preview

Color, text and layout changes appear in the preview the moment you make them — you do not have to save to look. Clicking an option in the Style tab's Home background group also takes the preview to the Home screen. Saving is what makes the changes real for visitors. The one setting that behaves differently is the roadmap board: changing it reloads the page after the save so the preview can pick up the new board.

What Belongs to the Brand

Several things belong to the brand rather than to the widget. Changing any of them destroys nothing and costs nothing, and none of them asks you to confirm deleting or regenerating AI training data.

WhatWhere to find it
Public web address (the widget URL)Brand → Brand settings → Public address
Interface languageBrand → Brand settings → General — and each visitor can pick their own, see Widget Languages
Which AI answersBrand → AI agent — the brand has one, and the widget uses it
Which knowledge base the Help tab showsBrand → Knowledge
Which documentation is linkedBrand → Knowledge
Which forms a card can openTickets → (the board) → Forms — forms live on the board they feed

Automate with AI

You can also change a widget through Yaplet, the assistant inside your dashboard, or any MCP-compatible client — describe the change you want and the AI applies it. See the Widget Tools reference for what it can do. The AI agent belongs to the brand, not to the widget: the AI can make one of your AI agents the one that answers for the widget's brand, or release it (the agent itself is kept). Changing which knowledge base a brand publishes is likewise a bookkeeping change that deletes nothing.

© 2026 Yaplet. All rights reserved.