The widget opens on top of your site. The visitor picks the chat or a messenger, the bot follows your flow, and you see the conversation in the dashboard inbox — next to Telegram and your other channels.
Four steps — and your site gets a button with your bot behind it.
Title, description, button colors and a banner. The editor shows the widget exactly as your visitors will see it.
Links to your bots in Telegram, WhatsApp and Viber plus any links of your own. On desktop the messenger opens via a QR code.
Pick a bot from the project — it gets the “Web chat” channel. The flow, buttons and AI agent work just like in messengers.
One line in the site footer. Works with WordPress, Webflow, Shopify or your own template — anywhere you can add custom HTML.
To let the bot answer free-form questions from visitors, add an AI agent to the flow
The website chat is one more channel of your bot. Messages, buttons under a message and under the input field, images, video, files and phone number requests work with no extra setup: one flow for all channels.
The AI agent types its answer in front of the visitor, and a mini app — booking or a request form — opens on top of the chat without leaving your site.
Not everyone wants to type in a website chat. The same window holds buttons for Telegram, WhatsApp, Viber and any links of your own: the visitor picks a familiar messenger and lands straight in your bot.
On a phone the messenger opens with one tap; on desktop the widget shows a QR code — point the camera, and the conversation continues on the phone.
A reply may arrive while the widget is collapsed or the person has switched to another tab. The widget lets them know: a red badge on the button, a short sound, a counter in the tab title and a preview of the reply above the button.
The conversation is kept: if the visitor reloads the page or comes back tomorrow, the chat opens where they left off.
A visitor who opens the chat becomes a bot contact — with variables, tags and history, just like in Telegram. The operator sees which page the person wrote from and can reply personally: the message arrives in the website chat.
Broadcasts and the CRM work for website contacts too, and the widget settings show how many people wrote from this particular widget.
Button and icon colors, title, description, a banner linking to a promotion — everything is edited with a live preview. The chat can open right away or as a button in the channel list.
List your site’s domains and the widget won’t run on anyone else’s pages. The embed code is the same forever: edit the widget in the dashboard and the site updates itself.
List the sites where the widget is allowed — it won’t load on other pages. Subdomains are set with a *.example.com mask.
An image above the channel list linking to a promotion, the catalog or a new collection.
Photos, documents, audio and video up to 10 MB. File uploads are switched off with one toggle.
Answers from your knowledge base and types the reply in front of the visitor — like the AI chats people already know.
Appointment booking, a menu or a form opens from a bot button without taking the visitor off your site.
An operator sees the conversation in the dashboard and can reply at any moment — the visitor gets the answer in the same chat.
A broadcast message lands in the website chat: the visitor sees it with a badge on the button when they return.
A cap on new visitors per hour from one IP: fake traffic won’t eat up your contact package.
A tag in the page address — the wbt_start or ref parameter — is passed to the bot when the chat opens, like a start parameter in a Telegram link.
Widget labels come in English, German, Russian or Ukrainian: the language is taken from the page.
A separate widget for each site or section: different bots, texts and channels. A finished widget is copied in one click.
The “Powered by Watbot” line at the bottom of the widget is removed with a separate plan option.
Anyone with a website and visitors who would rather type than call.
The bot answers about stock and delivery, shows the catalog and takes the order right in the chat.
Salons, clinics, car services: the bot answers common questions and books a convenient time.
Advice on the program, help choosing a plan and a payment link — while the interest is still warm.
An AI agent with a knowledge base handles the first line; tricky questions go to an operator.
A couple of questions about budget, area and timing — and a qualified lead with contact details goes to the CRM.
Menu, order status and promotions — in the website chat or in the messenger the customer prefers.
The widget with messenger buttons is free and takes a few minutes to set up. The bot chat runs on the Pro plan — the first 7 days are free.
The widget itself is free: a button on your site with links to messengers works without a subscription. The bot chat is the bot’s “Web chat” channel and is part of the Pro plan; a new account gets Pro free for 7 days. The “Powered by Watbot” line at the bottom of the widget is removed with a separate option.
Open the widget in the dashboard, go to “Place on site” and copy the code. Paste it into the site footer — before the closing body tag. Any site or builder that accepts custom HTML will do: WordPress, Webflow, Shopify or your own template.
Only by location: it is the same bot and the same flow. Messages, buttons, images, files, conditions and the AI agent work the same way, with nothing extra to configure. If you like, the website chat can have its own button layout.
Yes. All website conversations land in the dashboard inbox next to chats from other channels. The operator sees which page the visitor came from and can reply personally — the message appears in the website chat.
Only someone who opens the chat becomes a contact — not every visitor of the page. These contacts count toward your plan’s contact package together with messenger subscribers. To keep fake traffic from eating the package, the widget settings have a cap on new visitors per hour from one IP.
While the page is open, a badge on the button, a sound, a counter in the tab title and a preview of the reply announce the new message. If the person has left the site, the reply waits in the chat: on the next visit the conversation opens where they left off. To keep such visitors, ask for a phone number in the flow or suggest continuing in a messenger.
Yes. The chat is turned on with a separate toggle. Without it, the widget stays a free button with links to your messengers, social networks and any other addresses; on desktop the messenger opens via a QR code.
The code loads asynchronously and doesn’t block page rendering. The chat itself is loaded only when a visitor opens it.
Yes, up to 100 widgets per project. Each has its own texts, colors, set of channels and bot, and the domain list limits where the widget can run.