How to create a Telegram referral bot without code

Before BotFather: write the referral contract in six lines

A referral campaign becomes much easier to build when its rules fit on one screen. Write who can participate, what the referred user must do, what the sponsor receives, when the reward becomes available, what behavior is invalid and how a withdrawal works. If any line is unknown, the interface will only hide the uncertainty.

Set a maximum campaign liability before choosing an attractive reward. Multiply the reward by the highest number of qualified referrals the budget can support, then add network fees, support, failed transactions and a fraud reserve. The bot should never promise more than the funded operating model can deliver.

• Eligible users
• Qualifying action
• Reward amount
• Qualification timing
• Invalid behavior
• Minimum withdrawal
• Campaign cap
• Support path

Step 1: create and secure the Telegram bot

1. Open the verified @BotFather

   Send /newbot and choose a recognizable display name.

2. Choose the username

   Use a unique username that users can recognize in a referral URL.

3. Copy the token privately

   The token controls the bot; never paste it into public chats or screenshots.

4. Complete the profile

   Add an avatar, short description and plain explanation of the referral program.

5. Prepare recovery

   Know how to revoke and replace the token if it is exposed.

Step 2: connect Mini Empire and choose the first loop

Open the Mini Empire builder, create a bot project and connect the BotFather token. The prepared referral engine supplies the core user state, invite flow, menu and owner controls. Begin with one loop: understand the offer, satisfy the entry requirement, copy the referral link, invite a qualified person and observe the reward.

Customize the visible menu around that loop. Secondary buttons can explain the rules, show balance, display referral status, start a withdrawal or change language. Every button should either move the user forward or resolve uncertainty; decorative options weaken the first session.

Step 3: configure attribution and qualification

Telegram referral links normally use a start parameter. The bot receives the parameter when a new user starts it and can associate that account with the sponsor encoded in the link. Record the relationship once. Do not let later links silently replace the original sponsor, and do not count a user who opens their own link.

Next, define the qualification event. Mini Empire projects can use channel requirements and product activity to delay the credit until the new user has completed something meaningful. Tell both sides whether the invite is pending, qualified or rejected so a legitimate delay does not look like a missing payment.

Step 4: set rewards, levels and withdrawal rules

Choose a reward small enough to survive the least valuable legitimate cohort. Multi-level rewards can increase distribution, but each additional level creates more liability and makes the rules harder to explain. Start with one level unless there is a clear reason for a sponsor-of-sponsor commission.

Set the minimum withdrawal high enough that fees and support do not overwhelm small transfers, yet low enough that a real participant can reasonably reach it. State the address format, queue behavior, any daily limits and what happens after a failed transfer. Never describe an unfunded balance as instantly withdrawable.

• Reward per valid referral
• Maximum referrals rewarded per period
• Number of referral levels
• Minimum withdrawal
• Daily payout limit
• Project wallet reserve
• Failure and refund behavior

Step 5: run the seven-account abuse test

1. Normal pair

   One sponsor and one genuine new user complete the expected flow.

2. Own link

   The sponsor opens their own link and receives nothing.

3. Repeated start

   The referred user restarts the bot and no second credit appears.

4. Second sponsor

   A later referral link does not overwrite an existing relationship.

5. Incomplete gate

   A user who skips requirements remains pending.

6. Rapid cluster

   Several suspiciously fast accounts are visible for review or limited.

7. Withdrawal edge cases

   Invalid addresses, low balances and repeated taps do not lose or duplicate funds.

Step 6: launch in cohorts and operate the program

Invite 10–25 relevant testers first. Measure how many understand the offer, reach the qualifying event and can explain the withdrawal rule without assistance. Fix the most common confusion before buying traffic or announcing a large bounty.

After launch, use broadcasts for rule changes, status updates and meaningful campaigns. Use tasks when they create measurable value, not merely activity. Review reward cost and retained contribution by cohort every week. A referral program is an acquisition channel with liabilities; it should be operated with the same discipline as paid advertising.

• Activation rate
• Qualification rate
• Qualified invites per active user
• Seven-day retained referrals
• Reward cost per retained user
• Withdrawal success rate
• Support tickets per 100 users