What Yaplet can do

What Yaplet can do today, area by area, with a sentence you could type for each. Also what the "and more" really means, what it can't do yet and what it won't do even if you ask.

How to read this page

Every sentence in italics is something you could type to Yaplet. Names, addresses and numbers are examples. A few things apply to all of them:

  • Your permissions and your plan decide. Yaplet only offers what you could do by hand. If your role has no access to an area, or your plan doesn't include it, Yaplet can't do it for you.
  • Looking things up runs by itself. Changes wait. Anything that creates, changes, deletes or sends stops at a Confirm card until you press Confirm. Working with Yaplet explains the card.
  • You can always ask how something works. Yaplet searches our documentation and help articles, also for features it can't operate.

Inbox and conversations

Find chats, read them, move them along and answer in your name. Needs the Inbox permission.

  • "Show me today's unassigned chats."
  • "Find a conversation about a double charge from last week."
  • "Assign the chats about refunds to Anna."
  • "Mark everything waiting in Unassigned as read."
  • "Add a private note to this chat: VIP customer, handle with care."
  • "Reply to this visitor that the parcel left today, and send it by email too."
  • "Send this visitor our returns form."
  • "Start the order status workflow in this chat."
  • "Email this visitor the transcript."
  • "Forget what the AI remembers about this visitor."
  • "Ban this visitor for 7 days. They keep sending spam."

Replies, forms, workflows started in a chat, transcripts and bans reach the visitor at once, so each gets a red Confirm card. Yaplet can't reply into Facebook or Instagram chats yet: answer those in the inbox. It can ask for a rating only in a chat that is assigned to you, because the rating is about you.

Tickets

Create, move and clean up tickets on the boards you have access to. Needs the Tickets permission.

  • "Create a bug ticket on the Bugs board: 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."
  • "Email the reporter of this ticket that the fix ships next week."
  • "Archive the ticket about the Safari checkout bug."

An email about a ticket goes only to the reporter's own saved address. Yaplet can't make new boards or forms.

Brands and chat widgets

Set up a brand, change how its widget looks and behaves, and get it onto your website. Needs the Brands & chat widgets permission.

  • "Set up this brand from greenshop.example: its details, widget colors and the pages the AI should learn."
  • "Create a new brand for our second shop."
  • "Our team is online Monday to Friday, 9 to 5, Budapest time. Set that as this brand's team hours."
  • "Change my widget's brand color to #FF5500 and round the corners more."
  • "Ask visitors for their email before a chat starts."
  • "Turn on conversation ratings on my widget."
  • "Hide the news and roadmap tabs on my widget."
  • "Change the greeting on the widget's Home screen."
  • "Add a card to the Home screen that links to our returns page."
  • "Set up quick buttons for orders, returns and shipping."
  • "How do I install the widget on Shopify?"

Be careful with "a new widget": a new widget gets a new brand of its own. If you mean the one you already have, say "my widget". The logo, the bot picture and the Home photo are files you upload yourself on the widget's page, and texts in other languages are translated on its Languages tab.

Your website's AI agent and what it knows

The AI agent is the Yaplet that answers your visitors. Yaplet in your dashboard can set it up, teach it and find out why it said something. Needs the AI agent or Content sources permission, depending on the job.

  • "Tell my AI agent to keep answers short and never promise a delivery date."
  • "When the AI has no answer, offer a person instead of declining."
  • "Stop answering on Instagram. Send those messages straight to the team."
  • "Turn my AI agent on."
  • "Add a document to my brand's knowledge: customers can get a full refund within 30 days."
  • "Show me what my AI agent can read."
  • "Which sections of greenshop.example has the AI learned? Switch the blog off."
  • "Learn new pages of my website automatically."
  • "Why did the AI agent answer that?"
  • "Create an API tool so my AI agent can look up an order's status."

Switching the AI agent on takes effect the moment you confirm. An API tool calls your own system, and Yaplet tells you where to read the secret key your developer needs.

Products

Connect a catalog and set what the AI may say about your products. Needs the Content sources permission.

  • "Add our Google Shopping feed as a product source."
  • "Refresh my products now."
  • "Add an instruction for this brand: always mention free shipping over $50."
  • "Add these 40 claims about our vitamins from the list below."
  • "Show me the claims that are still drafts."

Yaplet switches a claim or an instruction on only when you have read its exact wording and said yes. If a change would switch a brand's claims on or off as a whole, it explains what that changes first.

Chat workflows

