Home · Blog · What a bot can do for a Telegram channel: leads, lead magnet, segments

What a bot can do for a Telegram channel: leads, lead magnet, segments

· updated · Command CHBT · Telegram, Channels

A Telegram channel has one problem: it talks but doesn’t listen. A subscriber reads a post, wants to ask something or leave a request — and hits the comments, where requests drown, or the admin’s private messages, where nobody counts them. A bot closes this gap: the link in the post leads to a private conversation where the bot gives the material, asks for a contact, answers questions and marks which post the person came from. Below — what exactly the CHBT bot can do for a channel, how the deep link setup works, five working schemes and an honest list of what the bot doesn’t do: posting and comment moderation.

What kind of bots do channels have and which one - CHBT

The word “channel bot” combines tools of different natures. Some work within the channel as an administrator, some work in private with a subscriber. The difference is fundamental: the former manage the publication, the latter talk to people.

TaskWhere worksDoes CHBT
Delayed posting, buttons below postsinside the channel, admin botyes — the “Editorial” section
Moderation of comments, antispamin group discussionsyes — “Editorial”: a review queue
View statistics and subscriptionsAPI channelno
Issuing a lead magnet for contactpersonal botda
Accepting applications from postpersonal botda
Answers to questions subscriberspersonal botda
Audience segmentation by interestspersonal botda
Distribution to those who opened botpersonal botda

The CHBT conversational bot belongs to the second group: its place is a private conversation the subscriber opens via a link from a post. Publishing posts with buttons, scheduling and comments under posts are handled by the separate “Editorial” section — for it, the bot is added as a channel admin.

The link “post → deep link → PM”: how it works

The basis of all the schemes below is deeplink: a link of the form https://t.me/имя_бота?start=payload. The subscriber clicks it in the post, Telegram opens a chat with the bot and the “Start” button, and after clicking the bot receives not just /start, but /start with the specified payload. This value in CHBT triggers the trigger “Deep link” — a separate entry into the script, bypassing the general greeting.

Rules for payload sets Telegram: up to 64 characters, only Latin letters, numbers, hyphens and underscores. Cyrillic alphabet and spaces cannot be used. Convenient naming system - topic plus date or post number: checklist_0911, promo_sept, post_142. The name should be clear to you in a month when you look at the tags in “Contacts”.

How the link gets into the post. Text link - always: select a word in the text of the post and paste the URL, works in any channel. A button under the post - only if you publish through a bot scheduler that can add inline buttons; CHBT does not put such buttons in the channel, but you can insert a deep link into the scheduler button. For channel stories and channel descriptions - the same link.

An important consequence: the bot cannot write to the channel subscriber first. Until a person clicks “Start”, the bot does not exist - this is a limitation of Telegram, not the constructor. Therefore, each diagram below begins with the subscriber action: follow the link.

Scheme 1. Lead magnet for contact

The most common task of the channel: the post promises a checklist, a template, a recording of the broadcast - and it should be given not to everyone, but to those who leave contact. Template “Issuing a lead magnet” in CHBT consists of three steps - offer, contact, link to the material; Add a tag to the post yourself.

  1. Trigger "Deeplink" with payload checklist_0911. The greeting with /start is not shown - the person already knows why he came.
  2. "Message": “The checklist from the post about the launch of the channel is here. Where can I send the PDF version and updates?” with buttons “Email” and “No need, give me a link.”
  3. “Data collection” → E-mail with format checking - only in the “E-mail” branch. Those who chose the second button are given the material immediately: you already have a contact in Telegram, and the mandatory collection of mail is an extra step, during which some people will leave without the material.
  4. "Message" with link to a file in the cloud or to a website page. Disclaimer: in Telegram, the CHBT bot sends text and buttons; you cannot attach a PDF directly to the chat - the material lives on the link.
  5. “Action” → Add tag magnet-checklist.

After a week in the section “Contacts” This tag shows how many people took the material, how many left mail, and there is an export to CSV. About how a lead differs from a lead magnet and why qualification is needed - in marketer's dictionary using the example of one bot.

Scheme 2. Applications from the post: promotion, recruitment, recording

The post “we are opening enrollment for October”, “discount until Friday”, “three spots left” - and under it there is a link “Leave a request”. Without a bot, leads go to comments and the admin’s personal message, where they must be rewritten into a table manually.

The flow with the bot is as follows: “Deeplink” trigger with payload oct_group → “Message” with the essence of the offer and the “Sign up” button → "Data collection": name, then phone with format check → “Action” → tag zayavka-oct and Notify operator → “Message” with confirmation: “Thank you, {{name}}, we will call you back today before 18:00.”

The lead ends up in two places at once: a card in “Contacts” with a tag and a conversation with a tag in “Conversations”; to the owner - a letter by e-mail and push in the account. Deal on Kanban in the section «CRM» created by the same script - the “Transaction in CRM” action in the “Action” block immediately after collecting the phone, with a name from the variables and the starting stage; the manager just has to move the card through the stages. If leads are needed in an external system, add an "HTTP request" - POST with contact data and variables to your URL or Make/n8n.

