How long does it take to launch?
Usually five minutes: paste the script, set up the greeting and pick the operators.
We collected the answers to the most common questions about setup, operator workflow and integrations. If you did not find what you need, write to us from the contact page.
Usually five minutes: paste the script, set up the greeting and pick the operators.
A single <script> line with your site key, right before the closing </body>. No other files are needed.
No, not if you can edit your site template or the “footer code” block in your CMS. Everything else is configured in the dashboard.
Yes. The widget is a plain JS script — a spot in the template or in a custom code block is enough.
Yes, every site gets its own key, and their dialogs and routes stay separate.
The script loads asynchronously and never blocks rendering: the page opens exactly as fast as before.
The site key in the script must match the key in the dashboard, and the domain must be on the allowed list for that site.
Yes, you can spread requests across the team and set routing rules.
In Telegram — in a private chat or in a team group. The answer is a plain reply to the bot message.
The customer name and contacts, the page they are writing from and their city — the card arrives together with the request.
With the “Claim”, “Release” and “Transfer” buttons: everyone sees who is handling the customer, so replies never double up.
After the configured number of minutes the bot reminds the admin — no request goes unnoticed.
Yes, configure the operator schedule and auto-replies for out-of-office hours.
They send /op_me to the bot. After that the admin hands out routes — with /assign or in the dashboard.
Webchatix connects to CRM and email services through ready-made connectors.
Yes, images and documents travel both ways, and the whole history stays in the dashboard.
The widget adapts to the screen automatically and stays comfortable to read and type in.
Yes: colour, button position, operator name, avatar and greeting text all follow your brand.
Yes, when they come back the conversation continues from where it stopped.
On your own server, the connection runs over HTTPS, and dashboard access is protected by a key.
The dashboard overview shows the number of sites, operators, open and claimed dialogs, and the list holds the request history per site.