Every other number in this catalogue is read by somebody else. A bot start is not: it is an account sending /start to your bot, and the only place it shows up is your own database. That makes the link you submit the real decision, because a link carrying ?start= and a code is filed differently from the bare address. TGLUX has 30 bot start services from $0.20 per 1000, taking orders from 50 up to 200,000. Below: the mechanic, payloads and referral codes, what a start is worth, today's rates, and getting the bot ready.
Quick map
- One account, one start, one row in your table
- Where a start lands when the link carries a payload
- Telegram bot start referral: judging one row against another
- What a thousand bot starts costs
- What one start is worth to you
- Getting the bot ready before you order
- From bot check to delivered starts
- Questions a bot owner asks first
One account, one start, one row in your table
Telegram treats /start as the opening of a conversation. An account taps a bot link, the client sends that command, and your bot receives an update naming the account. Telegram bot start referrals are that event, ordered in quantity against a link you supply.
One thing separates this from the rest of the catalogue: there is no public number. A channel shows its member count and a post shows its views, so anyone can read those. A bot shows nobody anything. The figure a start order moves is the one in your own database, which means the audience for it is you, a partner, or a referral scheme that is counting.
Where a start lands when the link carries a payload
The link you paste decides where a start lands. The bare bot address registers the account and nothing more. Add ?start= and a code, and Telegram hands that code to your bot alongside the start command, so your handler can file the registration under a campaign, a referrer or a bonus.
If your bot runs a referral scheme this is not a detail. An order placed on the plain link fills the same count of registrations and attributes none of them, and there is no way to re-file them afterwards. One order carries one link, so one code: starts that have to be split between two codes are two orders.
Telegram bot start referral: judging one row against another
The honest way to tell Telegram bot start referrals apart is to watch one order and then look again a week later. What a good service does is unremarkable: it records where you started, fills steadily rather than all at once, and returns the money for anything it could not deliver. What a bad one does is also unremarkable, and only visible on the second look. Either way the test costs a few cents here, which is the only reason the advice is worth anything.
What a thousand bot starts costs
Rates here sit in two groups rather than on a smooth curve: the plain country rows at $0.20 per 1000, and the rows the provider names by Search Ranking at $0.70. The ladder below runs from the cheapest row in the category to the dearest so both ends are visible. Each is quoted per 1000 and accepts orders from 50 to 200,000:
- 🇺🇸 Usa Bot start - from $0.20 / 1000 (min 50, max 200,000)
- 🇹🇷 Turkey Bot start - from $0.20 / 1000 (min 50, max 200,000)
- 🇰🇿 Kazakhstan Bot start - from $0.20 / 1000 (min 50, max 200,000)
- 🇸🇦 Arab Bot start by Search Ranking - from $0.70 / 1000 (min 50, max 200,000)
- 🇫🇷 France Bot start by Search Ranking - from $0.70 / 1000 (min 50, max 200,000)
- Random 13-Country Bot start by Search Ranking - from $0.70 / 1000 (min 50, max 200,000)
Rates move with the catalogue - the live list is on our Telegram Bot Starts page.
The dearer rows in this category are the ones the provider names by Search Ranking; what reaches your bot is the same start command either way, payload included. If you have not compared them on your own bot yet, the plain country rows are the place to begin.
What one start is worth to you
What you are buying is the top of your own funnel and nothing below it. Every stage after the start command behaves exactly as it did before, on a larger number of accounts.
So the figure to watch is not the start count. It is whatever your bot counts next, and whether that moved in anything like the same proportion. The country on a row matters for the same reason: a bot whose first message is in one language is talking to whoever that row delivered, and a registration that cannot read the reply is a row in a table rather than a user.
Getting the bot ready before you order
Four checks, and together they take less time than the order does. Open your own link in Telegram and press start, so you know the bot replies. Read your log and confirm the payload arrived, not just the registration. Make sure nothing is mid-deploy. And have a way to count registrations, because you will want the figure from before.
The third one is the one that costs money. Starts are delivered while the order runs and the event cannot be replayed - if your bot was restarting as they arrived, the registrations happened and your handler may never have seen them. No cancellation or refund covers that, because the order delivered what it promised.
From bot check to delivered starts
- Create a free account at TGLUX; the whole price list is readable before you deposit anything.
- Build the link you actually want - the bare bot address, or one with
?start=and a code if the starts need attributing - and tap it yourself to be sure the code reaches your handler. - Pick a row on the Telegram Bot Starts page, matching the country to the language your bot replies in.
- Place the smallest order the row takes, which is 50 here, against that exact link.
- Check your own registrations, not only the order status, before you order again.
Questions a bot owner asks first
What if my bot was down while the order ran? The starts still happened and the order counts as delivered, so there is nothing to refund. That is the whole reason for pressing start on your own link first: a minute spent there is cheaper than an order you cannot see the result of.
Do you need my bot token? No. The public bot link is the whole requirement. A bot token is full control of the bot, so anything that asks for one should be treated as disqualified on the spot, whatever the reason given.
What does the code on the end of my link do? Telegram passes it to your bot as the argument of the start command, so your handler can file each registration against a campaign, a referrer or a bonus. An order on the plain address delivers the same registrations with nothing attached, and they cannot be labelled afterwards.
Can I watch the starts arriving? In your own logs, yes. A bot has no public counter, so the two figures to compare are the order progress on your TGLUX dashboard and your own registration count - which is why it is worth recording that count before you order.
Will the accounts use my bot after the start? Treat a start as a registration and nothing more. What happens after the start command depends entirely on what your bot replies and what it asks for, and no order can change that part.
Point a test order at your own bot
Get the bot replying, write down the number of registrations it has, then place one order at 50 from the Telegram Bot Starts page. Everything after the start command is yours to improve, and that is far easier to judge against a figure you measured than one you guessed.