Live chat for your website, answered from Telegram

A visitor writes in the chat window on your site, the question lands in your Telegram group as a separate topic, and your reply from that topic shows up in their window within seconds. One line of code, no developer needed.

Free. Your whole team answers, with no per-agent fee.

Safe and lawful: we follow the Russian personal data law (152-FZ), the databases are kept in Russia, conversations travel over an encrypted connection, keys and tokens are stored encrypted.

Sign up
Through Telegram, Yandex, VK or email, no password and no card
Set it up
Domain, how the window looks, the Telegram group
Paste
One line of code or a ready 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...
Visitors write from one window on your site, and you answer from wherever suits you
The chat window
A button in the corner of your page: this is where visitors write. They still see the history a week later.
Your Telegram group
A separate topic for every visitor. The group admins answer from there.
Your CRM
Bitrix24 and RetailCRM: the message arrives where the manager already works with customers.
Your own software
API and signed webhooks: your code picks the messages up and answers.

What it really looks like

Screenshots of the real chat window and dashboard. Taken on our test site, so the conversation is a test one.

The WidgetChat window on a website: a visitor question and a support reply
What the conversation looks like for a visitor on a desktop. Taken on our test site; the shop does not exist.
The Telegram step in the WidgetChat dashboard
The Channels step: your own bot or the WidgetChat bot, and four marks that light up by themselves once everything is done in Telegram.

What the chat window can do

It is a conversation, not a contact form. This 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, ready to be corrected before sending.
Annotated screenshots
A button in the paperclip menu captures the page; on the capture you can crop a part and draw an arrow or a frame. Ctrl+V pastes an image from the clipboard.
Reply to a specific message
When a conversation holds several questions, the answer is tied to the one being discussed. Both sides see the quote.
Sent messages can be corrected
A visitor fixes a typo or a wrong number within a day. The edit and the deletion reach the agent 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.
Events for your analytics
Opening the window, the first message and the support reply are sent to Yandex Metrica and to Google tags through dataLayer, with no code changes. In Metrica you only create the goals.

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 question goes to Telegram A separate topic for this visitor appears in your support group, with a notification.
  3. 3 Someone on the team answers The reply from that topic shows up in the chat window within seconds, with no page reload.
  4. 4 The conversation is kept The person came back a week later in the same browser, and the history is there.

Why replies are written from Telegram

A usual live chat asks you to keep a separate agent panel open, and while nobody has it open, the visitor waits. A small team almost 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.

What the visitor gets

A conversation, not a form: attach a file, take a screenshot and mark what is wrong on it, dictate instead of typing (dictation recognises Russian). The history is kept in the browser, so a person who comes back a week later continues from the same place. On a phone the window takes up almost the whole 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 answer from Telegram
Usually
A usual chat needs an agent panel kept open: while nobody has opened it, the visitor waits.
Here
The question arrives in your Telegram group as its own topic. The reply from there goes back into the chat window, no separate panel needed.
One conversation, wherever you answer from
Usually
Most services give you one workplace, their panel, and answers from a CRM or over the API live in separate histories.
Here
Telegram, a Bitrix24 open channel, RetailCRM chats and your own software over the API work at the same time and look at the same conversation. The visitor receives the reply once, wherever it was written.
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 with HMAC-SHA256, and if your endpoint stays silent we try two more times. The dashboard shows the delivery log with response codes.
Voice turns into text
Usually
Voice messages usually arrive as a file the agent has to listen to.
Here
The visitor dictates, the agent 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 and its own Telegram group: messages, history and settings never cross.
Data handled under personal data law
Usually
Many chats keep conversations wherever their cloud happens to be, and say little about it.
Here
The databases are in Russia, and we are listed in the Roskomnadzor register of personal data operators under number 34-26-045552. We do not sell conversations or use them to train AI models.

Frequently asked questions

How much does the chat cost?

Nothing: WidgetChat is free, and there are no limits on sites, conversations or agents. Prices of other services with the date we checked them are on the pricing page.

Do I need a developer to add the chat?

No. The dashboard gives you one line of code to paste into the site template before the closing body tag. If a contractor looks after the site, the dashboard also prepares a task you can forward.

Do agents need a separate app?

No. Replies are written from ordinary Telegram, on a phone or a computer. Every visitor gets their own topic in your group, so conversations never mix.

What if nobody answers right away?

The message waits in the topic. The visitor sees the reply the next time they open the site in the same browser, and hears a sound if the tab is still open.

Does it work on phones?

Yes. On a phone the window takes up almost the whole screen and uses the system pickers for files, photos and video.

Where can I answer visitors from?

Visitors write from the chat window on your site. You answer from the Telegram topic, a Bitrix24 open channel, RetailCRM chats or your own software over the API. All of them see the same conversation.

Is there a chatbot or AI replies?

No. Every message goes straight to a person. There is no flow builder and no AI auto-reply in WidgetChat.

Updated