Technical assignment for the development of a Telegram bot with a management system

1. General information

The project represents a management system for Telegram bots, where users can register their bots, manage content, analyze users, and integrate Facebook Pixel. The main bot of the system performs administration and management functions for registered bots.

2. System functionality

2.1. Management bot (main bot)

2.1.1. Bot registration

• The user sends the bot token.

• The system automatically registers the bot and adds the user to the administrators.

• Launching a new bot is done using containerization (Docker or a similar method).

• In response, the user receives a message with the bot ID in the system, the bot's name, and the creator's data.

2.1.2. Control panel in the bot

• View the list of all registered bots with IDs and names.

• Ability to delete a registered bot.

• View the number of active and inactive users for each bot.

2.2. Functionality of each registered bot

2.2.1. Management menu (via inline buttons or messages)

1. Delays (scheduled posts)

• The "Add post" button allows the user to send a message that the bot will save for later distribution.

• After sending the post, the bot asks:

  • How many seconds after the start should it be sent?

  • How many seconds should it be deleted?

• Automatic deletion of messages after the specified time.

2. Bot duplication

• The "Duplicate bot" button requests the ID of another bot from the system and copies all saved forwarded posts to the current bot.

3. Number of users

• The "Number of users" button displays statistics of active and inactive users of the bot.

4. User view

• The "User view" button allows the bot to send a message on behalf of the user.

2.2.2. Facebook Pixel integration

• The command /cr requests the pixel ID and pixel token from the user.

• After receiving the data, the bot generates a link with the domain associated with this pixel.

2.3. Additional functionality (optional)

• Ability to edit posts (title, body, buttons).

3. Technical requirements

• Use of Python (Aiogram / Telethon / PyTelegramBotAPI) for interaction with the Telegram API.

• Data storage in PostgreSQL / MySQL.

• Docker for containerization and management of running bots.

• Server on Linux (Ubuntu / Debian), deployed on a VPS / Dedicated server.

• Integration with Facebook API for working with the pixel.

4. Timeline and cost estimation

4.1. Development of the management bot

• Bot registration and launch via Docker — 2 days.

• Control panel in the bot — 1 day.

4.2. Development of functionality for registered bots

• Settings menu (inline buttons) — 1 day.

• Delays (scheduled posts) — 2 days.

• Bot duplication — 1 day.

• User statistics — 1 day.

• User view — 1 day.

• Facebook Pixel integration — 2 days.

• Additional functionality (editing posts) — 1 day (optional).

4.3. Total time costs

Estimated implementation time: 7 days of development + 7 days of testing.

4.4. Cost estimation

The cost of the project depends on the chosen technologies and developers, approximately:

• Basic version — from $400.

• Full version (with post editing) — from $600.

4.5. Support and server resources

• Support cost: $30 per month, includes updates, bug fixes, and basic technical support.

• Recommended server specifications:

  • CPU: 2–4 vCPU (depending on the number of bots).

  • RAM: 4–8 GB.

  • Storage: 50–100 GB SSD.

  • OS: Linux (Ubuntu 22.04 / Debian 11).

  • Additionally: Docker, PostgreSQL/MySQL, API integrations.