Yaplet Assistant
Yaplet is the AI assistant built into your dashboard. Describe what you want in plain words and Yaplet reads your data, creates resources and changes settings for you — and always asks for your OK before it changes, deletes or sends anything.
Overview
Yaplet is an AI-powered assistant that lives in your dashboard. Instead of navigating through menus and forms, you can simply describe what you want in plain English and Yaplet will handle it. It has access to the same tools as the MCP server, meaning it can do most of what you can do through the dashboard UI.
How It Works
Open Yaplet
There are three ways in, for members who hold the Yaplet assistant permission (see Permissions below):
- The Yaplet blob. The orange mascot in the bottom-right corner of the page is Yaplet's button. Hover it and it reads Open Yaplet (or Open Yaplet (3 new) while notes or unread chats wait for you); click it and the side panel slides open beside your current page. Hover it and press the small ⌄ (Minimize Yaplet) to tuck it away so only its head and eyes show, and click it again (Show Yaplet) to bring it back — open or minimized is remembered in this browser. The blob also steps aside by itself on busy screens such as the email builder, and while Yaplet's own support chat is open.
- The Ask Yaplet card at the top of the sidebar. It says or search any page and shows the shortcut (Ctrl K, or ⌘K on a Mac). Click it to open the Search window.
- Ctrl K (⌘K on a Mac) from anywhere in the dashboard opens the same Search window. Type a question and choose Ask Yaplet: "…", or type the name of a page and pick it under Go to. Before you type, the window offers buttons for what Yaplet can do on the page you are on, plus your five most recent pages.
Members without the Yaplet assistant permission get a plain Search pages field instead (same Ctrl/⌘ K shortcut, pages only) and see no blob.
The side panel header has the chat's title, Yaplet chats (with an orange count of chats holding a Yaplet message you have not seen yet), a ⋯ menu for the current chat, Agent mode: make Yaplet big and Close. Yaplet chats slides your chat list in over the conversation, with New chat at the top; press it again, press Esc or pick a chat to put the list away. In a narrow window the list opens from the left instead. Agent mode expands the same chat into the full-page agent view, described in the Yaplet Agent View and Chats article; its Side panel button brings you back. To open Yaplet full-page when you sign in, set First screen to Yaplet under your account menu → Settings → Yaplet; the default is Dashboard.
If you reload the page while the side panel is open, it comes back open on the same chat. This lasts as long as the browser tab: a new tab, a new window or a later visit starts with Yaplet closed, and opening it shows its home.
Some buttons around the dashboard send Yaplet a request for you — see Buttons That Ask Yaplet for You below.
Type Your Request
Write what you want in the text input (it says Ask Yaplet to make a change...). You can ask questions, give instructions, or describe complex multi-step workflows. Yaplet understands context and will use multiple tools in sequence when needed.
If an answer fails, the error shows above the message box and the send button turns into a retry button that asks the same question again. Type something new instead, and it is sent in the same chat.
Review and Confirm
- Reads (listing records, viewing details, searching, reports, looking up which action to use) happen automatically.
- Changes, deletes and sends wait for you. Yaplet stops at a Confirm action card and does nothing until you press Confirm or Cancel.
See Results
While Yaplet works, it shows each step in the conversation in plain words — Looking through your chats…, Finding the right action…, Getting the change ready: … — and the line switches to the past tense when the step is done (Looked through your chats, Done: …). A step that failed says Couldn't …, and a change waiting for you says Waiting for your OK: …. Open a step to see what Yaplet asked for and the result; raw data is never shown. When a change's Confirm card has loaded, its line uses the card's action name, in your dashboard's language; otherwise a line shows the action's internal name, such as tickets.update, which stays in English. For resources it creates, Yaplet often provides direct links to the dashboard page where you can review and fine-tune.
Yaplet can take several steps for one answer — looking up the right action, reading what is there, then acting — so a multi-step request usually finishes in a single reply.
The Confirm Card
Every change, delete or send shows a card before it runs:
- The action's name in plain words, such as Update ticket or Write article with AI.
- Applies to: the name of the record it acts on, when there is one.
- The values being sent, as short readable rows — the new title, the column, the assignee, and so on.
- Uses AI credits, when the action writes text with AI.
- Claims: a line at the top of the values when a change to a brand's claims or product instructions may switch its claims on or off — for example This change may switch claims ON for the brand "…" (they are off now), followed by what that changes in how the AI talks about the brand's products. Yaplet can make such a change only after it has explained it and you said yes in the chat — without that, the change is refused and nothing happens.
The card is written in the language of your dashboard. You never have to type anything to confirm — you only press Confirm (for a delete, Yaplet also gives the record's exact name, and Yaplet checks that it matches the record before anything is deleted).
Deletes and sends get a red card with a red Confirm button. It names the record and says This cannot be undone. Read it carefully: a deleted record is gone for good, and a reply or email reaches the visitor or reporter the moment you confirm.
When Yaplet has prepared two or more changes at once, a Confirm all (N) button appears above the cards so you don't have to click each one; when a delete or send is waiting too, a hint beside it reminds you that Deletes and sends are confirmed one by one. You can still confirm or cancel any card on its own. Deletes and sends are never part of Confirm all — each one is confirmed by itself. Confirm and Confirm all become clickable once the cards have loaded their details (Loading details…), so you always see what you are confirming; if the details can't be loaded, the card says so and lists what the action gets.
Apply to Canvas (Workflow Editor)
While a workflow is open in the editor, Yaplet never saves that workflow itself. It writes the change and checks it, and once the check passes, an Apply to canvas button appears under the check:
- Apply to canvas puts Yaplet's change — the steps, the trigger and the name — on the canvas, without saving. A toast says Applied Yaplet's change — not saved yet.
- Undo on that toast brings back the canvas, the trigger and the name as they were.
- Look the change over, then press Save yourself. Until you save, nothing changes for your visitors.
The button only appears in the editor of that workflow. On other pages, such as the Workflows list, there is none — there Yaplet creates or changes workflows through the Confirm card.
The Empty Chat
When you open Yaplet with no conversation yet, the side panel shows Yaplet's home, the same one as in the full-page agent view, only smaller: a greeting, one line about your day, today's numbers, what needs you and some ideas. The Yaplet Agent View and Chats article describes every part. Two parts matter most in the side panel:
- On (the page you are on), I can — up to four buttons built from what Yaplet can do on that page, limited to what your permissions allow. They change as you move around the dashboard. Requests that the page offers itself, such as Create with AI on a brand's Workflows page, come first (see Buttons That Ask Yaplet for You, below).
- Ideas for this morning (or afternoon, or evening) — four buttons at a time. The list ends with two starters that work on every page:
- "Explore Yaplet: what can it do for me?" — Yaplet walks through each product area, what your plan and permissions include, and what to set up next.
- "Fix a problem: find what is missing or failing" — Yaplet checks your account for anything missing or failing and proposes the fix.
You type in the box under the home. Two cases show a simpler start screen instead of the home: when Yaplet has opening words for you (a message it wrote first, with a Back button), and when agent mode opens over a dialog. It then shows its words, or What should we do on …?, any waiting notes under Waiting for you, the page buttons under On (the page), I can, and the two starters under Anywhere in Yaplet.
Your Chats
Yaplet keeps your conversations, so you can come back to any of them. The same chat menu works in the side panel, in agent mode and in the full-page agent view.
| To do this | Do this |
|---|---|
| Start a new chat | Press New chat at the top of the chat list (in the side panel, open the list with Yaplet chats first) |
| Switch to another chat | Open the list with Yaplet chats: your Pinned chats first, then the others under Today, Yesterday and Earlier. With none yet it says No chats yet |
| Rename a chat | Click the title, type the new one and press Enter (or click away) to save; Esc cancels. Up to 200 characters; an empty title keeps the old one |
| Pin or unpin | Open the ⋯ menu and choose Pin chat or Unpin chat |
| Delete a chat | Open the ⋯ menu and choose Delete chat…. Yaplet asks Delete this chat? — The chat and its messages are deleted for good. — and you press Delete (or Cancel) |
A new chat is named for you after your first message, in three to five words. If a chat cannot be renamed, pinned or deleted, a short toast says so. Chats that Yaplet itself starts and keeps by subject (see the Yaplet Speaks First article) are always pinned and cannot be unpinned; you can still rename or delete them.
After an Answer
- Next-step buttons. Under Yaplet's last answer you may see one to three outlined buttons. An ask button sends a follow-up request in your name; an open button (with an arrow) takes you to a dashboard page. Yaplet hides a button that needs something you are not allowed to do. The buttons disappear once you use one or the conversation moves on, and ask buttons are disabled while Yaplet is writing.
- Thumbs up and down. Every finished answer has two small buttons (Helpful and Not helpful). A thumbs down opens What was wrong? (optional) with Send and Skip; after you send a note Yaplet says Thanks, noted. It helps us make Yaplet better. Your last click wins. The buttons are not shown while Yaplet is still writing or while a Confirm card is waiting. Yaplet's team reads the thumbs counts and thumbs-down notes together with the name of your workspace — never the chat itself.
Buttons That Ask Yaplet for You
Some buttons around the dashboard send Yaplet a request in your name, so you do not have to write it yourself. Nothing is pre-typed into the chat: it shows only the button's words.
- Requests a page offers for itself are listed under On (the page), I can on Yaplet's home, and in the search window (Ctrl K) under On (the page), Yaplet can. Pages have no Yaplet button of their own in the title bar. Examples: Create with AI (Brand → (your brand) → Workflows), Edit with AI (while a chat workflow is open in the editor), Draft an article (Knowledge base articles), Generate a docs page (Documentation) and Write a news release (Marketing → Engagement → News & Releases). A request that needs your input first opens a small box next to the button that asks what it should cover. Enter sends it at once; Esc closes the box.
- Explain AI answer (under an AI reply in the Inbox) and Ask AI for help (on the email domain setup under Settings → Connections → Emailing) send their request immediately.
- Ask Yaplet about this appears when you point at the title-and-description card of an open ticket. Yaplet then gets only the ticket's type and id and reads it under your own permissions.
These buttons are hidden for members without the Yaplet assistant permission.
What You Can Do
Below are example prompts organized by category. Many of these involve multiple tools working together behind the scenes — Yaplet handles the orchestration automatically.
Chat Widget Setup & Customization
- "Change my widget's accent color to #FF5500 and set the background to a gradient decoration."
- "Show me all my widgets and their settings."
- "Hide the news and roadmap tabs in my default widget."
- "Set my widget to ask visitors for their email before starting a chat."
- "Give me the install code for my main widget."
- "Make the launcher button a two-color gradient from #6C63FF to #FF6B6B."
- "Turn on conversation ratings on my widget."
Website AI Agent Setup
A brand has at most one AI agent for its website visitors, and it answers on that brand's chat widget automatically. It is also called Yaplet, but it is a different thing from the assistant you are chatting with on this page. There is nothing to link and no list of chatbots to build.
- "Add a document to my brand's knowledge explaining our refund policy: customers can request a full refund within 30 days of purchase."
- "Set the AI to hand off to a human agent after 5 messages if it can't find an answer."
- "Change what the AI does when it doesn't know: decline politely instead of offering an agent."
- "Show me all the documents my AI agent can read."
- "Create an API tool my AI agent can call to look up an order's status."
- "Turn my AI agent on."
Diagnosing AI Responses
- "Show me the messages in conversation X — I want to check what the AI said."
- "Why did the chatbot give a wrong answer in this conversation? Diagnose the AI response for message Y."
- "The chatbot couldn't answer a question about pricing. Add a document with our pricing info to fix it."
Chat Workflows
- "Build a workflow for my brand that asks visitors for their order number and email, then hands the chat to my team."
- "Change the open workflow so the welcome message also offers a 'Talk to sales' button."
- "When a visitor asks where their order is, look it up with our order API and tell them the status."
- "Duplicate my returns workflow into my second brand."
- "Which of my workflows failed in the last 24 hours, and why?"
- "Switch off the holiday sale workflow."
Help (Knowledge Bases & Documentation)
- "Create a knowledge base called Support."
- "Write an article about getting started with our platform and publish it."
- "Generate an article titled 'Billing FAQ' covering common billing questions for a SaaS product."
- "List all articles in my knowledge base and tell me which ones are published."
- "Move the Getting Started article to the Onboarding category."
- "Unpublish the old pricing article."
- "Create a documentation page about our API reference in Markdown."
- "List all documentation pages and their categories."
Inbox & Conversations
- "Show me all unassigned conversations."
- "What conversations came in today?"
- "Search for conversations mentioning 'refund'."
- "Show me the messages in the most recent conversation."
- "Assign the latest unassigned chat to me."
- "Send a reply in conversation X saying 'Thanks for reaching out! Let me look into this for you.'"
- "Add a private note to conversation X saying 'Customer is a VIP — handle with care.'"
- "Reply to the customer and also send it as an email."
Tickets
- "Create a bug ticket on the Bugs board titled 'Checkout fails on Safari'."
- "Move ticket 42 to In Progress and assign it to Anna."
- "Set this ticket to high priority and add the 'billing' label."
- "Add an internal note to this ticket: reproduced on iOS 18."
- "Email the reporter of this ticket to say the fix ships next week."
- "Archive the ticket about the Safari checkout bug."
Newsletter Campaigns
- "Create a newsletter campaign called 'March Update' with the subject 'What's New in March'."
- "Generate a promotional email about our spring sale with 50% off all items."
- "Create a campaign based on my Welcome template but change the headline to 'Happy New Year'."
- "Set the campaign recipients to all active subscribers."
- "Target only the 'Premium Users' contact group for this campaign."
- "Show me my recent campaigns and their stats."
- "What's the open rate on my last campaign?"
- "Design a newsletter template for our brand — logo header, address and social links in the footer — and make it my default."
- "Show me how my last campaign looks on a phone."
Email Automations
- "Create a welcome email automation: when someone subscribes, wait 1 day, send a welcome email, wait 3 days, send a tips email."
- "Add a condition to my onboarding automation to check if the contact opened the first email."
- "Write the welcome email content for node 2 in my automation — make it warm and professional."
- "Rename my automation to 'New Customer Onboarding'."
- "Show me the stats for my welcome series."
- "Which of my automations are switched on?"
- "Switch off the old summer promo automation and delete it."
Engagement (Banners, Chat messages, Surveys, Tours, News)
- "Draft a banner announcing our holiday sale that shows on session start."
- "Create a feedback survey that triggers after 30 seconds on the pricing page."
- "Set the banner to only show to visitors from the US, once per visitor."
- "Move my sale banner to the top of the list."
- "Write a news release about our new feature update — generate the content with AI."
- "List all my engagement items."
- "Which of my banners performed best last month?"
- "What did people answer in the feedback survey?"
Shifts
- "Clock me in for chat duty."
- "End my shift."
- "I forgot to clock out yesterday — set my shift's end to 6 PM."
- "Record an 8-hour shift for Anna last Tuesday."
- "How many hours did each agent work last month, and what do we owe them?"
- "Finalize last month's completed shifts for payroll."
Analytics & Reports
- "How are my agents performing this month?"
- "Show me chatbot analytics for the last 30 days."
- "Where are my visitors coming from? Show country breakdown for this week."
- "How many AI credits did we use this month compared to last month?"
- "What's my chatbot's AI handling rate?"
Complex Multi-Step Workflows
These prompts demonstrate Yaplet's ability to chain multiple tools together:
- "Teach my AI agent our FAQ: add a document for each of these five questions, then give me the install code for my widget."
- "I want a complete newsletter setup: create a welcome campaign with AI-generated content, target all active subscribers, and show me the preview link."
- "Review my chatbot's performance: show me the analytics for this month, find any conversations where the AI failed, and diagnose the most recent failure."
- "Create a knowledge base, write 5 articles about common support topics for a SaaS product, and publish them all."
What Yaplet Can See on Your Screen
Yaplet does not watch your screen. It always knows the page you are on (for example, settings/billing), today's date and your dashboard language, and if a workflow is open in the editor it gets the whole canvas, including edits you have not saved yet.
It also knows the item you have open and the brand the page shows. The open item is:
- the conversation open in the inbox,
- the ticket open in its side panel on a board,
- the visitor whose details panel is open on the Visitors page,
- the documentation set, category or page open in the documentation editor,
- the product API source you have selected,
- and, on the help center Articles page, that help center (its brand).
When your question is about what you have open ("this ticket", "summarize this visitor"), Yaplet reads that record directly instead of looking at the page. It reads it with your own permissions, so it sees only what you may see. A record you point at with Ask Yaplet about this takes precedence over the open one, and the full-page agent view keeps the item that was open on the page you came from. On the help center Articles page, a new article goes into that help center without Yaplet asking which brand. Together with your question, only a reference to the item — which one it is — leaves your browser; Yaplet then reads the item itself.
When you say "this", "here" or "the error I see" about something an open item cannot show — an error message, values you have not saved, what you typed — or when no item is open, Yaplet looks at the page: the step shows Looking at your page, then Looked at your page. Yaplet reads the page's main column and any open dialogs:
- the title, headings and the tab that is open,
- the first rows of a table (long cells are shortened),
- form fields with the values currently in them — also values you have not saved,
- messages and alerts on the screen.
It reads only a limited amount of text. That text is saved with the chat and sent to the AI model together with your question.
Who Pays
Yaplet follows the same payment rule as everything else that costs money in Yaplet: before it answers, it asks who pays, in this order:
- The free 14 days — your free AI credits pay first.
- Bought credit — your credit balance, if you have topped it up.
- A paid plan — your plan's usage billing.
If nobody can pay, Yaplet does not run: your message does not go through, and the payment window opens instead with the ways forward — start the free 14 days (only if your workspace never used them, owners only), add credit, or see plans.
Permissions
Yaplet doesn't have a separate permission set for what it can do. It runs under the dashboard feature permissions you already hold — the same ones that decide what you can do by hand in the UI. Each area's actions map to the permission that gates its feature:
- Widget tools require Brands & chat widgets
- AI agent tools (settings, diagnostics) require AI agent
- Content source tools (knowledge documents, API tools, product sources, product claims and instructions) require Content sources
- Workflow tools (building, checking, changing and switching off chat workflows) require Chat workflows
- Knowledge base and documentation tools require your Knowledgebase / Documentation permissions
- Conversation tools require your Inbox permission
- Ticket tools require the Tickets permission, and additionally respect which boards you have been given access to
- Newsletter tools require your Newsletter permissions — one-off campaigns need Campaigns, and automations need Email automations
- Engagement tools require the matching permission per item type — banners, chat messages, surveys, tours and news each have their own. The menu section is called Engagement but in the permission list they sit under Outreach, as Banners, Messages, Surveys, Tours and News
- Analytics tools require your Reports permission
- Shift tools require Time Management; the hours-and-pay report additionally needs its Reports sub-permission. All Shifts is needed to see or change anyone else's shifts — and to finalize a shift for payroll or change a pay rate at all, including on your own shift
The result: Yaplet can never do more than you could do yourself in the dashboard. If your role can't access a feature, Yaplet won't offer its actions either. Organization owners automatically hold every permission their plan enables; other roles get whatever was granted at the org and user level.
You also need the Yaplet assistant permission itself to use Yaplet at all. Owners hold it automatically; any other member needs an owner to tick it for them, and none of the built-in role presets, such as Chat Agent, includes it. A member who is suspended or disabled loses Yaplet at once, including access to their old Yaplet chats, and sees You can't use Yaplet in this workspace: your access is suspended, or you don't have the Yaplet assistant permission. Ask the workspace owner. It works again when they are re-enabled; a member who is removed from the organization loses access to their chats too.
A second permission, Yaplet speaks first, sits under Yaplet assistant and lets Yaplet speak first (the Yaplet Speaks First article explains what it adds). Owners have it automatically, and any other member gets it when the owner ticks it for them.
What Yaplet Won't Do
Some things always stay with a person, even when you ask Yaplet directly. Yaplet can explain them and link you to the right page, but it won't do them:
- Money: your plan, add-ons, the payment card, credit top-ups, phone numbers, the dedicated IP.
- Access: team members, invitations, permissions, members' pay rates, API keys, integrations.
- The account: data export, deleting the account, signing the data-processing agreement.
- Emails to subscribers and public posts: sending, scheduling or resuming a campaign, switching an email automation on, approving an autopilot issue or letting an autopilot send without approval, and publishing social posts.
- Switching a chat workflow on: Yaplet builds workflows switched off and changes only switched-off ones; you switch a workflow on yourself. It also never saves the workflow you have open in the editor — it puts its change on the canvas, and you save it.
It also never deletes in bulk: one named record at a time, and never a whole brand, widget, knowledge base, documentation set or board, or a subscriber. The full list is on the MCP Server page.
Tips
- Be specific. Instead of "improve my AI", say "add a document about our return policy to my brand's knowledge."
- Chain actions. Yaplet can handle multi-step requests in a single prompt.
- Ask for help. If you're not sure how to do something, ask "How do I set up email automations?" and Yaplet will guide you.
- Use it for diagnostics. When your AI chatbot gives a bad answer, ask Yaplet to diagnose it — it will tell you exactly what went wrong and offer to fix it.
- Review before confirming. Always check the Confirm card — the action, the record it applies to and the values — before clicking Confirm. Take extra care with red cards: deletes and sends cannot be undone.