Skip to main content

Why Telegram

Where your users are

900M+ active users. If your community, customers, or team uses Telegram — meet them there.

Rich bot features

Commands, inline keyboards, media, groups, channels, DMs. Telegram has one of the best bot APIs available.

Zero friction

Users don’t need to install anything. They just message your bot on Telegram.

Step-by-step setup

1

Create your bot with BotFather

Open Telegram and search for @BotFather. Send /newbot and follow the prompts:
  1. Enter a display name (e.g., Acme Support)
  2. Enter a username — must end in bot (e.g., AcmeSupportBot)
  3. BotFather sends you a token: 7123456789:AAFxxxxxxxxxxxxxxxxxx
Save this token — you’ll need it in the next step.
2

Connect the token to Bothive

In your Bothive dashboard:
  1. Open your bot → Channels
  2. Click TelegramConnect
  3. Paste your bot token
  4. Click Save
Bothive automatically sets the webhook. You’ll see a green when the connection is live.
3

Write your HiveLang bot

4

Test in Telegram

Search for your bot in Telegram → send /start → confirm the welcome message appears.Send a real support question and check that:
  • The response arrives within 2 seconds
  • Formatting looks correct in Telegram
  • Tool calls (if any) succeed
5

Set BotFather commands (optional)

Add a command menu so users know what your bot can do:
  1. Message @BotFather → /setcommands
  2. Select your bot
  3. Paste your command list:

Telegram-specific formatting

Bothive uses Telegram’s MarkdownV2 formatting when responding on the Telegram channel:
Tell your agent explicitly in the instructions to use Telegram formatting. The model adapts its output to whichever channel it’s responding on if you guide it.

Common Telegram setup issues

Check that the webhook is set correctly. In Bothive, open Channels → Telegram and click Verify webhook. If it shows a red , try reconnecting with the token.
By default, Telegram bots only receive messages that start with / in groups. To change this, send /setprivacy to @BotFather and disable privacy mode — or ensure users tag your bot with @YourBotUsername.
This usually means you’ve connected the same bot token in multiple places. Make sure the token is only connected to one Bothive bot.
Check which tools are being called in the Run trace. Slow tool calls are usually integration issues — check your integration credentials. You can also switch to a faster model (e.g., GPT-4o mini or Groq) for response-speed-critical bots.

Groups vs DMs

Test with real people and inspect the result

Once Telegram is connected, share https://t.me/YourBotUsername with a small tester group. Testers only see the Telegram bot; they cannot see your Bothive project, credentials, knowledge base, or internal traces. After each meaningful test, open Agent dashboard -> Observability. Bothive records the run’s Telegram channel, session boundary, message delivery activity, latency, final response, failures, and any tool or memory events that the runtime emitted. The channel health panel also shows whether the Telegram connection is active and its inbound/outbound message counts.
Ask testers to send a known answer, an unknown answer, a follow-up question, and a request that would need a tool. That gives you a much better signal than only testing /start.

Next reads

Slack Bots

Deploy to Channels

Observability