Working with Yaplet

How to get good results from Yaplet: how to ask, what the Confirm card means and why changes wait for you, long multi-step jobs, chats, following up, and what to do when it can't do something.

How to ask

Write the way you would write to a capable colleague who is new to your business. Yaplet knows how the dashboard works and can read your account. It doesn't know what is in your head.

  • Say the result, not the clicks. "Ask visitors for their email before a chat starts" is enough. You don't need to know which tab holds that setting.
  • Name the thing. Which brand, widget, board or campaign. If you name no brand and aren't on a brand's page, Yaplet lists your brands and asks which one, unless you only have one.
  • Give the facts only you know. Yaplet can't guess your refund policy or your sale's end date. Put them in the message.
  • Describe the problem if you don't know the feature. "Visitors keep asking where their order is. What should I do?" Yaplet compares what could solve it (the AI's knowledge, an API tool, a workflow, a quick button, a form), tells you what it recommends and why, and builds it only after you say yes.
  • Point at your screen. Say "this", "here" or "the error I see" and Yaplet reads the page you are on. You see Looking at your page while it does. Yaplet also knows which item you have open — the conversation in the inbox, the ticket in its side panel, the visitor whose panel is open, the documentation page you are on or the selected product API source — and reads that item directly when you say "this"; it still looks at the page for things like an error you see.
  • Write in your own language. Yaplet answers in your dashboard's language, or in the language you write in if that is a different one.
Instead ofTry
"Improve my AI.""Add a document to my brand's knowledge about our return policy: 30 days, free for defective items."
"Make a newsletter.""Draft a campaign for the Premium group about our spring sale, 20% off until March 31, using our default template."
"My widget doesn't work.""My widget doesn't show on greenshop.example, which runs on Shopify. What's missing?"
"Clean up the tickets.""Archive every ticket in the Done column of the Bugs board."

The message box takes text only, so paste what you want Yaplet to work from. Keep passwords, API keys and signature secrets out of the chat: when something needs one, you type it into the page yourself.

What the Confirm card means

Yaplet looks things up without asking. Anything that creates, changes, deletes or sends stops at a card headed Confirm action, and nothing happens until you answer.

Changes wait for you because Yaplet is an AI and it can misunderstand you. It might pick the wrong brand or read "the old banner" differently than you meant it. The card is where you catch that, before it matters. Here is what to look at:

  • The action's name in plain words, such as Update ticket.
  • Applies to: the record it acts on. Check that it is the one you meant.
  • The values it is about to save or send.
  • Uses AI credits, when the action itself writes with AI.

Press Confirm to run it or Cancel to drop it. You never have to type anything. After Cancel, tell Yaplet what you would rather have.

A red card means it can't be taken back. Deletes and sends get a red Confirm button and the words This cannot be undone. A reply reaches the visitor the moment you confirm, and a deleted record is gone for good. For a delete, Yaplet must also give the record's exact name, and the name is checked against the record first.

Confirm all shows when two or more ordinary changes are waiting. Deletes and sends are never part of it: they are confirmed one by one.

Confirming an ordinary change is real too. Switching your AI agent on or publishing a help article takes effect at once. What waits for a person is listed under What Yaplet won't do in What Yaplet can do.

Every change, delete and send Yaplet makes goes into your Audit Log as AI change or AI delete or send, with your name on it, because it acted for you.

When a workflow is open in the editor

Yaplet doesn't save the workflow you have open. It writes the change, checks it and shows Apply to canvas. That puts the change on the canvas without saving, so you can look it over and press Save yourself. The details are in Yaplet Assistant.

Long, multi-step jobs

You can give Yaplet a whole job in one message. It can take many steps for one answer: finding the right action, reading what is there, then acting. It carries on by itself after each Confirm. You can follow along in the conversation, where each step has its own line, such as Looking through your chats… or Waiting for your OK: ….

  • Say the order if it matters. "First write the article, show it to me, and only then publish it."
  • Expect several cards. "Write five articles and publish them" means several changes to confirm, some of them together.
  • Keep working if you like. On a computer the side panel stays open while you move between pages, and the Ask Yaplet card reads Yaplet is working until the answer is done.
  • If it stops before it is done, write "carry on".
  • Some work finishes in the background. A sample autopilot issue takes a few minutes, and the pages of a website are read after the answer has ended. Ask again later: "Is the sample issue ready?"
  • Very long chats forget their beginning. Yaplet only reads the most recent messages of a chat. If it seems to have lost the thread, repeat the key facts or start a new chat.

Chats

Every conversation is saved as a chat. A new chat is a clean start, and Yaplet reads only the chat you are in, not your other ones. So use one chat per job, and start a new one when the topic changes.

Your chats are private: nobody else can open them, not even the workspace owner. Renaming, pinning and deleting are explained in Yaplet Assistant, and the list of chats in Yaplet Agent View and Chats.

Following up

  • Just keep writing. "Make it shorter." "Now do the same for my second brand."
  • Use the buttons under an answer. Yaplet may offer up to three next steps. One kind sends a follow-up request in your name, and the kind with an arrow opens a dashboard page.
  • Check the result where it lives. For what it creates, Yaplet often gives you a direct link to the page.
  • Changed your mind? There is no undo button in the chat. For an ordinary change, ask Yaplet to change it back, or do it by hand on the page.
  • Ask where it got an answer. When Yaplet answers from our documentation, it gives the links. If something sounds off, check there, because an AI can be wrong.
  • Tell it how it did. Thumbs up or down under an answer goes to the Yaplet team, with an optional note. They read the counts and notes, never the chat.

When Yaplet can't do something

Yaplet says so plainly. What to do next depends on why:

What happenedWhat it meansWhat to do
It says a person has to do thisThe job is one that always stays with a person, such as sending a campaign or changing your plan.Follow its link and do it on that page.
It says you need a permission, or that your plan doesn't include itYaplet has the same access as you.Ask a workspace owner for the permission. A plan is changed on the Billing page.
It says no action does thatYaplet can't do this yet. You may see the line Passed on to the Yaplet team. It may be added in a future update. That means your request was saved as something to add. Nobody will write back about it.Do it by hand on the page. Yaplet can still explain how.
A step says Couldn't …That step failed. Open the step to see the result.Tell Yaplet what you want to try next. If a whole answer fails, the error shows above the message box and the send button turns into a retry button.
You see Writing to Yaplet needs credit or a plan.Nobody can pay for the AI right now.Use the payment window that opens. See Who pays in Yaplet, your AI agent.

There is no person behind Yaplet. It is an AI agent, so it can't hand you over to anyone on our team. For more help, Help & docs in the sidebar opens a small menu with Help center and Documentation, each opening in a new tab.

© 2026 Yaplet. All rights reserved.