A few years ago, "put your support on Telegram" meant hiring someone to write a bot, host it on a VPS, keep the process alive, and restart it every time it silently died at 3am.

In 2026 it's a token and a paste. That's the whole job.

This guide walks through connecting a WhisperChat AI chatbot to Telegram - six steps, roughly five minutes, no server, no code, and no webhook URL to wire up by hand.

Why Telegram is worth the five minutes

If your audience already lives in Telegram - and for a lot of communities, ecommerce brands and crypto/SaaS products, they do - then asking them to go back to your website to open a chat widget is friction you don't need.

Here's what you get once it's connected:

The same brain as your website widget. Telegram answers run through the same retrieval pipeline and the same knowledge base. Train once; every channel stays in sync.
Each chat keeps its own context. Follow-up questions work exactly like they do in a browser conversation.
Sources come attached. When an answer came from crawled pages, up to three source links get appended.
It's quiet in groups. In a group it only replies to its command or a direct mention, so it never talks over your community. In one-to-one chats it answers everything.
Your own welcome message. You control what people see the moment they press Start.
Everything is logged. Telegram questions land in your dashboard History, Insights and Leads, marked with Telegram as the source.

Before you start

Short list:
A trained WhisperChat chatbot. Telegram answers come from the same knowledge base as your website widget. If it hasn't been trained yet, do that first or the bot will just tell people it doesn't know.
A Telegram account - you need it to talk to @BotFather.
The Premium plan. Telegram is a Premium integration.

Nothing to install. Nothing to host. WhisperChat registers the webhook with Telegram for you.

The setup, in six steps

Two places: @BotFather inside Telegram, and your chatbot's Deploy page in WhisperChat. That's the entire surface area.

Step 1 - Create the bot with @BotFather

Open@BotFather in Telegram and send:

/newbot

It asks two things:

A display name - what people see at the top of the chat. Use your brand name.
A username - must end in bot. This is the public handle people search for, like @acmesupport_bot.

Pick the username carefully. You can change the display name later; the username is harder to move once people have it saved.

Step 2 - Copy the API token

BotFather replies with a token that looks like this:

123456789: AAFxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Copy it. Don't paste it into a group chat, a shared doc, or a screenshot - anyone holding that token controls your bot.

If it ever does leak, send /revoke to BotFather and reconnect in WhisperChat with the new one. Takes thirty seconds.

Step 3 - Connect it in WhisperChat

Switch to your dashboard. Open the chatbot → Deploy → find the Telegram card → press Connect.

Paste the token. While you're in there you can also:

adjust the welcome message people see when they press Start
set the group command the bot responds to

Press Connect Telegram.

Step 4 - That's it, the webhook is already registered

This is the step that used to be the hard part, and now it isn't a step at all.

WhisperChat validates your token against Telegram's API and calls setWebhook for you, with a secret only your chatbot knows. There's no URL to paste anywhere and no bot process to keep running.

One thing to know: if your deployment isn't reachable over HTTPS, Telegram refuses the webhook - and the connect step tells you exactly why rather than failing silently.

Step 5 - Press Start and ask something

Use Open bot in Telegram in the dialog. Press Start and you'll see your welcome message.

Then just type a question:

What is your refund policy?

The bot shows typing… for a moment, then replies with the answer and the pages it came from. In a one-to-one chat, every message gets answered - no command needed.

Step 6 - Optional: add it to a group

Add the bot to a group like any other member.

In a group it stays quiet unless someone actually addresses it:

/ask what are your pricing plans?

…or mentions @yourbot directly. That's on purpose. A bot that jumps into every group conversation gets muted within a day.

Done. Six steps, and half of them were copy-paste.

What's happening behind the scenes

Skip this if you just want it working. Read it if you're the one who has to explain the integration to someone else.

Every update is authenticated. The webhook URL carries a per-chatbot secret, and the same secret is registered as Telegram's secret_token so it arrives in a request header too. An update that proves neither is rejected before anything is read from it.

