Not specified
52 proposals
Technical assignment
for the client search automation system in Telegram Development
1. General task
It is required to create an MVP system for automatic client search in Telegram chats with the provision of found users to sales department operators.
The system should consist of:
user bots based on Telethon;
Telegram bot for operators;
Telegram bot (or a separate administrative section within the bot) for the administrator;
PostgreSQL database;
Docker configuration for deployment in configuration.
A web panel is not required at this stage.
2. Working with multiple Telegram accounts
The system must not be limited to one Telegram account.
It is necessary to ensure support for multiple accounts (for example, 5 or more) with the ability to increase their number without changing the configuration.
For each account, there should be the ability to:
authorize via Telethon;
maintain its own session;
connect a new account;
disconnect an account;
replace an account without losing the database.
The administrator should be able to independently connect new Telegram accounts.
3. Distribution of chats among accounts
The system will use a large number of Telegram chats (approximately 800 or more).
All chats are included in a single system.
The system should automatically:
manage chats among connected accounts;
observe Telegram restrictions;
Handle the need to transfer a chat to another account;
Prevent duplication of one chat by multiple accounts (unless specifically included).
It is desirable to ensure load balancing among accounts.
4. Managing the chat list
The administrator should be able to do this without the developer's involvement:
connect a chat;
delete a chat;
import a list of chats from a file;
bulk upload chat costs;
enable or disable monitoring of individual chats;
restart history collection for a selected chat.
After adding a new chat, the system automatically includes it in one of the key accounts.
5. Data collection
For each connected account, it is necessary to implement:
Initial parsing
After adding a chat:
loading message history for the specified period;
saving all available information.
Monitoring
After the initial loading is completed:
constant tracking of new messages;
saving new users;
saving new activity of existing users.
6. Handling Telegram blocking
requires proper handling:
FloodWait;
PeerFlood;
temporary Telegram restrictions;
erroneous connections;
connection breaks;
possible reconnections;
temporary unavailability of the account.
If one account is temporarily blocked by a restriction, the rest of the work continues.
7. User data storage.
For each user, the following should be saved:
Telegram ID;
first name;
last name (if available);
username;
profile link;
list of all chats;
message text;
date and time of the message;
link to the message (if obtainable from Telegram).
User merging is performed exclusively by Telegram ID.
If a user has written in 20 chats — they display one card.
8. User card
The operator should see:
first name;
username;
Telegram ID;
profile link;
list of all chats;
messages;
activity date.
Example:
User:
Ivan Ivanov ID
user
: 123456789
Chat "Business":
Message:
"Good day, interested in advertising"
Date:
01.03.2026 12:15
Chat "Marketing":
Message:
"Who is handling promotion?"
Date:
05.03.2026 18:42
9. Operator work
The system should automatically form a queue of clients.
After receiving a client:
the user is assigned to an operator;
the second operator cannot receive the same client;
maintain a history of actions.
Statuses:
Took the client;
Unavailable;
Could not reach;
Refusal;
In progress;
Call back;
Delete.
After selecting a parameter, the next client will automatically open.
10. Reissuing users
There should be an option to configure user reissuance.
For example:
never;
after 30 days;
after 60 days;
after 90 days;
arbitrary period.
11. Administrative section
The administrator should be able to:
Account management
add an account;
delete an account;
view account status;
view account restrictions;
replace an account.
Chat management
add;
delete;
import;
export;
disable monitoring;
disable monitoring.
Operator management
add;
delete;
block;
change rights.
Parser management
start collection;
stop collection;
rebuild history;
view current status.
Statistics
View:
number of users;
number of messages;
number of processed clients;
number of active operators;
number of connected accounts;
number of active chats.
12. Database
Use PostgreSQL.
It is necessary to store:
users;
messages;
chats;
activity;
Telegram accounts;
operators;
processing statuses;
processing history;
distribution of chats among accounts.
13. Scalability
The architecture should provide the ability to:
connect 10, 20 or more Telegram accounts;
connect thousands of Telegram chats;
handle load;
export data;
work with CRM;
connect new features without a complete project overhaul.
14. Docker
The executor should set up:
docker-compose.yml;
Dockerfile;
launch instructions;
update instructions;
database backup instructions.
The system should manage the command as one.
