YouSelfBot
UA Guide Log in Try it free

Three conversations — and it's working

No settings you have to figure out on your own. Below are the conversations themselves, from the first sentence to “undo”.

Start a conversation How much it costs
Free plan: one assistant and 10,000 credits a month. No card needed.
Conversation one

You say what it will do

One sentence is enough to start. Whatever's missing, the Builder will ask about.

You:
I want an assistant for my café.
Builder:

Good. What will people ask it most often?

You:
Opening hours, menu and table bookings.
Builder:

Got it. Now give me materials — a website address, a price list file or just text.

Assistant created
“Café assistant”. It doesn't know anything yet — knowledge comes in the next conversation.
Try:
Demo of the first conversation: the person writes “I want an assistant for my café”, the Builder asks what it will be asked most often, gets the answer — “opening hours, the menu, and table bookings” — creates the assistant, and then asks for materials. The suggestions under the field play the same conversation for a beauty salon and an online store.

The assistant starts out empty and doesn't know anything yet — knowledge comes in the next conversation.

One sentence is enough to start, and that one sentence is the only thing required: if you change your mind, the assistant simply won't do anything.

Conversation two

You give it materials

A website address, a price list file or just text — any of these works. It will answer only from what you gave it.

You:
https://kavyarnia.example
Read 12 pages
Menu, prices, opening hours and booking terms.
You:
menu-2026.pdf
Price list added
The file stays in your materials — you can replace it when prices change.
You:
We hold the table for 15 minutes. Evening bookings are for four or more.
Saved as text
Anything that's on neither your website nor your price list, you can just say.
Builder:

That's enough for it to start answering. Next — where to put it.

Drag a file into the conversation or click:
Demo of the second conversation: the person gives a website address — the Builder reads 12 pages; drags in the file menu-2026.pdf — it becomes a material; types a booking rule as text — that goes into the materials too. On the right, the list of what the assistant now knows keeps growing. You can drag the sample files below the conversation into it yourself — each one becomes another line in the list.

It reads your website when you ask — up to 100 pages by default, up to 150 at a time on request — and tells you how many it found and what didn't open. After that it rereads it once a week on its own and lets you know in the conversation: a price changed on the site reaches the replies without you asking again. Don't want that? Say “don't reread the site”.

Conversation three

You choose where it goes

Small things it does right away. Where your customers will see the result, it asks and waits for a clear “yes”.

You:
Call it “Café assistant”.
Name changed
Its name is now “Café assistant”. It does small things right away and tells you what it did.
You:
Put it on the website as a chat window.
Builder:

Your customers will see the window, so I'm asking: turn it on for your website?

You:
Yes, turn it on.
Chat window is on
The line of code to paste is in the dashboard, under “Channels”.
Demo of the third conversation: a request to rename the assistant is done right away, and it says what it did. But the chat window on the website — what customers will see — it doesn't turn on until the person answers “yes”; until then two buttons sit under the question and the turn waits. “Try it yourself” lets you answer: “yes” turns the window on, “not yet” leaves it off.

A Telegram bot and an “every morning at 9:00” schedule are connected the same way.

None of this turns on silently: anything your customers will see always goes through your “yes”. But the window's name, hint or color it changes right away — and tells you right away what it changed.

About channels

Changed your mind? Say “undo”

Everything it did on that turn is reverted. Not “almost everything” — everything.

You:
Add an action: log bookings to a Google Sheet.
Action added
“Log booking” — a row in your spreadsheet after every confirmed booking.
You:
Undo.
Builder:

Undid everything I did on this turn.

Undone
The action is removed, and the assistant is back to how it was before this turn. Your spreadsheet wasn't changed.
Try:
Demo of undo: the person asks to add the action “record bookings in a Google Sheet” — the action appears, a line shows up in the log, and the action count goes from three to four. Then the person types “undo” — the count goes back to three, and the log line stays, marked as undone. You can undo older lines yourself: with the button next to the line or by typing “undo” in the field.

Mistakes are cheap here: until you say “yes”, customers see nothing, and whatever's already done can be undone with one word.

Try it for yourself What role it will fill