Answers are generated off the request. Telegram re-delivers an update until the webhook answers 200, and retrieval plus generation takes longer than Telegram is willing to wait. So WhisperChat acknowledges immediately, shows the typing… indicator, and sends the reply from a background worker as a normal message.

A retry never answers twice. Each Telegram update ID is claimed in an idempotency log before the worker starts. A redelivery is acknowledged but never generates - or bills for - a second answer.

Long answers don't get truncated. Telegram caps a message at 4,096 characters, so longer answers are split on line breaks and sent as consecutive messages. Formatting is sent as Markdown and retried as plain text if Telegram rejects it, so the answer always gets through one way or another.

Privacy: what the bot can actually see

Only one secret is involved here - your bot token - which makes this simpler than most integrations.

Your token stays server-side. It's never sent back to the browser; the dialog shows a masked placeholder instead. Leaving the field empty keeps whatever's already saved.

Only messages sent to the bot reach WhisperChat. In groups, Telegram's own privacy mode means it doesn't receive ordinary chatter at all. It's not listening to your community.

Disconnecting removes the webhook from Telegram and clears the stored token. The bot still exists in your Telegram account until you delete it with @BotFather, but it stops answering immediately.

Things that trip people up

"I connected it but nothing happens when I message the bot." Press Start first. Telegram doesn't deliver messages to a bot until the chat has been started.

The bot ignores me in a group. That's the design. Use /ask your question or mention @yourbot. Plain messages in a group are never delivered.

Telegram refused the webhook. Your deployment isn't reachable over HTTPS. The connect step reports the specific reason - read it, it's usually a certificate or DNS issue.

I changed the token and it broke. Reconnect in WhisperChat with the new token. The old webhook was registered against the old one.

Answers say "I don't know" for everything. The chatbot hasn't been trained, or the content it needs isn't in the knowledge base yet. This isn't a Telegram problem - test the same question in your website widget and you'll get the same answer.

Does this eat my message allowance?

Yes - each answered question costs one message from your plan, exactly like a widget conversation, with the same multiplier for premium models.

If your subscription credits run out, a small daily grace allowance kicks in before the bot starts declining questions.

Worth knowing: a user's Telegram name is stored as the conversation's display name only. It's an identity, not contact details someone submitted, so a Telegram chat doesn't automatically become a lead in your dashboard.

Is Telegram the right channel for you?

Blunt version: it depends entirely on where your people already are.

If your customers are in Telegram groups, Telegram is where they'll ask. Making them open a browser to reach your support widget is a real drop-off, and you'll never see the questions you lost.

If they're not - if Telegram is just a channel you feel like you should have - the widget or Slack is a better use of your setup time. Presence on a channel nobody uses is a hobby, not a strategy.

FAQ

Do I need to host anything or keep a bot process running? No. WhisperChat handles the webhook and generates answers server-side. Nothing runs on your machine.

Do I have to paste a webhook URL anywhere? No. That's the part WhisperChat does for you. You paste one token and you're finished.

Can I use the bot in a group? Yes. Add it like any member. It responds to /ask or a direct @mention only.

Does the bot read every message in my groups? No. Telegram's privacy mode means ordinary group chatter never reaches it.

Can one Telegram bot serve several chatbots? Each connection ties one Telegram bot to one WhisperChat chatbot. For a second chatbot, create a second bot with @BotFather.

What happens if I change the token? Reconnect in WhisperChat with the new token and the webhook re-registers.

Do Telegram conversations appear in my analytics? Yes. They're logged with Telegram as the source and show up in History, Insights and Leads.

Can I change the welcome message later? Yes, in the same connect dialog.

Wrapping up

The bar for "have a Telegram support bot" has dropped through the floor. It used to be an engineering project. Now it's a /newbot command and one paste.

What still takes real effort is the knowledge base underneath it. A bot on Telegram with thin documentation is just a faster way to disappoint people. Train it properly, then let it work.

Open your dashboard to connect it, or check thefull Telegram integration docs for the reference version.

How to Connect an AI Chatbot with Telegram in 2026 (Step-by-Step)