Build the step-by-step flows your chat runs: buttons, questions, API calls and hand-offs. Needs the Chat workflows permission.

  • "Visitors keep asking where their order is. What should I do?"
  • "Build a workflow for my brand that asks for the order number and email, then hands the chat to my team."
  • "Change the workflow I have open so the welcome message also offers a Talk to sales button."
  • "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."

Yaplet builds every workflow switched off and changes only workflows that are off. You switch one on yourself. When a step needs an address your developer hasn't built yet, Yaplet leaves it as a draft and tells you exactly what they have to build. More in Workflows.

Phone agents

Set up the agents that answer your phone calls and look at how the calls went. Needs the Voice & calls permission. A member limited to some brands reaches only those brands' phone agents.

  • "Show my phone agents and which of them have a phone number."
  • "Create a phone agent called Front desk for my brand. It answers questions about delivery and opening hours."
  • "Change the greeting of my phone agent so it is shorter."
  • "Show yesterday's phone calls and read me the transcript of the longest one."
  • "Pause my phone agent until the new price list is ready."
  • "Delete the phone agent called Old front desk."

Yaplet reads agents, calls (real and test calls) and transcripts by itself. Creating, changing, pausing and deleting wait for your Confirm. A new agent answers nobody until a person attaches a phone number, and its call recording starts switched off. A paused agent that still has a phone number plays callers an error message and ends the call, and only a person can resume it. Deleting is for good: Yaplet needs the agent's exact name first, and the phone numbers stay and are still billed, with nothing answering them.

Creating an agent, or giving it a new greeting, voice or language, generates speech, which uses credits. It doesn't run when nobody can pay. Changing the name or the instructions costs nothing. More in Voice Agents.

Help center and documentation

Write and organize what your customers read. Needs the Knowledgebase or Documentation permission.

  • "Create a help center called Support."
  • "Write a help article about how returns work and publish it."
  • "Move the Getting Started article to the Onboarding category."
  • "Unpublish the old pricing article. First tell me which articles link to it."
  • "Create a documentation set for our API."
  • "Write a docs page about authentication."

New articles and pages start unpublished. Yaplet can publish them after you confirm, and a published article goes straight to your visitors and into the AI's knowledge. It can't delete articles or pages.

Newsletter

Prepare everything that goes out by email, up to the moment of sending. Needs the Newsletter permissions, and questions about your sending domain need the matching Settings permissions.

Campaigns and automations

  • "Draft a campaign about our spring sale, using our default template."
  • "Set the recipients of this draft to the Premium group."
  • "How did my last campaign do?"
  • "Check how my last campaign looks on a phone and tell me what's wrong."
  • "Create an email automation: when someone subscribes, wait 1 day, send a welcome email, wait 3 days, send tips."
  • "Write the welcome email of this automation."
  • "Switch off the old summer promo automation and delete it."

Autopilot

  • "Set up a newsletter autopilot for this brand."
  • "Write a sample issue of my autopilot."
  • "Add a topic idea: how we choose our suppliers."
  • "Cancel the next issue of my autopilot."

Templates and subscribers

  • "Show premade email templates."
  • "Create a template from the webinar design and make it my default."
  • "Add these 20 addresses to the VIP group."
  • "Unsubscribe these three addresses."
  • "Create a segment of subscribers who haven't opened an email since June 1."

Sending domain

  • "Check my sending domain. Which DNS records are still missing?"
  • "Is Gmail marking our emails as spam?"

Sending stays with you, every time: see What Yaplet won't do, below. An autopilot Yaplet sets up has Require my approval on, and every issue waits for a person. Its sample issue is written in the background and takes a few minutes.

Engagement

Prepare banners, chat messages, surveys, product tours and news posts, and read how they did. Each type has its own permission.

  • "Draft a banner for our holiday sale that shows once per visitor on the pricing page."
  • "Create a feedback survey that appears after 30 seconds on the pricing page."
  • "Create a chat message for visitors from Germany."
  • "Write a news post about our new mobile app."
  • "How are my banners doing?"
  • "What did people answer in the feedback survey?"

Everything is saved unpublished, and Yaplet gives you the link so you can review it and publish it yourself. A product tour usually arrives without steps, because its steps point at elements of your website that you pick in the tour editor.

Shifts

Clock in and out, correct mistakes and pull the numbers. Needs the Time Management permission. Other people's shifts and payroll need All Shifts, and the hours report needs its Reports sub-permission.

  • "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."
  • "Show the hours report for last month."
  • "Who clocked in from a phone this month?"

Reports

Ask for numbers in your own words and compare them. Needs the Reports permission, and the credit balance is for the workspace owner only.

  • "How is my team doing?"
  • "How is the AI agent doing?"
  • "Which countries are my visitors from?"
  • "How many AI credits did we use this month compared to last month?"
  • "What's my credit balance?"

