Build the flow once. It runs in Telegram and as a chat widget on your website — the same nodes, the same contacts, the same analytics. Web chat is not a second product to maintain; it is the same bot answering on a second channel.
One flow, two channels
Most teams end up with two disconnected things: a Telegram bot, and a website chat tool that knows nothing about it. FlowCastle treats a website visitor and a Telegram user as the same kind of contact, handled by the same flow.
That is not a copy of your flow. It is the same flow. Message steps, menus, conditions, variables, HTTP requests to your own API — every node you already built runs unchanged when the conversation arrives from your website instead of Telegram. Change the welcome message once and both channels change.
Add it without a token
Telegram bots need a BotFather token. Web chat needs nothing. Inside your application, add a bot, choose Web Chat, and it exists — no developer account, no approval step, no API key to request. You can have a working widget before you have decided on a bot name.
Three ways to put it on your site
The floating bubble. One script tag before the closing `</body>` tag puts a chat bubble in the corner of every page. This is what most sites want.
An inline frame. An iframe snippet drops the chat into a specific place on a specific page — a support page, a pricing page, a landing page — at a width you choose.
A standalone page. Every web chat bot also gets its own full-screen URL you can link to, put behind a QR code, or hand out in an email. That page is installable as a web app, so a regular visitor can keep it on a phone home screen and receive push notifications.
The embed guide walks through all three, with the exact snippets.
What visitors can actually do
The widget is a real chat surface, not a contact form with a chat skin:
- Tap buttons and menus, including multi-choice selections and buttons that ask for confirmation
- See images, open documents, and download files your flow sends
- Upload their own photos and files, up to 50 MB
- Watch a typing indicator while the bot is working
- Come back tomorrow and find the conversation still there
Returning visitors are recognised in their browser, so a conversation that started on Monday continues on Thursday instead of restarting from the welcome message.
Make it look like it belongs to you
Colour mode light, dark, or follow the system. Accent colour, bubble colours, chat background — including a background image. Your avatar, your favicon, your header. Panel width and corner radius. A welcome message that sends itself when the chat first opens, and a dismissible notice under the header for the thing you actually need people to read.
There is also a setting for whether the chat opens by itself when the bot replies, or just shows an unread badge and waits.
When a person needs to take over
Bot conversations become inbox conversations. When a visitor asks something the flow was not built for, the flow can hand the conversation to a human, and your team answers from the live chat inbox — the same inbox that holds the Telegram conversations. The visitor stays in the same chat window and never learns they crossed a boundary.
The chat widget on this website runs on FlowCastle, using a template you can install and read: Website Chat Assistant.
Your own domain
By default the widget loads from FlowCastle. If you would rather it lived at `chat.yourcompany.com`, add the subdomain, create the CNAME record we show you, and we provision the TLS certificate. DNS and certificate issuance usually complete quickly, though it can take up to 24 hours. Subdomains only — an apex domain like `yourcompany.com` cannot be used for this.
Everything downstream still works
A web chat visitor becomes a contact. That means the rest of the platform applies without special handling: broadcasts, drip sequences, goals and conversion reporting, tags and variables, the analytics funnel that shows where people stop. One audience, however they arrived.
What it does not do
Worth knowing before you build around it:
- Payments do not run in web chat. Telegram Payments works in Telegram. A flow with a payment step will not take money from a website visitor — send them to your existing checkout instead.
- Telegram Mini App buttons are Telegram-only. They are ignored by the widget.
- The floating bubble sits in the bottom-right corner. That position is not configurable yet.
We would rather you read that here than discover it in production.
Start with the channel you have
Build the bot for Telegram, add the widget to your site the same afternoon, and let the same flow answer both. The free plan needs no credit card.