Bug fixes for the parsing Telegram bot for OLX / Urgent / Fast payment

A small project needs to be implemented for selling digital and physical products. What needs to be done: Develop a simple modern landing page for selling 3 products: PDF version; physical kit; paid Telegram subscription. Connect payment through WayForPay. Integrate orders with KeyCRM: transfer of customer data; creation of orders in KeyCRM; possibility of further automation. Develop a Telegram bot for managing subscriptions: automatic access issuance after payment; subscription activity check; subscription renewal; automatic access removal after payment completion; user administration through a simple panel or bot commands. It would be a plus: experience with WayForPay; experience integrating with KeyCRM; experience creating Telegram bots and paid subscriptions. Please specify immediately: exact cost; implementation timeline; examples of similar projects.

We need a chatbot with AI in Telegram for a webcam studio. The only task of the bot is to find suitable information in the studio's knowledge base and pass it to the models. It should not give its own advice or recommendations. If there is no suitable information in the knowledge base, it should direct the model to its curator. We have already assembled a bot on the suvvy.ai platform, and it generally works correctly. However, since we dealt with everything ourselves without specialists in this area, there are questions. We are currently looking for a specialist who could provide consultation/audit on this topic. The questions are approximately as follows: 1. We need a specialist to look at our settings and tell us if the cost of the bot's work is normal for us, or if it can be optimized (on this or another platform) to make the response prices lower? 2. How should we properly format the knowledge base for the bot? On Savvy, there is an option to add entries in the "question-answer" format or upload entire documents. It is important for us to clearly understand what information to upload in what format to the knowledge base so that the bot works as efficiently as possible, while also maintaining optimal response prices. There are also some minor clarifying questions about various functions, but these 2 are the most fundamental and essential) We are eagerly awaiting proposals regarding the cost and format of the consultation

We are a large logistics company with our own exports. We have a large fleet of vehicles and we constantly send our own vehicles for export to European countries.Description Website: https://echerha.gov.ua/ On this website, we place our vehicles in an electronic queue for crossing the state border. During registration, the following data must be entered: driver's first and last name; foreign passport number; email address; logistics phone number for notifications; type of vehicle (cargo); manufacturer's name of the vehicle; state registration number of the tractor; state registration number of the trailer; customs declaration number. A specific day and time for crossing the border is predetermined for each vehicle. For example, the vehicle must pass through the "Rava-Ruska" checkpoint on Monday at 10:00.Our Problem - The queue on the website https://echerha.gov.ua/ moves unpredictably. - For example, today is Friday, and the vehicle must cross the border on Monday at 10:00. - We do not know exactly when the queue will start moving. This can happen on Friday evening, at any time on Saturday or Sunday, early in the morning, during the day, or late at night. - When the queue starts moving, it is immediately visible on the website. Sometimes, within just a few minutes, it can move from Friday to Monday or even to Tuesday. - Because of this, logistics personnel are forced to constantly monitor the mobile application or website to not miss the moment when the queue reaches the required date and time. If this moment is missed, we physically cannot place the vehicle in the queue for the needed time slot.Task - After entering the vehicle data (for example, into a table or another interface, depending on the programmer's implementation), the system should automatically track the movement of the queue. - When the queue reaches the predetermined date and time, the system should automatically fill in the necessary data and place the vehicle in the queue without the involvement of the logistics personnel.

A Telegram bot is needed to accept orders for work. I am engaged in the restoration of slopes and repairs. I need a bot that my clients (window companies) will fill out, and I will receive notifications with complete information about the order. What data do I need from clients: 1. Company name (preferably automatically by phone number) 2. Address of the object 3. Phone and name of the customer 4. What we are making the slopes from (drywall, plastic, sandwich) 5. What type of building (panel building - slope up to 270mm, brick building - slope 280-400mm, brick building - slope over 400mm, other. Or specify the depth of the windowsill... 6. Window sizes and their quantity (there may be several different windows at one object), can be written manually or add image files with quantity and sizes. 7. Additional services: Painting of external slopes, m. linear. Sealing of joints (without painting), m. linear. Sealing of joints with painting, m. linear. Puttying of external slopes (without painting), m. linear. Puttying of external slopes with painting, m. linear. Puttying of external slopes with perforation and painting, m. linear. Warm external slopes made of polystyrene with painting, m. linear. Warm external slopes made of polystyrene with a border and painting, m. linear. Restoration of thresholds Other work (description) 8. Who pays for the order and how

Looking for a developer to create an AI assistant based on OpenAI GPT-5.5 with integration of Tourvisor API (Tour Search).What needs to be implementedBackend Preferably: Python (FastAPI) or Node.js The backend must have a REST API for integration with external services.Integration with OpenAI It is necessary to use OpenAI API (GPT-5.5). The AI must: conduct a dialogue with the client; remember the conversation history; automatically determine the language (Russian/Kazakh); respond as a travel agency manager; use a system prompt and knowledge base.Integration with Tourvisor At the first stage, only: API "Tour Search" After receiving data from the client, the backend should call the Tourvisor API and get real offers. The architecture should allow for subsequent connection: API "Hot Tours"; API "Hotel Descriptions"; without significant reworking of the project.Logic of operation The AI must independently conduct the dialogue. For example: Client: I want to go to Turkey The AI clarifies: departure city; dates; number of adults; number of children; ages of children; budget; wishes. After receiving the necessary data, the backend makes a request to the Tourvisor API. The results obtained are passed to GPT to form a nice response to the client.Important requirements The AI must not: make up prices; make up availability; make up tours. Use only information obtained from the Tourvisor API.Function Calling (Tools) is desirable It is necessary to implement separate functions: searchTours() In the future, the following will be added: searchHotTours() getHotelInfo()Admin panel A simple web panel is needed where you can: change the system prompt; upload/change the knowledge base; view conversation history; view logs and errors.Technologies Python FastAPI (preferably) Docker PostgreSQL Swagger/OpenAPIWhat should be delivered upon completion source code of the project; installation instructions; Docker configuration; API documentation; assistance with the first launch.Will be an advantage experience with OpenAI API; experience integrating with Tourvisor API; experience creating AI assistants for WhatsApp, Telegram, or other messengers.Additional wish The project should be written modularly so that in the future it can be connected without reworking: WhatsApp (Talk Me or another service); Telegram; Instagram Direct; company website. Important: provide for the possibility of connecting the API "Hot Tours" and "Hotel Descriptions" in the future without changing the main logic of the application.