Home · Blog · Transfer of subscribers from Instagram* to Telegram and MAX through a bot
Transfer of subscribers from Instagram* to Telegram and MAX through a bot
The social network account has subscribers, but no base: you cannot write to them yourself, you don’t know their contacts, and the reach of the post is decided by the algorithm. And it’s also impossible to sell there humanly: price and availability live in post captions and in manual correspondence. Overflow is the transfer of part of the audience to where you can both work and trade with it: to a bot in Telegram or MAX, which delivers what is promised, puts a tag, puts the person in “Contacts” and - if the catalog is connected - immediately responds with price and availability. Below is a working diagram of five nodes, assembled on CHBT: link in the header, deep link with payload, first 30 seconds in the bot, database markup and QR for offline. Plus texts for stories, metrics and five mistakes that reduce the translation of the audience to zero.
Overflow scheme and why a bot and not a channel
*Meta is recognized as an extremist organization and is banned in the Russian Federation.
The entire diagram is contained in one line: link in the header → deep link with payload → bot issues material and tags → person in “Contacts” → broadcasts and chains. Each node is one setting in CHBT or one action on the social network, and then we will go through them in order.
Why does the link lead to a bot and not to a Telegram channel, although the channel seems to be a natural “movement”? The channel has three disadvantages for overflow. A channel subscriber is not a contact: you don’t know who he is, you can’t write to him personally, and you can’t segment him. The channel does not provide feedback: the person has subscribed and that’s it, then it’s just coverage. And the channel does not answer questions: “how much does it cost” will remain unanswered until your post.
The bot does the opposite: each transition is a card in “Contacts” with the channel, date and source tag; everyone can ask a question using buttons and receive a segment; You can send a newsletter to everyone or start a chain with pauses. And the bot will give you a link to the channel itself - in the first message, if you also need the channel.
A disclaimer about the beginning of the funnel. CHBT does not connect Instagram* as a channel and does not automate correspondence on it - why this is so is explained separately in the article Instagram* for businesses from the Russian Federation. Here we take it for granted: the funnel begins with a click on the link, and everything before the click is your posts, stories and manual responses in direct messages.
Node 1. Link in the header: one, and it leads to the bot
In the profile header there is space for one link that is actually clicked. Multi-link services (“all our social networks on one page”) look neat, but they add a screen between a person and a bot, and some people get lost in this extra step. If the goal is an overflow, the link should lead directly to the bot.
Telegram or MAX? It's not fashion that decides, it's the audience. Many Instagram* subscribers already have Telegram, and the habit of opening bots there has been formed - so this is a reasonable default choice for the header. MAX should be the main link if you work with an audience that already communicates with you there: parents of students, residents of the area, clients of local services. In other cases, MAX is connected to the same project CHBT as a second channel, and the link to it lives in stories and on offline media, and not in the header. What to consider when choosing, analyzed in comparison MAX or Telegram for bot.
Text below the link. The description field next to the link is the only place where you explain why to click. “Link to bot” does not work; “Checklist “10 repair errors” - in the bot via the link” works. Formula: what a person will receive + where (“in the bot”, “in Telegram”). One sentence.
Update the campaign link. When you launch a new lead magnet or promotion, change not the bot address itself, but the parameter after it - this way the sources will be kept track of, and the script will understand what exactly the person was promised. The next node is about this.
Node 2. Deep link with payload: one bot, many inputs
Deep link - a link to a bot with a parameter. For Telegram it looks like this: https://t.me/vash_bot?start=insta_bio. The person clicks, the bot opens, and along with the start command the parameter arrives in CHBT insta_bio. In the script, it is caught by the “Deep Link” trigger: you specify payload, and the branch is launched only for those who came via this link.
The point is not in technology, but in accounting. Create a separate payload for each entry point, and in a month “Contacts” will answer what works and what doesn’t.
| Entry point | Payload | Tag in CHBT | What does the bot give out? |
|---|---|---|---|
| Link in the header | insta_bio | src-insta-bio | Main lead magnet |
| Stories with promotion | insta_st_sep | src-insta-stories | Promo code September |
| Reels about the service | insta_reels_1 | src-insta-reels | Price for this service |
| QR on the packaging | offline_pack | src-offline | Instructions and request for feedback |
In the script, these are several “Deep Link” triggers, each leading to its own short branch: “Message” with the promised material → “Action” → “Add tag” → and then all the branches converge into a common block with a segmenter question. There is no need to duplicate the entire script for each payload.
AT MAX the link to the bot from the MAX account for business also accepts a start parameter - when opened, the platform transmits it in the launch event, and the same “Deep Link” trigger fires with the same payload. One script for both channels; Only the link addresses differ.
If a person opened a bot without a parameter - found it by name or came from someone else's repost - the usual trigger “Command /start” will work. This thread also needs to be decorated: greeting, buttons, tag src-direct. Empty /start is the most common hole in overflows.
Node 3. First 30 seconds in the bot
The person clicked the link because he was promised something. The first message must fulfill this promise - immediately, without “subscribe first” and without a questionnaire. The following is the order.
- Issue. “Message”: “Keep the checklist “10 repair mistakes”: link. Save it - it will come in handy at the estimate stage.” An important detail: CHBT sends text and buttons to Telegram and MAX, but not files, so the material lives via a link - on a disk, in a note, on a website page - and a short checklist can be entered directly into the text of the message. Template “Issuing a lead magnet” has already been assembled under this logic: contact in exchange for material.
- Source tag. “Action” → “Add tag”
src-insta-bio. Silently, a person does not see this. - One question with buttons. “Message”: “To send only useful things, you now: [Planning repairs] [Already in progress] [Looking for myself].” Each button is “Add Tag” with a segment. One question, not three: with each subsequent one, some people leave.
- Contact - not now. They ask for a phone number when they give something more for it: a calculation, a consultation, an appointment. In the first 30 seconds you already have a contact in the messenger, and that's enough. Place the “Data collection” block with format checking in the “I want calculation” branch, and not in the input.
- If you are selling a product, show the product. A connected catalog (uploading a store via a link or a price file) turns the bot from a PDF distributor into a seller: when asked “how much does it cost”, it answers with the price and availability from your upload, and not “write me in a personal message.” The AI seller answers this way - from the Basic plan; products for it are taken from the store upload, file or using the Wildberries seller key, and the site’s catalog is marked “not verified” in the account before the first download. This is the main reason to take people away from the social network: there is nothing to trade there, but here there is something to trade.
- Where next? The last message is not a dead end: the buttons “Sign up”, “Ask a question” (→ block “Operator”), “Our channel” (link). A person who has nowhere to click closes the bot and forgets about it.
Formulas for the first message for different tasks - issuing, recording, support - are discussed separately in the article bot's first message; One thing is important here: what was promised in the first paragraph.
Node 4. Base: tags, broadcasts, chains
After the third node, each person transferred is a card in the “Contacts” section: name from the messenger, channel (Telegram or MAX), date, source and segment tags. What to do about it:
- Filter by tags in “Contacts” answers the questions “how many came from stories in a week” and “how many of them are planning repairs.” Export to CSV - with one button, if you need to calculate it in a table or give it to the manager.
- “Mailmails” (Basic plan, 650 ₽ per bot per month): text with substitution {{name}}, audience by tag, delayed launch. There are no buttons or pictures in the newsletters - put the link in the text. The message goes to the messenger where the contact came from, so the Telegram and MAX audiences each receive it.
- Reheating chain - not through broadcasts, but with a script: after publishing the material, “Pause” for two days → “Condition” by tag (didn’t sign up?) → “Message” with the next useful step → another pause → offer. This is a car funnel, only without the mysticism; mechanics with blocks are discussed in the article about trigger chains in the bot.
The main rule of marking is that tags are set by the script, not by a person. Source, segment, key actions (“received-material”, “requested-calculation”, “signed up”) - all with the “Add tag” action in the required blocks. Then the database is marked from the first day and does not require revision. How to build a tagging system so that in a year you can figure it out - in the article about tags as a segmentation system.
What to write in stories and reels to get clicks
The scheme only works as often as you remind it. The link in the header gives a smooth background; splashes - from stories and reels. Three formulas that don't look like bot advertising.
- Problem → material → where to get it. “Three errors in the estimate that cost 100 thousand. I put it into a checklist - it’s in the bot, the link is below.” Not “subscribe to the bot”, but “take the checklist”.
- Answer to the question from the direct message. “You ask how much it costs. The price list with examples is in the bot, and it will calculate based on your footage.” The second sentence is true only if you have a branch in your script with buttons for footage; promise what the bot does.
- The shortage is fair. “Windows for October: four left. Sign up in the bot." Scarcity works when it is real; a fictional one kills trust in two stories.
Posting rules:
- One story - one link - one payload. The sticker link leads to a deep link with the parameter of this series of stories, and not to the “general” address. Otherwise, you won't know which series worked.
- Locked One story with an explanation of “what the bot gives” - to the topic, first. People who come from recommendations watch what is relevant, not the feed.
- Rhythm. Reminder about the bot - once every 3-4 days, each time with a new reason. Daily “go to bot” unsubscribes.
- Direct manually. For those who write in direct messages, a person answers, but the answer ends with a link to a bot with payload
insta_direct: “Details and recording are here.” This is how even manual correspondence replenishes the database.
If you talk about the bot in the caption to the reels, the link there is not clickable - write “link in the header” and keep the current deep link in the header.
QR for offline: same bot, different payload
A business with a physical point or delivery has a second stream of people - those who hold your product, receipt or business card in their hands. They should also be led to the same bot, only via a QR code.
In CHBT there is a “QR campaigns” section for this: you specify a payload, and the service generates a QR code with a link to the project’s Telegram bot with this parameter. The flow is the same “Deep Link” triggers as for stories, only the tags are different: src-offline-pack for the package insert, src-offline-kassa for a sign at the cash register, src-offline-card for a business card. For the MAX bot, the “QR campaigns” section does not build a link yet - take the bot link with the parameter from the MAX for business account and generate the code using an external generator; nothing changes on the script side.
What should be next to the QR code: one phrase about the benefit. “Care instructions and warranty - via QR” on the insert; “Appointment reminder will come here” at the counter; “Discount for the second visit - in the bot” on the business card. Bare QR without a signature is scanned by only a few.
For marketplaces, the scheme expands and becomes the main one. The seller on Wildberries or Ozon does not know the buyer: there is no contact, the review appears without warning, and you cannot correspond within the site - not a single platform has marketplace chats in CHBT, and we do not promise this. Therefore, the buyer is brought into their channel using exactly the same technique: QR in the package insert, template “Buyer bot” — support, guarantee, instructions and request for feedback, contact and transaction in CRM. This mechanic has a common basis with transferring audiences from social networks: the same “Contacts” of one project.
In both cases, the meaning is the same: to take a person to a place where he can be sold. On the social network and on the storefront, you do not own either the contact or the conversation; in your bot - you own both, and if the catalog is connected, the bot also names the price and availability itself. How the catalog is connected and what exactly is read from the sites using the seller’s key - on the page integrations page.
How to measure overflow
There are no counters for script blocks in CHBT, and the overflow analytics is based on three things: tags, a dashboard and dates.
- Transitions by sources. “Contacts” → filter by tag
src-insta-bio,src-insta-storiesetc. The number of cards is the transitions that reached the bot. Watch it once a week, write it down in a table: dynamics are more important than absolute numbers. - Conversations across channels. In the “Analytics” section, the “By Channels” block shows conversations for 30 days separately for Telegram and MAX - this way you can see where people are actually going if there are links to both.
- Depth. The ratio of the number of contacts with the action tag (“requested-calculation”, “signed up”) to the number with the source tag. If 200 people came from stories and 6 asked for a calculation, that’s 3%; write down this number and compare the following stories with it. If 0, the problem is in the third node, not in the story.
- Share with phone. Upload “Contacts” to CSV and count in the table which part of the cards has a full phone number. Shows whether the thread with "Data Collection" is working and whether you are asking for contact too early.
In order not to be upset in vain: a small part of the audience switches from viewing stories to the bot, not all of those who switched answer the segmenter question, and the phone leaves even less - the less you offer for it. Compare your weeks with each other, and not with other people’s “norms”: even a small marked database is already an audience for segmented broadcasts.
Five mistakes that reset the overflow
- The link leads to the channel, not to the bot. Channel subscribers are not a base. If you want a channel, let the bot give you a link to it after the material.
- Questionnaire before issuance. “Leave your phone number and we will send you a checklist” - many people leave at this step. First the promise, then the question, the contact - in exchange for something more.
- One payload for everything. After a month, you don't know what worked and you keep doing everything. The minimum is separate parameters for the header, story and offline.
- Empty /start. The person came without a parameter, and the bot is silent or responds with “unknown command.” The “Command /start” branch should be as thoughtful as deep links.
- Bot dead end. The material was issued, and then nothing: no buttons, no questions, no operator. The person closes the conversation, and you have no next reason to write to him - except for the mailing, which without segmentation will be spam.
The entire scheme - link, deep links, search results, tags, QR - is assembled in one evening: the channel is connected using a token on the page of the Telegram bot, the “Issue Lead Magnet” template provides a ready-made skeleton, and the Free plan is enough for the first 30 conversations to see transitions from the header. What decides next is not the tool, but the regularity of the stories. Create a bot to transfer subscribers →
Telegram chatbotChatbot MAXTemplate “Issuing a lead magnet”Instagram* for businesses from the Russian Federation: why don’t we connect?Tags as a segmentation system