Where your customers already are
The same conversation, the same knowledge, the same actions — in any channel.
Chat window: one line of code
In the page footer — and the round button you just saw appears in the corner.
<script src="https://youselfbot.com/widget.js" data-bot-key="pk_your_key" data-api="https://api.youselfbot.com"></script>
The same place as any visitor counter: the page footer, right before </body>. Paste it once and you're done: you change the color, greeting and title later in the dashboard, with no need to paste the code again.
This is the only place on the whole site where you need code — and it's exactly one line, which you copy, not write.
Messengers and email
Customers message you where they already chat with friends — and get answers from your materials.
You create a bot in @BotFather, paste the token into the dashboard — that's it. It starts receiving messages right away.
- Message
@BotFatherand create a bot — it will give you a token. - Paste the token into the dashboard.
- Done: the bot answers from the same knowledge as the chat window.
It sees photos, transcribes voice messages and answers what was said, and if a recording can't be made out, it'll ask to have it typed instead.
Discord
/ask — Discord doesn't deliver regular messages to bots without a persistent connection.Slack
Your own app
A mobile app, an internal chat, a POS — any system of yours sends a message and reads the reply right away.
POST /v1/channels/chn_.../inbound/SECRET { "conversation": "user-42", "text": "when are you open?", "sender_name": "Olya" }
{ "answer": "We're open daily from 9:00 to 20:00." }
This is the channel that keeps the list open: anything that can send a request and read a response can speak in your assistant's voice — with the same knowledge and the same actions.
This section is the only one on the site addressed not to you but to whoever built your app. If there's no such person, you don't need it: the chat window and messengers are enough. And if there is — everything for developers is in its own section: API, MCP and webhooks.
When a customer asks for a person
The assistant goes quiet, the request comes to you, and the customer sees your reply in their window within seconds.
Of course. Press the button and I'll bring the owner into this same conversation.
Hi, I'm here. How can I help?
While a person is handling the conversation, no credits are spent at all.
You never both reply at once: as soon as a person takes the conversation, the assistant stays silent until you hand it back. While a person is talking, no credits are spent at all.
Calling a person doesn't work in every channel
In the chat window and in your own app, the customer presses a button — and you reply from the dashboard. Telegram, Viber, and WhatsApp have no button, but it's enough to write “get me a person”: the assistant goes quiet, and your reply from the dashboard reaches the customer in the same chat.
In email, Discord, and Slack you can't call a person: the assistant answers there on its own, from the knowledge you gave it. If you need live replies every day, use the chat window or a bot in Telegram, Viber, or WhatsApp.
Put it where people already message you
Free plan: one assistant, 10,000 credits a month, no card.