One detail about order. Asking for a phone number in the first message after the transition is a mistake: the person has just left the channel feed and has not yet decided. First, the “Sign up” button as a confirmation of intention, then the name, then the phone number with an explanation of “where to call back.” The mechanics of checking phone and e-mail in the “Data Collection” block - asking again with your “Text in case of error” until the format matches - is the same as in any application flow.

Diagram 3. Answers to subscribers’ questions instead of the admin’s personal message

Over time, the channel administrator’s personal account turns into a help desk: “how much does it cost”, “when is the next stream”, “is there a recording of the broadcast”. The bot takes this if the channel description and pin contain the line “Questions for the bot @bot_name.”

Inside are triggers "Key word" with "contains" or regex mode: costs|price|how much, flow|set|start, recording|broadcast|video. Each one leads to a ready-made answer with a link. Everything that doesn't fit catches the trigger “Any message” → short “I pass the question to the author of the channel” → block “Operator”: the conversation goes into the inbox, the bot goes silent, the person answers from the office. The template “Autoresponder FAQ” from the catalog provides a template.

If there are a lot of standard questions and they are formulated freely, you can add an “AI agent” block to the Basic plan: the agent answers your knowledge base (product description, prices, schedule - in plain text) and passes it on to the operator when he is not sure. The agent's default response to models is one AI credit, more expensive on powerful models; in Basic 150 credits per month.

Scheme 4. Segmentation by posts: different payload - different tags

Here the bot does what the channel itself cannot do: it shows which of the subscribers are interested in what. Mechanics - each post has its own link with a unique payload, and in the script, the “Deep Link” trigger through the “Action” attaches a topic tag.

  • Post about launching a channel → ?start=topic_launch → tag launch.
  • Post about advertising → ?start=topic_ads → tag ads.
  • Post about monetization → ?start=topic_money → tag money.

There is no need for a separate script for each post. Three “Deeplink” triggers for three payloads - each does one “Action” with a tag and goes into the general part: on “Canvas” this is a connection into the same block, in complex schemes - “Subflow” with a common conversation. Then all three branches follow the same path: offer, contact, response. Only the input is duplicated, not the script.

What does it give? In “Contacts” there is a filter by tags and an answer to the question “what topic gathers people who are ready to start a conversation.” There are no counters for script blocks in CHBT, and “Analytics” shows incoming messages by day for 14 days and conversations for 30 days by channel - but not by post. Tags on deep links are a way to get statistics on posts without separate analytics. How to build a tagging system so that in six months you can figure it out - in the article "Tags as a segmentation system".

Scheme 5. Mailing to those who opened the bot

The post in the channel is seen by those who have entered the channel. A message from the bot comes as a notification in a personal message - it is opened more often. Therefore, a channel plus a bot are two ways to reach one audience, and the second works for broadcast announcements, recruitment deadline reminders, and personal offers.

Section “Mailmails” (Basic plan) sends a text with variables like {{name}} by audience selected by tags: for example, only those who came with topic_money, but did not leave a request. Delayed start by date and time, stop on the go, send one message through the queue, no faster than 20 per second - within Telegram limits. Statistics: sent and errors.

Three caveats. First: the newsletter goes only to those who opened the bot - not to all subscribers of the channel. The size of this database is the main reason to put a link to the bot in every post. Second: there are no media or buttons in the broadcasts - text and links. Third: delivery errors are mostly people blocking the bot; They should be removed from mailing tags rather than trying to reach them. Details about the queue and limits are on the page broadcasts via Telegram bot.

What the bot CHBT does not do for the channel

A list without softening — so you don’t plan for what won’t work.

  • The conversational bot doesn’t publish posts or reply in comments — the “Editorial” section does that. The bot picks up a request from a comment via a deep link under the post or a code word in private messages — see the article about comments in a Telegram channel.
  • Checks the subscription only if the bot is a channel admin. The “Subscription” rule in a “Condition” asks Telegram about subscribers; without admin rights there’s no answer, and the flow goes to the “Couldn’t check” branch.
  • Doesn’t send photos, videos or files in Telegram — only text and buttons. Materials go as links.
  • Doesn’t collect channel statistics: views, reach, unsubscribes belong to the channel API, not the bot’s.
  • Doesn’t message first people who haven’t opened the bot — a Telegram limitation.

The rest isn’t our area, and we won’t pretend otherwise.

Launching a channel: what to do on the first day

  1. Create a bot from @BotFather, connect to CHBT via “Channels” → “Connect Telegram”. The bot's name is with a reference to the channel so that the subscriber recognizes it in the list of chats.
  2. Take the template “Issuing a lead magnet” or “Collecting applications”, replace the texts, add a “Deep link” trigger with your payload.
  3. Put a link to the bot in the channel description and in the pin: “Materials and questions - @bot_name.”
  4. In your next post, provide a deep link with a unique payload and tag. After three days, look at “Contacts” by tag.
  5. Add a trigger “Any message” → “Operator” so that non-standard questions do not disappear.

All this is available on the Free plan with a limit of 30 conversations per month - just check the bunch on one post. Mailings, Canvas and AI agents - on Basic for 650 RUB per month per bot. The same flow works in Telegram, MAX and VKontakte from one project. Connect a bot to a channel →

More on the blog