Core Concepts

Understand the fundamental building blocks of Yaplet — organizations, brands, team roles, permissions, the widget, and how conversations flow between visitors and your team.

Organizations

An organization is your workspace in Yaplet — on screen you will see it called your workspace or your team. It contains all your data — brands, conversations, contacts, articles, campaigns, settings, and team members. Everything you do happens within the context of an organization.

  • Each user can belong to multiple organizations and switch between them from the avatar menu (your picture at the bottom of the left-hand menu), under Team
  • Each organization has its own subscription plan, billing, and settings
  • Which organization you are acting as is stored on your account, not in the browser — so switching in one window switches it in every window and tab you have open
Each user can only own one organization, but can join any number of organizations as a member. If you run several brands, keep them all in one organization: a brand is exactly the container for one public identity, and one organization can hold as many as your plan allows.

Brands

A brand is one public identity inside your organization. Every account is created with one, and most companies never need a second — which is why you will see the word everywhere in the menu and rarely have to think about it.

A brand holds:

  • Its name, the language it works in, and its public web address
  • Its company details, icon and logo
  • Its knowledge bases and documentation sets, plus uploaded files, website pages read for you, and Q&A entries
  • Its product feeds and API tools
  • One chat widget and one AI agent — at most one of each, and either may legitimately be missing
  • Its voice agents and its chat workflows

Everything that brand knows is searched as one pool: the chat AI, the phone agents, the inbox's suggested replies and AI Social Posting all read from it. Nothing has to be attached to anything — publishing an article indexes it straight away, with no chatbot and no widget involved. What a brand is and what it owns is covered in Brands.

Opening a brand while you are signed in to a different organization does not show you an empty page. Yaplet names the organization the brand belongs to, names the one you are currently in, and offers a button to switch and reopen it. It asks rather than switching silently, because switching changes every window you have open.

Team Members & Roles

Every person in your organization has a role that determines what they can see and do. Yaplet uses a role-based access system with the following hierarchy:

RoleAccess Level
OwnerFull access to everything, including billing and deleting the account
AdminFull feature access, can manage team members and settings
AgentCan use communication tools (Inbox, Tickets) and view assigned content
Custom rolesConfigurable per-feature permissions set by an Admin or Owner
Menu items and pages are automatically hidden if your role doesn't include the required permission. You'll only see features you have access to.

Permissions

Permissions control access to individual features within the dashboard. Each feature (Inbox, Newsletter, AI agent, etc.) has its own permission that can be granted or revoked per person.

Some permissions have children, and the parent gates them: Inbox is the parent of Inbox AI, Rephrase and Summary, so a member without Inbox never sees those three regardless of how they are ticked. AI agent, Chat workflows and Voice & calls are three independent switches, and turning one off has no effect on the others. Owners manage permissions on the team page: open the avatar menu and choose Manage team.

Brand access

On top of permissions, you can restrict which brands each agent can work in. The section is called Brand access, under each member on the team page, and it lists your brands with a switch each.

  • Granting a brand gives the agent that brand's conversations in the Inbox and that brand in the left-hand menu (its card and its pages) — it is not an inbox-only boundary
  • Owners and admins bypass it entirely: the helper line on the page reads "Owners and admins always have access to every brand."
  • A brand with no chat widget can be restricted the same way
  • Removing someone from the organization deletes their brand access along with their board access, permissions and shift-type assignments — so re-adding them later starts them from nothing
  • Push notifications (web and mobile) respect the same boundary: a restricted agent is not pinged about conversations they could not open

Configure brand access per agent on the team page (avatar menu → Manage team). Ticking an agent in the Inbox access section on the chat widget designer's Chat tab does the same thing — it gives them the widget's whole brand, and unticking takes the brand away.

The Widget

The widget is the customer-facing side of Yaplet — a small chat panel that you embed on your website with a code snippet. When a visitor clicks the launcher button, it opens into a full interface with multiple tabs:

  • Home — a branded landing screen with greeting text, team avatars, and action cards
  • Messages — live chat and AI conversations
  • Help — searchable knowledge base articles
  • News — product announcements and updates
  • Roadmap — feature voting board

You design it on your brand's Chat widget page, on seven tabs: Style, Home screen, Chat, Widget tabs, Languages, Install and General. What it does not decide is which AI answers in it, which knowledge base or documentation it shows, what web address it lives at, or which language it starts in — all of those belong to the brand. The one thing it still picks for itself is which roadmap board to display.

For installation instructions, see the Widget Getting Started guide.

How Conversations Work

A typical conversation in Yaplet follows this flow:

Visitor opens the widget

A visitor on your website clicks the chat launcher. They land on the home screen where they can start a new conversation or browse help articles.

AI responds first

If the brand's AI agent is switched on, it handles the initial conversation — answering from the brand's knowledge: its articles, its documentation, the files and website pages it has read, and its Q&A entries. That is the same body of content the phone agents answer from, the inbox suggests replies from, and AI Social Posting writes from.

Handoff to a human agent

When the AI can't answer, or the visitor asks to speak with a person, the conversation is handed off to your team's Inbox. Agents see the full chat history and can pick up where the AI left off.

Resolution and follow-up

The agent resolves the conversation, sends the visitor an intake form that files a Ticket on one of your boards for longer follow-up, or starts one of the brand's chat workflows for automated next steps (e.g., sending a follow-up email or updating a CRM).

Not every conversation follows all four steps. Some are resolved entirely by the AI, and some go straight to a human agent if the brand's AI agent is switched off.

Contacts & Visitor Tracking

Every visitor who interacts with your widget becomes a contact in Yaplet. Contacts are tracked across sessions and devices (when identified), giving your team context about who they're talking to.

Contact data includes:

  • Name and email (if provided or collected via forms)
  • Conversation history — all past chats and tickets
  • Page views and activity — what pages the visitor has seen
  • Custom attributes — any data passed from your app via the SDK

This data is available in the Inbox sidebar when chatting, and can be used for segmentation in newsletters and engagement campaigns.

© 2026 Yaplet. All rights reserved.