Website live chat with Telegram replies: how it works
I built a live chat for a small business workflow: visitors stay on the website while the owner replies from Telegram. This is a technical account of the working solution, including limitations and a comparison with cloud services.
The goal: do not force the customer to switch apps
A Telegram link sends the visitor away from the website. A cloud live-chat product introduces another dashboard, notifications and often a recurring fee. That can be excessive for a single owner.
The desired path was short: the customer writes where they already are, the owner replies in Telegram, and the answer returns to the original website chat.
Architecture without a separate CRM
- Website message
The form validates length, origin and limits before the server creates a protected conversation identifier.
- Telegram notification
The bot sends the message, contact and source URL. The identifier connects the reply to the correct browser.
- Owner reply
The Telegram webhook accepts a signed request only from the allowed owner.
- Visitor receives it
The widget checks for new messages and renders the answer without reloading the page.
What had to be fixed for iPhone
Safari zooms a page when a focused input uses a font below 16 px. The send button could consequently move outside the visible area.
Mobile fields now use 16 px and the panel height follows visualViewport. When the keyboard opens, the message list shrinks while the composer remains visible.
Security controls
- secret webhook signature and owner Telegram ID check
- cryptographically random conversation identifiers
- message rate, request size and field length limits
- honeypot and request-origin checks
- safe text rendering without HTML execution
- storage outside the public directory with automatic cleanup
- duplicate Telegram delivery protection
JivoChat, Tidio, Crisp or a custom chat
| Scenario | Best fit | Reason |
|---|---|---|
| One owner replies personally | Custom chat | Simple Telegram workflow and no mandatory plan |
| Several agents and departments | JivoChat, Tidio or Crisp | Routing, roles and reporting are already built |
| A special workflow is required | Custom chat | Logic and integrations can be changed |
| Launch is needed in minutes | Cloud service | A standard widget is faster to install |
Limitations worth stating clearly
This does not replace a contact centre. The base version has no routing for dozens of agents, advanced reporting, attachments or omnichannel CRM.
Its advantage is a short personal conversation, controlled storage, custom design and the ability to add only useful functions.
Implementation cost
A standard installation on one website starts at PLN 690. It includes Telegram bot setup, template adaptation, mobile testing and baseline security.
Multiple languages, CRM, n8n, Make or automated replies are estimated after inspecting the website.
Short answers
Is this an AI chat?
No. A person replies in the base version. AI can later handle repetitive questions.
Can I see a demo?
Yes. The chat in the lower-right corner of this page is the working version.
Does it support Joomla?
Yes. It is designed for Joomla, WordPress and custom HTML/PHP websites.
Why not use a Telegram link?
The visitor stays on the website, does not need an account and sees the conversation in its original context.
Need this chat on your website?
Open the working widget or send the URL. I will check the CMS and provide a fixed estimate.