How to set up an AI agent for your Telegram community in under 10 minutes — covering knowledge base upload, bot connection, and going live

Why most Telegram bots die within a week

The usual failure mode is treating the bot like a script instead of a knowledge-grounded agent. Scripted bots run out of answers on day two and users stop tagging them. This guide walks you through the connect, teach, and tune flow that keeps the bot useful past the honeymoon week.

What you need before you start

Three things:

1. A Telegram account.

2. A dedicated bot created via @BotFather (30 seconds, covered below).

3. An Aidevelopia account. If you don't have one, the free tier is enough to get started, no card needed.

No hosting, no webhook config, no code. The platform handles those.

Step 1: Create the Telegram bot via BotFather

Open Telegram, search for @BotFather, hit Start.

Send /newbot. Give it a display name (this is what users see in chat headers) and a username (must end in bot, must be unique). BotFather replies with a token that looks like 123456789:AAH-abc123XYZ.... Copy it. Treat it like a password.

Optional but recommended, in the same @BotFather chat:

• /setdescription, /setabouttext, /setuserpic to brand the bot.

• /setprivacy and choose Disable if you want the bot to answer any message in a group. Leave enabled if you want it to only respond to @mentions and slash commands.

Step 2: Paste the token into Aidevelopia

Log into Aidevelopia. In the sidebar under Channels, click Telegram.

Paste your bot token into the Token & Health tab and save. The dashboard sets your webhook automatically. When you see the webhook status flip to active with a green pill, the bot is live. That whole step is under 30 seconds.

Step 3: Feed the bot your knowledge

Now the bot has a mouth. Give it a brain.

Aidevelopia's Knowledge tab (under the Workspace section of the sidebar) accepts three sources:

• URL crawl. Paste your help center or docs URL. The platform crawls, chunks, and embeds automatically. Best for docs sites, Notion public pages, GitBook, Shopify FAQ pages.

• File upload. Drop PDFs, DOCX, TXT, or Markdown. Same pipeline. Good for internal SOPs or product PDFs you don't want on a public site.

• Manual FAQs. For the top questions you want pinned answers to. Faster to iterate than a doc.

Start narrow. For a first deployment, aim for your 20 most-asked questions plus your product pages. Ignore anything you wouldn't want on a busy Slack channel. You can grow it later.

Step 4: Test the bot in your DMs

Search for your bot by username in Telegram. Hit Start. Type one of the questions you seeded.

If the answer looks off, edit the source in the Knowledge tab and re-ask. Changes propagate as fast as the next embedding job finishes, usually seconds.

Use this DM as your staging environment. Do the awkward tests here before the community sees them.

Step 5: Add the bot to your community group

In your Telegram group, open the group settings, tap Add Member, search for your bot's username, add it.

The bot needs to be a group admin with, at minimum:

• Send Messages permission.

• Delete Messages if you want the keyword filter to auto-delete banned words.

• Ban Users if you want moderation commands and CAS auto-ban to work.

Grant admin, restrict everything else. Standard defense.

Step 6: Choose how the bot behaves in group chats

Under Settings in your Aidevelopia Telegram tab, three switches shape the experience:

• Reply on mention only. ON means the bot only responds when someone @mentions it or uses a slash command. OFF means it reads every message and responds when it's confident it has the answer. Big groups usually want ON.

• Fun mode. ON means when the bot is unsure but has a plausible guess, it labels it as a best guess and shares it anyway. OFF means it honestly says "not in my docs" instead. Communities that value personality want ON, technical/support communities want OFF.

• Admin chat IDs. Add your personal Telegram user ID (or a private admin group ID) here. This is where the bot sends escalation alerts when a user taps the "Talk to a human" button.

Save. Behavior applies instantly, no restart.

Step 7: Turn on the moderation and join gate

This is the part every guide skips. Bots without moderation get overrun.

In the Moderation tab:

• Escalation thresholds. Set warn/mute/kick/ban counts. Defaults are 3/5/7 warns which handles polite communities. Under active spam, tighten to 2/3/4.

• Keyword filter. Add spam patterns you actually see in your niche. For crypto communities: airdrop, pump, wallet, t.me/. For general communities: nude, onlyfans, bit.ly. Minimum 3 characters per pattern.

In the Join-Gate Security section (same tab):

• CAS spammer lookup. Leave ON. It's the free public banlist of known Telegram spammers. Blocks known bots at the door with zero UX cost.

• Auto-kick bots on join. ON if only humans should join.

• Captcha challenge. OFF by default because it adds friction. Turn ON if your group is public or you're seeing raids. Every new member has to tap a button within 60 seconds or gets auto-banned.

Save.

Step 8: Optional, add proactive features

Under the same Telegram section you'll find two more tabs worth knowing:

• Scheduled messages. Broadcast content on a cadence (send at X, repeat every 2/3/4/6/12/24 hours or weekly). Good for weekly announcements, product tips, or event pings.

• Menus. Rich message templates with inline button grids. Author them from the dashboard, trigger with a slash command like /menu, on new-member join, or from another menu's sub-menu button. This is how you build the tappable Wallet/Shop/About experience you see on the fancy community bots.

Both are optional. Neither runs until you configure them.

What doesn't work, common pitfalls

• Regenerating your bot token. Doing /token in @BotFather to get a new token silently kills your existing webhook. Aidevelopia's webhook monitor will flag it as failed within a few minutes, but you'll need to paste the new token in the dashboard.

• Not making the bot a group admin. Without admin, the bot can't delete banned-word messages or run moderation commands. It'll look silent when it isn't.

• Overloading the KB with everything. Dumping 5,000 unrelated docs dilutes retrieval. Start with the top-20 questions plus your product/pricing pages.

• Leaving reply_on_mention_only OFF in a busy group. The bot will jump into every conversation. Great for small communities, noisy for big ones.

FAQ

Do I need to host any servers? No. Aidevelopia handles webhook registration, message routing, and scaling.

Does the bot handle multiple languages? Yes, automatically. The bot detects the language of each user's message and replies in that same language, no matter what language your knowledge base is in. You don't need to duplicate content across languages. Tested and shipped for English, Spanish, French, Yoruba and 50+ others.

What happens when a user asks something outside the knowledge base? With fun_mode OFF, the bot honestly says "not in my docs yet" and shows a "Talk to a human" button. When tapped, your admins get a DM with the user's question, and can reply directly from Telegram using the native Reply gesture. The bot relays it back. Full two-way handoff, no dashboard round-trip.

Can I connect one bot to multiple groups? Yes. One bot, multiple groups, one dashboard.

Can I switch which AI model powers the bot? Yes. Under Settings, plans above the free tier let you pick between Groq, Cerebras, OpenAI, Anthropic, and Gemini. Different providers, different speed/quality/cost profiles.