Questions about your account and Yaplet itself

  • "Explore Yaplet: what can it do for me?" goes through the product areas, what your plan and permissions include and what to set up next.
  • "Fix a problem: find what is missing or failing" checks your account and proposes the fix.
  • "How do I set up email automations?" searches our documentation and help articles and answers from them.

And more: what asking adds

Most of the above you could also do by hand, one page at a time. This is what Yaplet adds on top.

One request, several products

Yaplet can take many steps for one answer, and it carries on after each Confirm. So you can describe a whole job:

  • "Add a document about our refund policy to my brand's knowledge, then write a help article about the same thing."
  • "Review how my AI agent did this month, find the conversations where it failed, and diagnose the latest one."
  • "Create a help center, write five articles about common support topics and publish them."

Finding out why the AI answered something

Ask about any AI answer, or press Explain AI answer under it in the inbox. Yaplet gets the question and the answer, the passages the AI actually found with their relevance, the searches it ran, what any API tool returned, and the settings it followed. It tells you in plain words why the answer came out that way and offers to add what was missing.

Seeing the page you are on

Yaplet always knows which page you are on, and the item you have open on it: the conversation or ticket, the visitor whose panel is open, the documentation page, the product source, or the help center you are in. Ask about "this ticket" or "this visitor" and it reads that record directly, with your own permissions, so it sees only what you may see. When you say "this", "here" or "the error I see" about something else, it reads the page, including form values you haven't saved. It never reads password, key or card fields. The details are in Yaplet Assistant.

Checking your whole account

One question goes through every brand you can see: widgets that never loaded, AI agents that are off, knowledge documents that aren't active, websites with new pages waiting, failing product feeds, unverified sending domains, paused campaigns, phone agents that can't take calls and workflows with failed steps.

Checking its own work

When Yaplet makes or changes an email, it checks the result at computer and phone width and tells you in words what it finds: unreadable text, broken images, placeholder links, a layout that phones shrink. You don't see the screenshots in the chat, so ask it to describe the email if you want more. When it writes a workflow, it checks the plan before you ever see a Confirm card, and a plan with errors never reaches you.

Speaking first

With the Yaplet speaks first permission, Yaplet doesn't wait for you. It introduces pages you open for the first time, writes to you about things like a failed payment or a paused sending domain, and catches you up when you have been away. See Yaplet Speaks First.

What Yaplet can't do yet

These have no action behind them today. Yaplet can explain them from our documentation and point you to the page, but you do the work there:

  • Phone: resuming a paused phone agent, the call recording switch and phone numbers. These stay with a person anyway.
  • Social posts: writing, scheduling and reviewing AI social posts.
  • Affiliates: partners, commissions and payouts.
  • Security: rules for blocking visitors and network protection. Banning one visitor from a chat does work.
  • Agent monitoring: flags and rules on how agents answer.
  • Audience: session replays and user journeys. Visitors themselves can be looked up.
  • Boards and forms: creating ticket boards and forms. Using existing ones works.
  • Parts of the AI agent page: Starters and Suggestions. Yaplet can read your starters and propose new ones, but adding them stays with you.
  • Workspace settings: message templates, languages and AI models. For sending domains, Yaplet can read the state and walk you through it, but it can't change the setup.
  • Shift types: Yaplet can read them but not create or change them.

Ask anyway if you need one of these. Yaplet tells you it can't, and you will usually see the line Passed on to the Yaplet team. It may be added in a future update. under its answer.

What Yaplet won't do, even if you ask

These are limits on purpose, not gaps. They apply to every AI connection, and Yaplet tells you where to do them yourself.

  • 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: sending, scheduling or resuming a campaign, switching an email automation on, approving an autopilot issue, or letting an autopilot send without approval. It also won't rewrite an issue of an autopilot that sends without approval, or change the settings of one that is on and sends without approval, and it won't remove a step with a written email from an automation.
  • Going public: publishing a social post, switching a chat workflow on, or publishing a banner, chat message, survey, tour or news post.
  • The workflow you have open: Yaplet never saves it. It offers Apply to canvas, and you press Save.
  • Deleting in bulk: one named record at a time, and never a brand, widget, knowledge base, documentation set, board or subscriber. Subscribers can be unsubscribed or removed from the list instead.
  • Emailing an address it picked: an email to a visitor or a ticket's reporter goes only to the address saved on that person.

The full list is on the MCP Server page.

© 2026 Yaplet. All rights reserved.