Appearance
Connect Telegram
Give any agent its own Telegram bot: paste a bot token, connect it, and let Telegram DMs, groups, and forum threads drive real agent runs. Use this when you want an account's agent reachable from a Telegram chat instead of the web chat.
Telegram is the one channel you connect directly from the agent's Settings tab. The website widget, WhatsApp, and native voice calls live in the Sales Platform, not here.
In the app
Open the agent → Settings tab → Channels → Telegram bot. https://app.mychatbot.app/agents/ → pick an agent → Settings.
Cheat sheet
Connect in three steps
| # | Step | Where |
|---|---|---|
| 1 | Create a bot in @BotFather and copy the token (123456789:AA…) | Telegram app |
| 2 | Paste the token into Bot token from @BotFather and press Connect | Agent → Settings → Channels |
| 3 | Status flips to Connected as @your_bot — message the bot to test | Agent → Settings → Channels |
The token is checked with Telegram the moment you press Connect. A bad token surfaces an inline error and nothing is saved. On success the panel shows Connected as @your_bot (a link to the bot) with a Disconnect button.
What you see per state
| State | Panel shows | What to do |
|---|---|---|
| Not connected | Token field + How to create a bot with @BotFather link + Connect | Paste the token, press Connect |
| Connected | Connected as @your_bot (opens the bot) + Disconnect | Message the bot to test |
| Error | A red message with the reason (e.g. "already connected to another agent") | Fix the cause, re-paste, Connect again |
Built-in slash commands
| Command | Effect |
|---|---|
/start | Sends the default welcome message |
/help | Sends the default help message |
/new | Starts a fresh conversation — the old thread stays intact and readable |
Register a bot end to end
1. Get a token from BotFather
In Telegram, open @BotFather, run /newbot, and copy the token it issues. It looks like 123456789:AA… — the numeric prefix is public, but the part after the colon is a secret. The How to create a bot with @BotFather link in the panel points at Telegram's own tutorial.
2. Paste it and Connect
Paste the token into Bot token from @BotFather and press Connect. Behind the scenes MyChatBot verifies the token with Telegram, points Telegram's message delivery at your agent, and stores the token encrypted. When it finishes, the panel shows Connected as @your_bot.
If the same bot is already wired to a different agent, you'll see an error telling you to disconnect it there first — one bot belongs to one agent.
In the app
Agent → Settings → Channels → Telegram bot → paste token → Connect.
3. Test it
Message the bot.
- Private chat — any message triggers a run.
- Group / supergroup — the bot only replies when it's
@-mentioned or when someone replies to one of its own messages. A plain group message with no mention is ignored.
Security
Two things protect a connected bot, and both are handled for you:
- The token is encrypted at rest. Your BotFather token is never stored or shown in plain text, and it's never written to logs. If you ever need to rotate it, disconnect and reconnect with a fresh token.
- Inbound messages are authenticated. Every update Telegram sends is checked against a per-bot secret before the agent trusts a single byte of it. That secret is regenerated automatically every time you reconnect — so re-pasting the token is the clean fix for most connection problems.
Same agent, different door
A Telegram run uses the identical configuration as the agent's web chat — the same model, the same tools, the same skills, the same instructions. Telegram is just another entry point into the same agent.
The model is set on the agent, not the channel
There is no per-Telegram model picker. The bot runs on whatever model the agent uses in the web chat. To change it, change the agent's model (see Models & reasoning) and Telegram follows.
Voice, images, and albums
- Voice notes are transcribed automatically before the agent reads them, and the transcript is passed along as text — so the agent understands the message even on models that can't hear audio. The transcription counts toward your usage the same way a chat turn does.
- Photos, audio, video, and files are attached to the run and show up inline in the agent's Conversations tab in the app.
- Albums (several photos sent as one group) are treated as a single message, so sending five photos doesn't spawn five separate runs.
Don't rapid-fire messages
If you send a second message while the agent is still answering the first, the bot replies:
Still working on your previous message — give me a moment and resend when you see my reply.
This is deliberate — it protects the in-progress answer from being lost. Wait for the reply, then send your next message.
WARNING
Back-to-back messages get the "still working" notice rather than being queued. This is the safeguard against a dropped reply, not a bug.
Where Telegram conversations show up
Telegram chats appear in the agent's Conversations tab in the app, tagged with a Telegram badge. They're read-only from the web — you continue the conversation by replying from your Telegram app, and the new messages show up here. Photos and voice-note transcripts render inline.
Starting a /new conversation from Telegram opens a clean thread; the previous one stays in the Conversations list.
In the app
Agent → Conversations tab.
Disconnect
Press Disconnect in the Telegram panel and confirm. New messages stop reaching the agent; the registration is retired cleanly. To move the bot to a different agent, disconnect it here first, then connect it on the other agent.
In the app
Agent → Settings → Channels → Telegram bot → Disconnect.
Best practices
Do
- Connect one bot per agent — each bot belongs to exactly one agent.
- Re-paste the token (reconnect) if the panel shows a connection error — reconnecting regenerates the security secret and re-registers the bot cleanly.
- Use
/newto reset context instead of expecting the bot to forget on its own.
Don't
- Don't reuse the same bot on two agents — you'll get an "already connected to another agent" error.
- Don't paste a token another account has already connected — same error.
- Don't expect to switch models from Telegram — set the model on the agent instead.
Test it
- Connect the token and confirm the panel shows Connected as @your_bot.
- DM the bot — you should see a typing indicator, then a streamed reply.
- Send
/new, then a message — a fresh thread appears in Conversations; the previous one is untouched. - Add the bot to a group and
@-mention it — it replies; a plain group message with no mention is ignored. - Send two messages back-to-back — the second draws the "still working" notice, proving the safeguard.
Billing can block replies
If the account has no active subscription or has hit its usage cap, the bot replies with a subscription / top-up message linking to https://app.mychatbot.app/agents/subscription instead of running. On a transient billing hiccup the bot errs on the side of answering, so a blip never silently drops your message.