Budget: 168 EUR Deadline: 1 day
ready to help you out with this
have huge experience working in full stack
will send you previous work to make sure we match
Hello ) Are you a jack of all trades?
There is a Telegram bot that:
– works in a chat with the client
– maintains a checklist of tasks
– monitors deadlines
– if a task is not completed, writes in a separate working chat of the team until it is completed
Describe the architecture:
– where and how the project state is stored
– how tasks, statuses, deadlines are stored
– how the bot determines overdue tasks
– how repeated reminders are implemented
– what happens when the server is restarted
An answer like “through if / cron / just DB” without logic is not acceptable.
The client sends a message or a file.
Describe step by step:
how the bot understands what it is: text, document, confirmation
how the bot understands which task it relates to
how it is checked whether the document is suitable or not
what the bot does if the document:
– is suitable
– is not suitable
– lacks data
what the bot replies to the client in each case
An algorithm is needed, not code.
AI is used in the project.
Answer:
– for which tasks AI is used
– for which tasks AI should not be used
– how to prevent AI from changing business logic
– how to divide responsibility between code and AI
An answer like “AI will decide” is immediately unacceptable.
There is a task with the status WAITING_CLIENT.
The deadline has passed. The client is silent.
Describe:
– how the bot detects this
– how often the bot writes to the client
– how often the bot writes in the working chat
– how to stop reminders
– what messages look like to the client and the team
Logic and timing are needed.
In a month, a new process appears:
– different steps
– different documents
– different deadlines
What will you do to:
– not rewrite the code
– change the process through configuration
– add new checklists
Describe what is stored in the database and what is in the code.
Describe your real experience:
– have you made bots or services that control tasks
– were there deadlines and responsibilities
– what exactly did you implement
If you have no experience — just say so.
Suitable:
– a person thinks in states
– understands processes and deadlines
– separates code and AI
– explains with logic, not terms
Not suitable:
– short answers
– general words
– “we can try”
– focus only on code
– AI as magic
Answer point by point.
Without fluff.
Budget: 168 EUR Deadline: 1 day
ready to help you out with this
have huge experience working in full stack
will send you previous work to make sure we match
Budget: 168 EUR Deadline: 10 days
Here’s how I would implement it:
I store the state in PostgreSQL, where each project operates as a Finite State Machine. This means that a task cannot skip a stage or get stuck in uncertainty. Deadlines are tracked through task queues based on Celery or Redis: when a task is created, an event is immediately scheduled for the deadline time. If the server restarts, the data will not disappear because the queue has a persistence parameter for permanent storage, and the bot will pick up the work from the same second.
When processing incoming data, the bot first determines the type of content and context, checking what stage the client is currently at and what action they expect in the waiting status. Validation occurs in two levels: first, the code checks the technical parameters of the file, and then the AI assistant confirms the content, for example, whether it is indeed the required document. If everything is fine, the status changes automatically; if not, the bot explains the error without closing the task.
I use AI for intent classification, data recognition, and answering typical questions. It is prohibited from making independent decisions about changing business logic or statuses. The AI only returns a structured JSON with data, which the code validates against strict rules before any action.
Working with deadlines is automated through events in the queue. As soon as the time is up, the bot messages the client after an hour, and then once every six to eight hours to avoid spam filters. If there is no response for more than twelve hours, the bot automatically sends a notification to the team's work chat. Any activity from the client instantly changes the status in the database, which automatically deletes all scheduled reminders for that task.
To avoid rewriting code when new processes arise, I will move all the logic of steps, document types, and message texts into a JSON configuration in the database. The code will only retain a universal engine that reads these schemas. Thus, a new checklist or change of deadlines is implemented simply by updating a record in the database without the need to deploy new code.
Regarding experience, I have created Telegram bots in Python for generating presentations, which used the Google AI Studio token and Pexels, and a bot for generating dialogues based on AI; I have also created Android applications.
Budget: 168 EUR Deadline: 1 day
Good day! I am ready to complete this project and have extensive experience in developing various applications.
Budget: 168 EUR Deadline: 7 days
I need help figuring out how to connect Viber so that the business owner can track the conversations of the managers. I have an online spare parts store. I previously worked alone. In the spare parts field, people often write specifically in Viber. I have a large client base that writes in Viber. I need to come up with a way for clients to write to a familiar account while the manager responds. Starting next month, I plan to hire a sales manager, and I need help connecting Viber to some platform where I could track conversations with clients.
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.
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.