WidgetChat — live chat for your website with Telegram, WhatsApp and MAX

WidgetChat
One snippet and the widget is live

A live chat for your website that brings messages from the widget, Telegram, WhatsApp and MAX into one dashboard.

Sign up
Email or Telegram
Set it up
Domain, channels, colour
Paste
One snippet, plus a task for your developer
mysite.com connection
active
<script
async
src="https://api.widgetchat.ru/widget/bozex-support-widget.js"
data-widget-id="wc_9qA...Lk"
></script>
Write to us
Support
Support
Hi! I can help you choose and answer any questions.
0:25
Message...
Messages arrive from four places and end up in a single conversation
Website
The chat window in the corner of the page. The visitor still sees the history a week later.
Telegram
Your support group: a separate topic for every visitor.
WhatsApp
Messages from the messenger land in the same conversation.
MAX
A Russian messenger: the reply goes back to the person in MAX.

What the chat window can do

It is a conversation, not a contact form. Below is what makes a visitor finish the question instead of closing the tab.

Voice becomes text
On a phone dictating is easier than typing. The recording is transcribed and the text appears in the input field — it can be corrected before sending.
A screenshot straight from the clipboard
Ctrl+V right into the chat window attaches the image from the clipboard. A file can also be dragged in or picked with the button.
Reply to a specific message
When a conversation already holds several questions, the answer is tied to the one being discussed. Both sides see the quote.
Sent messages can be corrected
A typo or a wrong number is fixed by the visitor without writing the message again. The edit and the deletion reach the operator, both in Telegram and in the CRM.
Several photos as one gallery
Five photos do not stretch the conversation over five screens: they fold into a gallery, like in a messenger, and open on tap.

How the chat works

  1. 1 The visitor writes The chat button sits in the corner: the window opens on top of the site and nobody has to leave the page.
  2. 2 The message goes to Telegram A separate topic for this visitor appears in your support group.
  3. 3 Anyone on the team answers The reply from that topic shows up in the chat window within a second, with no page reload.
  4. 4 The conversation is kept The person came back a week later: the history is there and the conversation continues.

Why replies are written from Telegram

A usual live chat asks you to keep a separate operator panel open: while nobody has it open, the visitor waits. A small team never has that panel open — but Telegram is always open. So messages arrive there, every visitor gets their own topic, and the reply comes back into the chat window on the site within a second.

What the visitor gets

A conversation, not a form: attach a file, take a screenshot, dictate instead of typing — the recording turns into text right away. The history is kept, so a person who comes back a week later continues from the same place. On a phone the window opens full screen; on a desktop it can be moved and resized.

How it differs from other website chats

Only what works today. On the left is how a usual live chat is built, on the right is how it works here.

You can answer from Telegram
Usually
A usual chat needs an operator panel kept open: while nobody has opened it, the visitor waits.
Here
The message arrives in your Telegram group as its own topic. The reply from there is back in the chat window within a second — no separate panel at all.
Several places to work from at once
Usually
Most services give you one workplace: their panel or nothing.
Here
Telegram, the dashboard, your CRM and your own software over the API work at the same time. A reply written in one place appears in the others, and the conversation does not split in two.
One person, one conversation, wherever they wrote from
Usually
The widget, messengers and marketplaces usually live in separate windows and separate histories.
Here
The site widget, Telegram, WhatsApp, MAX and Wildberries chats come together into one card and one message thread.
Events arrive signed
Usually
Webhooks often send plain JSON: there is no way to tell a real request from a forged one.
Here
Every event is signed (HMAC-SHA256) and retried if your endpoint stayed silent; the dashboard shows the delivery log with response codes.
Voice turns into text
Usually
Voice messages usually arrive as a file the operator has to listen to.
Here
The visitor dictates, the operator reads ready text and answers without turning the sound on.
Sites do not share conversations
Usually
Several sites in one account often share a single stream of messages.
Here
Every site has its own workspace: messages, history and settings never cross, even inside one account.