Connect a Telegram bot to your website's support inbox

Some customers will never use the chat bubble on your website. They found you on Telegram, they live in Telegram, and if they can't reach you there, they'll reach a competitor who can. The usual fix — checking a separate Telegram app all day next to your support inbox — works right up until the day it doesn't, and a paying customer waits four hours because the conversation happened in the wrong app.

The better fix: make Telegram a channel of the same inbox. Visitors message your bot; the thread shows up next to your website conversations, marked with a Telegram badge; you (or the AI agent) reply from one place, and the answer is delivered back into their Telegram. Here's the whole setup, honestly timed at about five minutes.

Step 1: create a bot with BotFather

In Telegram, open @BotFather — Telegram's official bot for making bots. Send /newbot and follow the two prompts: a display name (what customers see, e.g. "Acme Support") and a username ending in bot (e.g. acme_support_bot). BotFather replies with an API token — a long string like 123456789:AA.... Copy it.

That token is the bot. Treat it like a password: anyone holding it can read and send messages as your bot.

Step 2: paste the token into Leadiosa

In the dashboard, go to Settings → Integrations → Telegram channel and paste the token. Leadiosa registers the webhook with Telegram itself — no server configuration, no chat-ID hunting. The Telegram channel is available on Pro and up.

Step 3: send your bot a message

Open your bot in Telegram (t.me/your_bot_username), press Start, and type anything. Within seconds the conversation appears in your inbox with a Telegram badge. Reply from the inbox — the message arrives back in Telegram. That's it; you're live.

What works in Telegram threads

Everything that makes the inbox worth having works for Telegram conversations too:

• The AI agent — in copilot mode its drafts wait for your approval; in autopilot it answers Telegram customers directly, grounded in the same knowledge base as your website chat. (New to the two modes? Copilot vs Autopilot explains when to trust which.)
• The FAQ bot, conversation tags, assignment and human handoff — same behavior, same rules.
• Attachments in both directions — a customer's photo renders in the inbox; a file you send from the inbox arrives in Telegram (photos inline, other files as documents, captions included).

Two honest limitations: widget-specific mechanics don't apply — there's no "visitor is typing" preview and no page context (Telegram has no page), and the offline email transcript doesn't apply either, because a Telegram customer already has the full history in their own app. Which, if you think about it, is the point.

"Telegram notifications" is a different thing — you may want both

Leadiosa has two Telegram integrations, and mixing them up is the most common support question we get about this feature:

• Telegram channel (this guide) — customers talk to your bot, conversations land in the inbox.
• Telegram notifications — your team gets alerts in its own group chat when something happens (new conversation, offline lead, rating), each with a button back to the inbox. One-way: you read in Telegram, you reply from the inbox.

They're independent and they run fine simultaneously — just use two different bots, one public-facing, one internal. Setup for the notifications side is in the integrations docs.

Why this beats a standalone Telegram workflow

One inbox means one history: when the same customer writes on your website today and in Telegram tomorrow, your team sees both threads in the same tool, with the same tags and the same AI assist. It also means your response-time stats, ratings, and the weekly digest cover all your support traffic, not just the part that happened in the widget. Channel coverage is exactly where most small-business chat tools make you pay per add-on — we compared the field honestly in Leadiosa vs Tidio if you're weighing options.

Have a website but no chat on it yet? The five-minute WordPress setup pairs well with this guide — do both and your website and Telegram traffic share one inbox by the end of the coffee.