Telegram Bot Funnel With Deep-Link Attribution

The deep link is the product: A Telegram bot cannot message anyone who has not pressed start first, which means there is no cold outreach to design and the entire funnel lives upstream of the bot. The mechanism is the deep link: t.me/yourbot?start=payload, where the payload carries up to sixty-four base64url characters. Campaign, source and your CRM identifier go in there and nowhere else, because once the user is inside the bot the platform tells you a numeric user id and nothing about where they came from. Practices that build the conversation first and attribution later end up with a subscriber list of unknown origin and no way to value it. Bot architecture: Webhooks with a secret token header, not long polling. Per-chat sending sits near one message a second and the global ceiling near thirty, so any broadcast past a few thousand recipients runs through a queue that reads retry_after on a 429 rather than sleeping on a guess. Update ids are treated as idempotency keys, because Telegram redelivers. Inline keyboards hold funnel state; a Mini App appears only when a real form or a card payment is required, with the payment provider token bound to your Stripe account, not ours. Stars only for digital goods. Identity before offer: Telegram hands you a user id and sometimes a username. No email, no phone number unless the person taps to share their contact. So the first job of the funnel is a consented identity exchange that resolves the Telegram id against a record you already own, and until that is done the subscriber is not a contact and does not belong in your lifecycle reporting as one. We build that step explicitly and we log what was shown when consent was taken. Where this actually pays: Corridor and diaspora audiences, where Telegram is not an alternative channel but the default one: Russian-speaking, Ukrainian, Central Asian and Iranian communities in the Nordics and beyond. Emergency appeals for nonprofits, where a public channel paired with a bot moves faster than any email deployment and the bot handles the donation. Travel operators serving routes into those markets, where the same thread carries the schedule change and the rebooking. Refusals: We do not scrape group members. We do not auto-add anyone to a channel. We do not touch MTProto userbot automation running on a personal account, which violates the terms and gets the account removed, usually the week after launch. No engagement farming, no purchased subscribers, no bot written to read as a human being. If your growth plan depends on any of those, we are the wrong practice and you will find cheaper help elsewhere. Not for you if: Your audience is mainstream Nordic consumers. Telegram penetration in Sweden sits in single digits and a bot built for that file will be a support channel for a few hundred enthusiasts. You want a customer service inbox, which WhatsApp does better and staff already understand. Or you want the bot to be an LLM that answers anything asked of it, which is a different engagement with a different risk profile and we would rather you bought it from someone who specialises in it.