Leads from messengers: forms inside WhatsApp, VK into amoCRM and gamification in Telegram

In October HighLevel released three things for WhatsApp and one for social networks, Telfin linked VK with amoCRM and Bitrix24, and Cossa took apart why game mechanics in Telegram channels don't keep people around. The common thread: a lead is born in a chat more and more often, and the question is where it goes next and who sees it. I've run telephony and the CRM link at a PDR company in the US since 2021 and built AmoCRM integrations for a car rental in South Africa, so I look at what happens after the button is pressed.

What came out

On October 26, HighLevel added forms through WhatsApp Flows: the form opens inside the conversation, with no link and no browser. It takes an existing form, drops the fields WhatsApp Flows can't display at build time, and the answers land in Forms, under Submissions, and attach themselves to the contact.

The same day brought carousels for WhatsApp: 2 to 10 cards in one message, each with its own image and up to two buttons. The important line: WhatsApp counts it as one marketing message, so ten products cost the same as one send. A tap on a quick reply button goes to a webhook, and you can see which product caught the eye.

Earlier, on October 15, HighLevel rebuilt its WhatsApp template builder: a phone preview while you edit and, most importantly, dynamic media. Before, every invoice or ticket needed its own template and its own Meta approval; now the header takes a value from a contact field, and one template sends each person their own document. The condition: the link has to be publicly reachable by Meta; private Drive links produce an error, and the error shows right away.

Social Comments in Conversations, also October 26: comments under posts published through Social Planner on Facebook, Instagram and TikTok land in the shared inbox next to SMS and email. Every commenter becomes a contact, you can reply publicly or by direct message, and comments with words like “price” or “how much” move to the top.

On the Russian market: on October 20, CNews reported that Telfin linked VK with amoCRM and Bitrix24. I only have the announcement from the page, so I won't go into the mechanics.

And a piece from the other end of the funnel. Mikhail Lobas of BotBox on Cossa, October 23, took apart why gamification in Telegram channels almost always fails. In niche channels, on average 3 to 10% of the audience reacts to a post. A giveaway through a randomizer bot gives a spike until the winner is announced, then those who came for the prize unsubscribe. A points leaderboard holds longer but breaks on two mistakes: nobody works out the points economy in advance, and there's no daily cap per action, after which subscribers show up with 50 comments in a row.

Why this matters to a business

Take a service company that repairs home appliances. A customer writes on WhatsApp: “my washing machine broke.” Before, the manager sent a link to a form, the customer opened a browser, got distracted, and the conversation went cold. A form inside the chat removes that step: the machine model, the address and a convenient time arrive with the request. But if the answers sit in Submissions while the technicians work in their own spreadsheet, the request gets copied over by hand again.

The takeaway: the channel the lead comes from matters less than where it lands and who is responsible for it. A WhatsApp form, an Instagram comment and a call to the IVR should arrive in one place.

Gamification follows the same principle. Points in a manufacturing company's Telegram channel will give nothing if there's no next action behind them: a sample request or a quote request.

How I do it

At the PDR company in the US, the lead's path is this: the website, forms and calls to the IVR land in the database and the super app, the salesperson sees the lead in the app, and calls and messages the customer from there. The customer gets push and SMS notifications from the portal, in English and Spanish. A call to the IVR creates the lead in the CRM on its own and attaches the recording and the AI breakdown of the conversation. GoHighLevel went from the main CRM to a supporting one; the center of the system is now the super app. So I read HighLevel's changelog with one question in mind: which of this touches our integration.

For AmoCRM I have a project design for a Telegram and WhatsApp bot with the conversation kept in the CRM: AmoCRM, a chatbot and messaging. It's a design; I don't describe any rollout results for it. The live AmoCRM project is a different one: in October 2024 a rental in Cape Town brought me in to integrate AmoCRM with Google Sheets, and over 2025 that grew into a system with a full-cycle booking site and an internal app. Deals stayed in AmoCRM, the complex logic moved to our own server.

What I would do

Before turning on WhatsApp forms, decide where the answer goes, the CRM or the technicians' app, and who is responsible for the lead in the first hours.

For dynamic media, check that the links to invoices and documents are reachable by Meta. At the PDR company my documents are assembled into PDFs on our own server, and before a template like that I would decide which of them can be opened by a public link.

Let social comments into the shared inbox only with a rule about who answers them; otherwise the inbox grows and the leads from it don't.

Launch points and giveaways in Telegram after the channel has an action that leads to a request, and work out the points economy beforehand, as Lobas advises.

How to connect documents, the CRM and tasks without duplicates, I covered in the article How to reliably connect documents, CRM and tasks. Directions: chatbots, CRM integrations and AmoCRM integration. Cases: technical partner to a PDR company and bot design for AmoCRM. Other reviews: GoHighLevel in October: what touches the integration and SMS with a tracked link and SIM swapping; earlier I wrote about when you need an internal system instead of running things in chats. If leads come from messengers and get lost on the way to the CRM, tell me which channels you have and where the requests should land: Discuss your task.