- Privacy-First Design – Fully compliant with the Telegram API. Pure message forwarding only — no data is ever stored!
- Anti-Spam Protection – Smart abuse prevention to keep both customers and support agents safe from spam and unwanted messages.
- Group Chat Integration – Seamlessly forward chats to support groups for clear, organized message handling. Great for teams with multiple agents.
- Lightning-Fast Response – Powered by AWS global infrastructure with millisecond-level latency and 99.98% uptime.
- Full Message Support – Handles every type of Telegram message, no exceptions.
- Totally Free to Use – Core two-way customer support features are 100% free for life!
Give it a try: @FriesOfficialBot
https://t.me/FriesOfficialBot
An open-source bidirectional bot for Telegram. It helps to avoid spam messages and allows restricted clients to contact you smoothly.
中文文档 | Sample Bot | Sample Backend
(Note: After interacting with the sample bot, check the background to understand the principle.)
(Note: The sample background is a public group for demonstration purposes. For private deployment, it's recommended to use a private group for security reasons.)
- When a client contacts customer service through the bot, all messages will be completely forwarded to the background management group, creating a separate sub-forum named after the client's information to distinguish them from other clients.
- Replies from customer service in the sub-forum can be directly sent to the client.
- Customer service can configure whether to continue the conversation with the client by closing/opening the sub-forum.
- Provides a permanent ban solution. There is a switch in the environment variables.
- Provides a /clear command to clear all messages in the sub-forum, also deleting user messages (not recommended, but sometimes necessary). There is a switch in the environment variables.
- By using sub-forums, multiple management members can be added to share the customer service workload.
- Complete communication records with clients can be intuitively retained.
- It's possible to know which customer service representative replied to a particular message, maintaining coherent customer service.
The main principle of this bot is to forward the conversation between the client and the bot to a group (preferably a private group) and categorize each client's messages into a sub-category. Therefore, before starting, you need to:
-
Find @BotFather and apply for a bot.
-
Obtain the bot's token.
-
Create a group (set as public as needed).
-
Enable "Topics" in the group.
-
Add your bot to the group and promote it to an administrator.
-
Remember to include "Message Management" and "Topic Management" in the administrative permissions.
-
Use the bot @GetTheirIDBot to obtain the built-in ID of the group and the user ID of the administrator.
-
Use the bot @GetTheirIDBot to get the built-in ID and administrator user ID of the group.
Open .env_example, fill in your bot's Token, account's API_ID/HASH, the management group's ID, and the administrator's ID. Save .env_example as .env.
python3 -m venv venv
. venv/bin/activate
pip install -r requirements.txt
python -m interactive-bot
Note: For formal operation, it's recommended to use process management tools like PM2, supervisor, etc., along with watchdogs to achieve uninterrupted operation, automatic restart, and failure recovery.
- Support message reply functionality. Messages can reference each other.
- Improve the database.
- Add client's human-machine recognition to prevent bored individuals from using userbots to spam.
- Add and recognize media group messages.
- Streamline the code, use payload to expand forwarding parameters.
- This product is open-source under the Apache License.
- The author, MiHa (@MrMiHa), is a struggling programmer, not a coal miner. If you have questions, please don't come and give orders.
- Discussion group: https://t.me/DeveloperTeamGroup. Feel free to join and play around.
- Feel free to fork, but remember to retain the content in "About".
- The initial version was written in 2 hours. If you like it, please donate. If you have trouble deploying, ask for help in the group.
- RackNerd's servers are recommended. In fact, I use this one. It's cheap enough. This one is enough: 2 cores 3GB - $27 per year
- If you can't deploy it, you can ask everyone in the group to help. You can also share servers with everyone: https://t.me/DeveloperTeamGroup.