Knowledge base BOT-T
Guides, support answers, and reference materials about the BOT-T service.
For example: payment, plans, Telegram bot, reviews...
Search results
The BOT-T knowledge base is the service reference hub with guides, support answers, and materials about the platform. Here you will find descriptions of modules, scenarios, payments, broadcasts, and other cabinet features. Topics range from basics to practical cases. The section helps you learn the interface, find the right feature, and solve common questions on your own. The catalog below leads to second-level articles — open a section and open a detailed guide. The BOT-T knowledge base is updated with the product so bot owners can rely on current recommendations.
Article catalog
General questions about bots
- What is the BOT-T bot builder?
- Frequently Asked Questions
- System of replenishment/debiting
- Referral system
- How do I send a broadcast in my Telegram bot
- WEB modules
- Free messages
- Access modules
- Configuring scenarios in the Telegram bot
- User profile
- Message for an invalid command
- Payment methods
- User management in the Telegram bot
- How can I view my statistics in a Telegram bot?
- Product search system setup
Types of bots and their individual configuration
Special services
API - for developers
Services
Popular questions
How to protect a bot from a ban and keep the audience
Create a channel from a different Telegram account (not the one that owns the bot) and add a mandatory subscription check to that channel in the bot. Then users stay linked to the channel: if the bot is restricted or blocked, you can reconnect a new bot and recover the audience through the channel and subscription requirement.
Are there limits on broadcasts and users in BOT-T?
BOT-T does not impose a hard ceiling on bot audience size or the number of broadcasts. You can grow users and messaging as the project scales, guided by your goals rather than artificial platform caps.
Bot types in the project and practical examples
In BOT-T the bot type sets the starting framework: which modules are ready, how sales, access, and communication work. The main types and practical cases are below.
Digital goods bot (auto-delivery, no cart). For keys, files, courses, accounts, and other digital content. Payment is checked automatically and the product is sent without an operator, 24/7. Teams often add a channel or chat lock, password or captcha on entry, referrals, and personalized broadcasts. Best when the purchase is one item or a simple set without a full cart.
Physical goods bot (with cart). A full shop in Telegram for clothes, food, souvenirs, and offline assortments. Includes cart, promos, bonuses, phone login, delivery calculation, reviews, and branded receipts. Choose it when one order has several items and delivery matters.
Access-control bot for a private chat or channel. Paid entry with automatic access after payment. Fits info products, courses, and paid communities. Supports auto-renewal, multi-channel packs, promo codes, and payment tracking.
Support bot. One inbox for tickets, categories, assignees, and history. Clients write in Telegram; the team replies from the bot or the site. Useful when private chats can no longer handle the volume.
Free-form bot. Custom funnels: message and button chains, quizzes, lead capture, broadcasts, delayed messages, and sales sequences. Pick it when you need your own user path without a fixed shop or subscription scheme.
Join-request bot for a chat or channel. Handles requests by your rules: auto-approve, filtering, and warm-up before entry. Helps with UTM sources, pre-entry funnels, and keeping the audience in the bot. Good for moderated communities and paid traffic.
In the BOT-T knowledge base, start from the goal — digital sales, retail, paid access, support, a custom funnel, or community growth — and open the articles for that framework.