Budget: 4500 UAH Deadline: 3 days
Hello.
I have experience with SendPulse. I am ready to take it on. Write to me, we will discuss.
Budget: 2000 UAH Deadline: 7 days
Hello, I worked on a project for automating Telegram bots with CRM integration for an educational platform with 500+ students, where I set up a reliable mailing system through SendPulse with a 99% message delivery rate.
Andrii, I'm curious - do you use webhook for data synchronization between SendPulse and CRM, or do you rely only on automatic triggers? This could be key to understanding gaps in the connection.
I suggest we get in touch, I will consult you for free on the technical side and we will create a development plan + I will tell you about my team!
Budget: 6000 UAH Deadline: 3 days
Hello! I am an individual developer with 4 years of experience in automation (n8n, API) and Telegram bots, so I will solve the issue of breaking the connection in SendPulse by implementing Deep Linking (start parameter) for instant client identification by ID from CRM. I will set up a reliable synchronization mechanism through Webhooks and re-initiate the contact request, ensuring the delivery of newsletters even without the initial nickname; I work through a sole proprietorship and am ready to conduct a technical audit of your system today. My works: https://3magency.co/, https://jk-solution.com.ua/, https://farfieworldwide.com/, Behance.
Budget: 7000 UAH Deadline: 7 days
Hello! We are a small team that has been engaged in web development and business process automation for over 4 years, so we are ready to implement a stable logic connection between Telegram and CRM for you, which will not depend on the human factor. We will implement an alternative authorization method through parameterized Start buttons, set up automatic initiation of phone number requests for "problematic" clients through filters in SendPulse, and ensure guaranteed delivery of reminders. Our experience of over 4 years allows us to integrate number verification through API and create a reliable bridge between services so that each user is correctly identified by their unique Telegram ID. Be sure to check our work examples that demonstrate a high level of technical preparation: freshagro.com.ua, farfieworldwide.com, rivnekolo.com.
Budget: 12000 UAH Deadline: 5 days
Good day! My colleague and I have been professionally engaged in the technical design of chatbots and data synchronization between marketing platforms and CRM systems for over 4 years, so we will help you set up a reliable user identification mechanism. We will implement a frontend audit of your funnel, replace the standard entry with a link embedded with a CRM ID (ref parameter), which will ensure instant linking of the profile to the deal regardless of the "Share contact" button. We will ensure technical excellence in execution, set up automatic subscription status checks, and correct filling of system fields in SendPulse. Our 4 years of experience is confirmed by successful projects drkukharevich.rivne.ua, crave-agency.com.ua, jk-solution.com.ua, where we have already solved issues of connection loss in complex integrations.
Budget: 10000 UAH Deadline: 3 days
Hello! My partner (designer + full-stack) and I have been specializing for over 4 years in developing complex automations and fixing architectural errors in the connections between SendPulse, Telegram, and CRM, so we will professionally solve the problem of delivering your messages. We will develop the identification architecture through Deep Linking (parameter start=ID), which will allow for a technically flawless connection between the client and the CRM without the mandatory sharing of the phone number, using a unique hash identifier. Our experience of over 4 years allows us to configure the correct transmission of the phone variables in SendPulse and implement a "soft" re-binding mechanism through custom webhooks, so that the automation works even without a nickname; take a look at our work from the perspective of technical accuracy: hyperfi.tech, espressolab.com.ua, hudi.com.ua.
Budget: 1111 UAH Deadline: 1 day
Andriy, greetings!
I specialize in the implementation, configuration, and technical support of CRM systems for over 6 years, as well as performing integrations with websites and other services.
I have experience working with Sendpulse.
I have reviewed your task, but I will be able to provide the exact cost and timeline after clarifying a few details about the project.
I guarantee quality implementation and stable operation of the system.
Budget: 1000 UAH Deadline: 2 days
Good day
If the problem is only with a few clients, it needs to be addressed.
The issue could have been that the number in the CRM was not in the correct format, or the user blocked the bot. In that case, the problem is not with the mechanism but with the clients.
(Blocking the bot instead of unsubscribing is a very common occurrence)
To inform clients 100%, messages can be duplicated by sending emails.
Budget: 2000 UAH Deadline: 1 day
Hello!!!
I am ready to complete the task, I have extensive experience.
Feel free to contact me.
Budget: 2000 UAH Deadline: 3 days
Hello! I am ready to complete your task, I have experience working on similar projects.
- Projects -
- Rating -
- Rating 496
Budget: 10000 UAH Deadline: 1 day
✋ Hello! We are the IT company dZENcode.
We can help with setting up the integration of a Telegram bot, SendPulse, and CRM for this task.
Which CRM is the integration currently set up with?
Are there examples of their cards and SendPulse connections for problematic clients?
We work in iterations, rates starting from 750 UAH/hour.
You can find detailed information about our services and rates on our website: Freelancehunt
Take a look – we will discuss the details of the work further, write when you are ready.
The final cost is determined only after clarifying the scope and requirements.
___________________
Best regards,
Manager of dZENcode
Our strengths:
💎 10+ years providing IT services: Outsourcing, Outstaffing
🔥 90+ in-house specialists
🚀 Projects "from scratch" and for support
⚙️ SLA and post-production support
✅ Contract with the company, guaranteed results!
🔥 250+ public reviews since 2015.
Budget: 3500 UAH Deadline: 5 days
Good day!
The task is clear. Here the problem is likely not in the newsletters themselves, but in the logic of user identification between Telegram, SendPulse, and CRM.
What I see from the description:
— if the user did not share their contact through the Telegram button, the connection may remain incomplete;
— in Telegram, the bot does not automatically receive the phone number; it can only be obtained if the user themselves presses the button to share the contact in a private chat. This is the standard logic of the Telegram Bot API. (Telegram)
— in SendPulse, the bot variables are stored separately; they need to be correctly mapped in the CRM, and for this, usually either the phone is stored in a variable or a connection is made through API/ID/tag/custom parameter. SendPulse supports variables, user input, and API requests for data transfer and synchronization with external systems. (SendPulse)
What I would suggest implementing:
1. An audit of the current connection logic SendPulse ↔ CRM ↔ Telegram.
2. A check on how the phone is currently stored and which variables are actually filled for "problematic" users.
3. A reliable re-binding mechanism:
— not only through Start,
— but through a separate scenario "Confirm Number" at any moment.
4. Alternative identification:
— through start parameter,
— CRM ID / internal user ID,
— or API connection if the number is not yet confirmed.
5. Logic such that even if the contact was not shared immediately, the user can be reconnected later without losing automated communications.
As a result, a more stable scheme can be built where the main key will not only be the phone but also the Telegram user ID / external CRM ID, and the confirmation of the number will become a separate repeatable step.
I can:
— analyze the current scenario;
— find where the connection is breaking;
— suggest the correct architecture;
— and, if necessary, implement the re-binding and backup identification mechanism.
If relevant, I can start with a brief technical audit of your current logic and then propose a precise solution.
I also wish you a good day!!)
Budget: 3500 UAH Deadline: 5 days
Good day!
I carefully read the description — the problem is likely that the user is not going through the correct connection between Telegram and CRM (especially if the number already exists in the CRM but is not confirmed through Telegram).
Such situations often arise if:
— the user did not click "Share contact"
— the connection is built only through the number, and the Telegram ID is not saved
— there is no mechanism for re-linking
I have already worked with similar logic (Telegram + automation + user processing) and understand how to fix this.
What can be done:
— add an alternative linking (through start parameters or ID)
— implement re-linking without dependence on /start
— check how the phone is transmitted and stored in SendPulse
— create a more reliable user identification logic
I can quickly understand the current implementation and propose a specific solution.
Proposals are currently absent
Current freelance projects in the category Bot Development
Is it possible to write code that helps catch the moment of a strong drop or rise? I want to implement such a strategy. A bot that will provide the necessary entry for the bet up or down when it will really be IT. I will attach what I mean. In general, I am looking for a specialist to create a pocket option trading bot.
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.