Connect Telegram

Your assistant can answer on Telegram, with the same knowledge base and persona it uses on your widget. You create a bot yourself in Telegram and paste its token in. There's no login, no developer account and no app review.

In the left menu, under Channels, open Telegram.

Who does what

Meta plays no part in Telegram.

Step by step

1. Open Telegram and message @BotFather. Create a bot (or use one you already made) and copy the token it gives you — it looks like 123456789:AAExampleBotToken.
2. In Telegram, paste the token into the field and click Connect Bot.
3. That's it. The bot appears in the table below as soon as it connects. You're then asked whether the AI should start replying (see below).

To reconnect later — for example after regenerating the token in BotFather — paste the new token into the same field and click Connect Bot again.

After connecting: "Should the AI start replying to your customers?"

Every bot you connect for the first time starts with your assistant off. Right after the connection goes through, the dashboard asks "Should the AI start replying to your customers?", showing the bot it's about, with Yes and No and the note "You can change this anytime." The question can't be closed or skipped.

• Yes — your assistant starts answering with the next message. The row shows Active.
• No — it stays off. Messages still arrive in your Inbox for you to answer yourself, and the row shows Paused.

You're only asked when your assistant could actually reply there — that is, while your plan is active. Otherwise the bot stays off quietly, and the question appears once you have a plan.

Reconnecting a bot you already had keeps its setting and asks nothing.

Pausing and disconnecting

Telegram rows get three switches: AI replies to messages ("Answers your customers in Telegram."), AI reads photos and AI listens to voice notes (see Usage and plans). With replies off the row reads "Replies paused: messages on that channel still arrive in your Inbox, but the AI will not answer them until you switch “AI replies to messages” back on. Nothing received while paused is answered afterwards." Disconnect removes the row entirely; customers messaging the bot get no reply until you reconnect.

Moving a bot to another of your workspaces: Disconnect it in the old workspace, then paste its token in the new one. The old conversations stay in the old workspace.

If something goes wrong

"That doesn't look like a valid Telegram bot token."

The token you pasted is either mistyped, or Telegram no longer recognises it (for example, it was regenerated in BotFather). Fix: open your bot in @BotFather, get its current token, and paste that in.

"This Telegram bot is already connected to another workspace. Disconnect it there first."

This bot is still connected in a different Agentech workspace — another of yours, or someone else's. Nothing was changed on the bot. Fix: open that workspace and Disconnect the bot there, then paste its token here. Or use a bot you haven't connected elsewhere, or create a new one in @BotFather. If that other workspace isn't yours, email us.

A Telegram row says "Needs reconnect"

Telegram reports the bot's token as revoked or deleted — usually because it was regenerated or the bot was deleted in BotFather. Fix: paste a new bot token in the field above Telegram and click Connect Bot.

I connected a bot and the assistant doesn't reply — the row says "Paused"

New connections start with the AI off, and you answered No to "Should the AI start replying to your customers?" — or you weren't asked because your plan isn't active. Fix: switch AI replies to messages back on on that row. If you were never asked and there's no plan, request access from Support → Contact us first.

"Your assistant stopped replying on Telegram: …" / a row says "Not replying — plan ended"

The strip at the top of the dashboard reads "Your assistant stopped replying on Telegram: [reason]" — "your plan has ended", "you've used this month's messages", "you've reached today's message limit" or "your workspace has no package that includes replies here" — and the row shows "Not replying — plan ended", "Not replying — messages used up", "Not replying — daily limit reached" or "Not replying — no package". The bot is still connected; your assistant has no messages left to answer with, so it stays silent. Customers are sent nothing about it, and their messages still arrive in your Inbox. Fix: press Request access or Contact us on the strip (both open Support → Contact us), or email us. Replies start again with the next message once you have messages available. Details in Usage and plans.

When to email us

Email admin@agentech.tech, or use Support → Contact us in the dashboard, when:

• Your bot is connected to a workspace that isn't yours.
• A fresh token from BotFather still gets "That doesn't look like a valid Telegram bot token."
• The row says Active but the bot never answers.

Tell us your workspace name, the bot's @username, and the exact message you saw. Never send us the bot token itself. We reply by email.