Budget: 27000 UAH Deadline: 12 days
Hello. I have extensive experience in developing Telegram bots. I am ready for collaboration.
Budget: 8000 UAH Deadline: 4 days
Hello.
I am developing bots for Telegram using NodeJS. I am ready to take on the task. Write to me, and we will discuss.
Budget: 12600 UAH Deadline: 5 days
Hello, the technical task is completely clear and I am ready to implement this project. I am waiting for feedback in private messages to clarify the details.
Budget: 8000 UAH Deadline: 1 day
Hello! I am ready to complete this project and have extensive experience in developing various applications.
Budget: 9500 UAH Deadline: 14 days
Hello! Very detailed and well-written project brief, it's a pleasure to work with such a clear vision of the product.
I develop in Python (Aiogram + SQLAlchemy), so I will be able to implement all the logic you have laid out: 1. Flexible database: I will implement the relationships "Driver - Tractor - Trailer" so that you can easily switch drivers between vehicles in the admin panel, and they will only see the data relevant to them. 2. Documents: I will create a reminder system (30/10/0 days) and separate permanent/temporary documents. 3. Smart maintenance: The most interesting part of your project brief is the analysis. I will implement logic where the bot not only records the battery replacement but compares it with the previous date and says "This is too early, go to the service for warranty." This is a cool feature for saving money for the business.
Regarding GPS and mileage: The project brief states that the ideal option is integration with GPS. I can set up the operation through the API of your GPS provider (Wialon, Navixy, or another) so that mileage and entry into geofences (Base, Service) are pulled automatically. If you are ready to start with an MVP using manual input of the odometer for now, we can do that, with the architecture laid out for future automation.
I am ready to discuss the details. What GPS monitoring service are you currently using?
Budget: 27000 UAH Deadline: 15 days
Hello.
I have reviewed the description - the task is clear. This is not just a bot with commands, but an accounting system with roles, transport, documents, dates, and regular reminders. I have worked with similar logic before, so I understand which parts are critical and where we can avoid unnecessary complications.
If the budget turns out to be limited, there are several workable options for how to reduce functionality and create a minimal version without losing the core logic. I am ready to discuss priorities and suggest the optimal approach based on your capabilities.
- Projects 6
- Rating 5.0
- Rating 1 051
Budget: 15000 UAH Deadline: 10 days
Great! I see a large-scale project with a clear structure. Such a bot will really solve the pain of document control and maintenance — everything in one place, clear for drivers, and peace of mind for you.
What you will receive:
A ready Telegram bot with an admin panel and sections for drivers
Automatic notifications for document deadlines and maintenance
A mileage tracking system and reminders
GPS integration with area reminders
A flexible architecture for further expansion
Important questions for accurate assessment:
Technical base:
What GPS tracker are you using? (access to the API is needed for mileage and geofences)
Is there currently any database of vehicles/drivers or are we starting from scratch?
How many vehicles and drivers do you plan to add?
List of documents:
Can you send a complete list of documents (temporary and permanent)?
What are the specific intervals for maintenance (oil 40k km — understood, but what about the filter?)
Notifications:
Will there be several admins or just you?
Do notifications go only to drivers or also to admins?
How I will do it:
Python + Aiogram + PostgreSQL (reliable, fast, scalable)
Adaptive database structure — easy to add new fields and functions
Clear code with comments — you will be able to modify it yourself or with another developer
Timeline: 7-14 days
Cost:
Depends on the volume of integrations, but approximately 15-20k for the full version. I will provide a more accurate estimate after clarifying the GPS and the list of documents.
I have made similar bots for fleets — I know the specifics of logistics. I write clean code that is easy to maintain and expand. Always available during the work process.
Let’s do this, answer the questions above, and I will prepare an accurate estimate with a breakdown by stages, and we can get started.
Budget: 12500 UAH Deadline: 7 days
Hello, Bogdan!
Our IT company creates and improves websites that operate stably, quickly, and solve specific business tasks for the client. We are engaged in developing websites "from scratch," as well as enhancing existing solutions, increasing their productivity and usability for your users.
We have experience in:
- developing responsive and fast websites on various platforms (WordPress, OpenCart, Shopify, WIX);
- integrations with payment systems, CRM, external services, and internal systems;
- optimizing website performance and security;
- setting up analytics and basic SEO tools;
- software development and automation of business processes: managing the client database, resource accounting, automating repetitive tasks, integrations with third-party systems;
After the project is completed, we provide 14 days of technical support. During this period, we help adapt the system to your business processes and consult on any issues related to the completed work. This ensures that the developed solution operates stably from the moment of launch and does not require additional adjustments.
We work in a structured and responsible manner - focused on results that align with your business goals.
Budget: 10000 UAH Deadline: 10 days
Hello! I can develop a Telegram bot for logistics and drivers with a clear modular architecture, making it easy to add new features without "rewriting" the entire project. I will create an MVP so that from the first release it truly helps: document control, maintenance based on mileage/date, and GPS zones.
I would like to clarify 3 things to design it correctly from the start:
Do you need notifications for the logistics/admin alongside the driver (and in what cases)?
Mileage at the start: only manual odometer or is there already a GPS tracker (which one)?
Should there be an option to have 2 drivers on one set (shifts/substitutions) or only 1 active?
On my part, I will ensure regular communication, transparent progress on stages, and strict adherence to deadlines — so that in the end you receive a tool that truly alleviates the headache regarding documents and maintenance.
- Projects -
- Rating -
- Rating 290
Budget: 8000 UAH Deadline: 15 days
Good day.
I can implement a Telegram bot in Python (aiogram) with a clear modular structure, so that the project can be easily expanded in the future.
At the first stage, I suggest focusing on the MVP:
roles (administrator / driver)
document accounting
maintenance accounting (by dates and mileage) with reminders
basic admin logic
database (PostgreSQL or SQLite at the start)
The block with GPS zones should logically be moved to a separate stage after the MVP, to avoid complicating the start and to correctly assess the integration.
Before starting, it is advisable to briefly document the requirements for the first version.
The deadlines and cost should be clarified after this, so that the assessment is accurate.
Budget: 8000 UAH Deadline: 8 days
Good day. I have experience in creating complex Telegram bots, such as CRM. Feel free to contact me.
Budget: 27000 UAH Deadline: 30 days
Good day, I will develop such a Telegram bot for you turnkey, I have over 5 years of experience in development, I will create a quality project that can be expanded and new functionality added in the future, also if needed I can implement everything on Django + aiogram and you will be able to easily integrate everything into a web version in the future. Feel free to contact me!
Budget: 8000 UAH Deadline: 5 days
Hello! I will be happy to complete this project for you. I just need to clarify some details.
I suggest discussing the details of the bot in private messages. I will create a convenient solution with a pleasant and understandable interface (markup, inline keys, menu). I have a few similar cases that I can tell you about in private.
My portfolio: Freelancehunt
Budget: 15000 UAH Deadline: 21 days
Hello
I can create such a bot
but there may be difficulties with GPS, despite the possibility of giving the bot access to geolocation, it will be quite inconvenient for drivers, of course, if they are not forced to turn this on so that you always know where they are, otherwise it will not work well
Write to me, we will discuss the details and I will provide a final estimate
Budget: 30000 UAH Deadline: 14 days
Good day, Bohdan
I have extensive experience in developing Telegram bots (reviews in the profile), I can easily implement your interesting project.
The task is clear, but we need to discuss a few important questions.
Write to me, I will be happy to collaborate. I will be waiting for feedback.
Budget: 13000 UAH Deadline: 35 days
Good day. The task is clear.
Here is how I propose to implement it:
- Python + aiogram
- Clear modular structure (admin panel/documents/maintenance/zones/analytics)
- Database: PostgreSQL or SQLite (at the start)
- Reminder scheduling (by dates and mileage)
- Driver confirmation via phone number
- MVP: manual mileage entry -> then readiness for GPS integration
I will design the architecture in such a way that:
- new types of maintenance can be easily added,
- a certain number of kilometers of mileage is counted during the working day,
- or later connect a GPS tracker without rewriting the logic,
scale to a large number of cars/drivers.
Timeline
- MVP (all main blocks without GPS integration): 3–5 weeks
- with GPS zones: +1–2 weeks depending on the service
Estimated cost
MVP: from 300-500 USD
with GPS zones: 700-900 USD
(exact price after agreement: number of document types, maintenance, message scenarios, GPS service)
What you will receive:
- a fully functional bot
- clean, understandable logic
- instructions + README
- the possibility of further support and development
To start, please clarify:
- are separate roles needed (logistician/driver/admin)?
- is there already a list of documents and maintenance regulations, or shall we create it together?
I am ready to discuss the details and start after agreement.
Budget: 8000 UAH Deadline: 4 days
Good day, I have experience working with Python as well as Telegram bots, I can complete everything quickly and efficiently, write to discuss the details.
Budget: 10000 UAH Deadline: 10 days
Good day. I am engaged in the development of Telegram bots and process automation using Python. I have experience in developing automation systems for enterprises, so I am ready to implement your project with a focus on the flexibility of the architecture.
How I propose to implement the technical part:
- Database architecture: I will use PostgreSQL. This will reliably link the driver, tractor, and trailer into one "set," while maintaining the service history for each piece of equipment separately.
- Notification system: I will implement background deadline checks (Cron). The bot will automatically check the database every morning and send push notifications regarding documents (30/10/0 days) and critical maintenance.
- Interactivity of maintenance: I will create custom scenarios. If the battery or tires need to be replaced before the scheduled time, the bot will not just provide text but will offer the driver a button to call "Warranty Instructions," which you will be able to edit from the admin panel.
- GPS and Geofences: For the MVP, I will suggest that the driver manually enter the mileage (for example, during refueling), and for the automation of geofences, I will connect to the API of your monitoring system (Wialon/Teltonika). This will allow sending prompts about AdBlue or seal checks precisely at the moment of crossing the zone.
Stages and timelines for development and testing (10 days):
- Admin panel and database (4 days): logic of "sets" and fleet management.
- Documents and maintenance (3 days): automation of counters and cyclical reminders.
- GPS block and connection checks (3 days): troubleshooting the correct operation of notifications when the driver changes the trailer or tractor.
Write to me. I am ready to discuss everything in more detail and immediately start working.
Budget: 11000 UAH Deadline: 7 days
Hello, I have reviewed the specifications for your bot, the project is not difficult and requires attention to detail.
I am ready to implement your bot and the admin panel (the admin panel is user-friendly and responsive for mobile devices).
Regarding the GPS tracker, it will be difficult to implement with the Telegram bot, as Telegram recently added the ability to broadcast location for bots, but it is necessary to force the location to update every n number of hours; a better option would be to request the odometer reading from the driver.
In implementing a similar bot, we abandoned GPS tracking due to problems. GPS tracking can be implemented in a standalone application without using a bot, but that is a different implementation option that needs to be discussed.
I will develop the bot according to the specifications, set up the server, and launch the system + 30 days of free maintenance after launch. Further maintenance and functionality improvements will be discussed.
Proposals are currently absent
Current freelance projects in the category Bot Development
A parser needs to be created to collect competitor prices, with a catalog of over 40,000 products. Access to the prices is only available under authorization.
Good day, I need help with creating the logic and implementing an idea. A chat-bot for tracking the status of document production for an educational center.
Telegram Bot
Hello. Below is a conditional technical specification for the bot for our synagogue. We need not just a Telegram bot, but a convenient mini-application for the synagogue and community, through which a person can navigate the life of the synagogue, quickly get the necessary information, view the schedule, learn about events, register, and interact with us. In terms of style and logic, we can base it on the reference bot we showed, but we need a better version: more convenient, modern, useful, and with a clearer structure. If you have strong opinions on design, UX, and structure, and you see how to improve it, we are open to suggestions. The main idea: for a person to quickly navigate the life of the synagogue through the bot. What should be in the bot. 1. Main screen with specific buttons The main screen should have clear large buttons: Today Schedule Events Shabbat Jewish calendar My dates A-Yom Yom for today Synagogue services Contacts Donate Settings 2. "Today" section This is one of the main sections. A person enters and immediately sees what is happening today. What should be displayed: what is today's Jewish date what prayers are today what time they take place what events we have in the synagogue today important dates and events in the Jewish world if relevant — time for lighting candles and the end of Shabbat Buttons inside: Prayers today Events today Jewish date Shabbat / candles More details 3. "Schedule" section Through it, a person should conveniently view the schedule. Buttons: For today For tomorrow For the week For Shabbat For holidays What inside: Shacharit Mincha Maariv lessons meals holiday services other activities with time and, if necessary, location It is important that the administration can easily update this schedule. 4. "Events" section A full section on events is needed. What should be included: upcoming events all events card for each event registration In the event card: title date time location short description register button more details button Examples of events: Shabbat lesson youth meeting lecture charity lunch women's / men's meeting holiday outing 5. "Shabbat" section This should be a separate section, not just part of the schedule. What inside: time for lighting candles time for prayers time for meals time for the end of Shabbat weekly Torah portion brief information about the upcoming Shabbat registration for Shabbat Buttons: Upcoming Shabbat Shabbat schedule Weekly portion Register for Shabbat What you need to know 6. "Jewish calendar" section What should be included: today's Jewish date upcoming holidays Rosh Chodesh fasts memorial dates brief explanation of the day / holiday Buttons: Today Upcoming dates Holidays Rosh Chodesh Memorial dates 7. "My dates" section We take this idea from the reference, but want to make it useful. The user should be able to save: birthday Jewish birthday yahrzeit other important dates What the bot should do: store these dates remind about them allow setting notifications Buttons: Add date My dates Reminders Delete date 8. "A-Yom Yom for today" section What should be included: text for today convenient beautiful display ability to view the previous / next day share button Buttons: Today Yesterday Tomorrow Share 9. "Synagogue services" section This needs practical navigation. What can be included: registration for a lesson registration for Shabbat registration for an event ask a question volunteering charity programs other services / directions of the synagogue 10. "Contacts" section Should include: address phone Telegram Instagram YouTube email ways to contact us if necessary, geolocation Buttons: Call Write Open address Instagram Telegram YouTube 11. "Donate" section It needs to be done neatly and clearly. What should be included: donate button payment methods details / link brief explanation of what the funds are for contact for donation questions 12. "Settings" section The user should be able to configure: language daily notifications notification time Shabbat reminders holiday reminders reminders for personal dates Buttons: Language Notifications Shabbat Holidays My dates Enable / disable mailing 13. Daily mailing We need the bot to send people relevant information every day: what prayers are today what time they take place what events we have in the synagogue today what important dates and events are in the Jewish world today if relevant — time for candles / end of Shabbat That is, a person opens the bot in the morning or receives a message and immediately understands the picture of the day. 14. Registrations and sign-ups Through the bot, there should be an option to register for: Shabbat lessons events meetings other activities Logic: a person presses a button leaves their name phone / username if necessary, additional data the application goes to the administrator / to a table / to CRM 15. Admin section It is important for us that the bot is easy to manage. The admin should be able to: update the prayer schedule add and edit events change texts launch mailings see registrations and applications change contacts and links It is important that this is really convenient for maintenance, not too complicated. 16. Support and development At the first stage, it is not necessary to do everything at once; a strong first version can be launched, and then supplemented in the process. But it is important to immediately foresee: the possibility of expansion support and maintenance of the bot after launch bug fixes improvements during use 17. What is important in the end We need a bot that will become a mini-application for our synagogue and help a person navigate conveniently: what is today what prayers what events what will happen on Shabbat how to register how to contact where to view the Jewish schedule what is happening in our synagogue and in the Jewish world If you see how to make the structure, buttons, design, and logic better than in the reference bot, that is a plus. We need not a clone, but a stronger, more convenient, and modern version. https://www.hebcal.com/home/developer-apis Chabad.org
Development of a Telegram bot: a closed platform-marketplace for experts I am looking for a developer (or a small team) to create a Telegram bot — a closed platform that connects verified experts and clients for solving professional tasks. The model is similar to a service marketplace with a supervising administrator, rather than a fully automated service. What is ready: A detailed technical specification (30+ pages) — user roles, step-by-step UX flows with button texts, status models for Requests/Cases, data model, payment status model, admin panel. Key functionality: - Two user roles (client / expert) with the possibility of combination - Verification of experts through the administrator (without automatic decision approval) - Selection and moderation of requests by the curator - Internal communication space within the bot (without disclosing contacts between parties) - Payment status model: escrow, confirmation of funds receipt, payments - Referral system with bonuses - Administrative panel with extended access rights Expected stack: at the discretion of the developer (Python/Node.js), the main thing is — experience with Telegram Bot API, working with states (FSM), databases, and payment integrations. Collaboration format: work based on the ready technical specification, discussion of deadlines and budget after reviewing the document. What to send: examples of implemented Telegram bots (preferably — with complex state logic or payments), an estimated timeline and cost.
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.