Brands

A brand is one public identity in Yaplet — its web address, its knowledge base, its chat widget, its AI and its phone agents. What a brand owns, when you need a second one, and what a deletion takes with it.

What a brand is

A brand is one identity your customers deal with: one name, one public web address, one body of knowledge, and the channels that answer from it. Almost everything else in Yaplet belongs to a brand — the chat bubble on your website, the AI that answers in it, the phone agents that take your calls, the articles your customers read.

Your account already has one. It is created together with your organization, named after your company, and given a web address derived from that name. There is nothing to set up before you can start.

In the dashboard it is the brand card at the top of the left menu, showing the brand's logo and name with its own pages listed under it: Playground, Chat widget, AI agent, Knowledge, Products, Content sources, Workflows and Brand settings. The same pages are the tabs along the top of every brand page.

What a brand owns

PartWhat belongs to the brand
IdentityIts name, its working language, its <name>.yaplet.help public web address, your company name, website and description, and its icon and logo
KnowledgeIts knowledge bases and documentation sets with all their articles and pages, uploaded files, website pages that were read, Q&A entries, product sources and the products in them, and API tools
Channels and automationAt most one chat widget, at most one AI agent, its voice (phone) agents, and its chat workflows
A brand with no chat widget, and a brand with no AI agent, are both ordinary and permanent states — not broken setups. There is an explicit way back for each: the brand's Chat widget page offers Add a chat widget when there is none, and its AI agent page offers Add an AI agent.

One body of knowledge, several surfaces

Everything listed on the brand's Knowledge page is a single pool. When a question arrives, that whole pool is searched in one pass, and the same pool answers on every surface:

  • the chat AI in your website widget
  • your phone agents
  • the suggested replies your agents get in the Inbox
  • AI social posts

Nothing is attached to anything. You never point a knowledge base at a chatbot or a documentation set at a widget — the brand owns the content, and everything the brand runs reads from it.

Publishing an article teaches it to the AI. You do not need a chatbot, and you do not need a chat widget, for your content to be searchable by the AI. Teaching the AI is paid like other AI work, so it needs a plan, bought credit or the free 14 days to pay for it. If nobody can pay, the article still publishes and is learned within about an hour after you add credit or choose a plan; nothing already learned is removed.

The public web address belongs to the brand, not the widget

Every brand can have one public address of the form <name>.yaplet.help, set in Brand settings → Public address. It serves one knowledge base and one documentation set at a time. Putting one up automatically takes the previous one down — and the displaced one is not deleted and not removed from the AI's knowledge, it simply stops being served. Changing the address itself breaks every link people already have to the old one, so Yaplet asks you to confirm first.

Because the address belongs to the brand, deleting the chat widget does not touch it. The public pages carry on working.

This is not "publishing". On the brand's Knowledge page, a knowledge base or documentation set shows either an On public site badge or an AI only badge, and the actions in its ⋯ menu read Show at acme.yaplet.help and Take down from the public site. Publishing is a separate thing: every individual article and page has its own Published switch, which decides whether that article is shown to visitors and read by the AI at all. Wherever this documentation says on the public site, show at or take down, it means the public site — never publishing.

Sharing content between brands

A knowledge base or documentation set can be handed to another brand in two ways, from the ⋯ menu of its row on the brand's Knowledge page: Copy to another brand… and Move to another brand…. Both stay grayed out until you have a second brand.

  • Copy duplicates it. Categories, articles and their order come across, but everything arrives unpublished — nothing shows on the other brand's public site, Yaplet does not learn from it there and nothing is billed until somebody publishes it. The copy waits in the other brand as a draft, and the two are independent from the moment it exists.
  • Move hands the original over, with everything the AI has already learned from it, at no cost. It arrives unpublished, as AI only, so you choose when it goes live on the destination's public address. If it was the one on this brand's address, this brand's address has nothing behind it until you put something else there.

When you need a second brand

One brand is right for one company with one public identity. Add a second when you genuinely have a second identity — a separate product with its own name, its own public pages and its own AI, whose knowledge should not be mixed with the first one's.

Brands count against the same plan allowance as chat widgets: whatever number of widgets your plan allows is also the number of brands you can have. What lives inside a brand is not a plan number: every brand may hold up to five knowledge bases and five documentation sets (one of each on the free plan), whatever plan you are on.

With two or more brands the dashboard changes slightly: a small Switch brand button appears on the brand card (it lists your brands, with New brand under them), and Overview gains a Brands table comparing them.

Deleting a brand, and deleting its chat widget

These are not the same act, and the difference between them is large.

Deleting the chat widget is safe for the brand

It removes the widget and everything held inside it — the conversations and their messages, the visitors behind them, the session replays, and the banner campaigns that ran in the widget. The brand survives untouched — its web address, its public knowledge base, all of its knowledge, its AI agent, its voice agents and its settings. Your customers' pages simply lose the chat bubble. You do it on the chat widget's General tab, under Danger zone, with Delete widget….

Deleting the brand is the dangerous one

It permanently removes everything the brand owns:

  • every knowledge base and documentation set, with all their articles and pages
  • uploaded files, website pages that were read, and Q&A entries
  • product sources and the products in them
  • API tools
  • the AI agent
  • the voice agents
  • the chat workflows

It also removes the brand from AI Social Posting and takes its autopilot with it. Its connected Facebook and Instagram pages and its past posts are released rather than deleted. There is no undo and no recovery.

Deleting a brand also deletes its chat widget. Brand settings → Danger zone deletes the brand whenever you ask it to, and the widget goes with it, taking every conversation held in it. The confirmation lists them first (the chat widget, then its conversations, for example "128 conversations") and warns you that the bubble disappears from every page it is installed on. You must type the brand's name before the Delete brand button arms. Deleting only the widget is a separate, smaller action: Delete widget… on the widget's General tab opens a window that lists what is deleted (the widget and its conversation count) and what is kept, and one click on Delete widget does it, with the brand surviving untouched. The same window has an unticked Also delete the whole brand box; tick it and the window becomes a full brand deletion, where you also type the brand's name and the button reads Delete widget and brand.
Phone numbers are not released by a deletion. A brand's numbers become unassigned and stay on your organization — and they keep billing — until someone releases them at Settings → Connections → Phone numbers. Only the organization owner can release a number; an administrator is refused.

Who can see which brand

Access is granted per brand, on the team page (avatar menu → Manage team). An agent holding a grant for one brand sees only that brand in the menu, and in the Inbox sees only the conversations from that brand's chat widget. Owners and administrators always have every brand.

For how brands sit inside your organization, roles and permissions, see Core Concepts.

© 2026 Yaplet. All rights reserved.