Start in Telegram

Open KickThemBot and connect your first private group.

KickThemBot setup starts in Telegram. Open the bot, connect one private destination, and prove the access lifecycle with a controlled account before sending paid traffic.

Open @KickThemBot See next steps

Telegram opens @KickThemBot. Opening the bot does not purchase a plan or expose a private invite link.

Telegram identityPrivate destinationControlled access testNo public invite link

Three steps

Go from this site to a controlled Telegram test.

Keep the first setup small. One bot, one protected destination, and one test member are enough to prove the lifecycle before launch.

01

Open @KickThemBot

Open the bot in Telegram and tap Start so setup is tied to your Telegram identity.

02

Connect one destination

Create or select a project, then add KickThemBot as an admin in the private group or channel you want to protect.

03

Run a controlled test

Use a test member to verify access, membership status, reminder timing, expiry, removal, and support recovery before launch.

Open @KickThemBot

Return to the launch checklist after the controlled member completes access, expiry, and removal testing.

Optional guides

Use a focused guide after the bot is open.

These supporting routes cover lifecycle testing, website checkout, and API work. They are references for the setup you start inside Telegram, not substitutes for opening the bot.

Free plan path

Prove the lifecycle in a small private group

Use the Fresh plan scope to test plan setup, access-code redemption, Telegram identity binding, reminder timing, expiry, and removal behavior before promoting a paid offer.

  1. Create one protected destination
  2. Generate a controlled access code
  3. Redeem with a test Telegram account
  4. Run expiry and support recovery checks
Open launch checklist
Website checkout

Connect an existing checkout to Telegram access

When payment happens on a website, keep the payment event server side and use an access code or membership update to route the buyer into Telegram safely.

  1. Confirm payment in the checkout backend
  2. Map product or price to a plan
  3. Create an access code after confirmation
  4. Bind redemption to Telegram identity
Read checkout handoff
Developer path

Use the API for trusted backend workflows

Use the documented project-scoped API when support tools, CRMs, checkout systems, or custom backends need plan lookup, access-code creation, membership lookup, or renewal updates.

  1. Keep API keys server side
  2. List plans from the trusted backend
  3. Create access codes or update membership
  4. Log support-visible outcomes
Review API scope

Plan size

Review the limits, then configure the plan in Telegram.

Opening @KickThemBot does not purchase a plan. It starts the authenticated setup flow where the available plan and billing choices can be confirmed.

Fresh

Test it

$0/mo
  • 20 active members
  • 1 project and 1 channel
  • 20 access codes per month
  • Basic renewal reminders

Use Fresh to prove the workflow with a small controlled Telegram community before upgrading.

Open bot

Bouncer

Start selling

$9/mo
  • 150 active members
  • 1 project and 3 channels
  • 200 access codes per month
  • Custom reminders

Perfect when your group is already making money, but member tracking is starting to waste your time.

Open bot

Empire

Scale up

$49/mo
  • 3,000 active members
  • 20 projects and 60 channels
  • 5,000 access codes per month
  • Advanced access reporting
  • Full API access

For operators managing multiple paid communities who need scale, control, and faster support.

Open bot

Before paid traffic

Run the access lifecycle once with a controlled account.

A launch-ready setup proves first access, renewal reminder, cancellation, expiry, removal, and support recovery before the public sales path sends real members into Telegram.

Check bot permissions Plan reminders Read direct answers

FAQ

Start safely before exposing a paid Telegram group.

Where should a new KickThemBot setup start?

Open @KickThemBot in Telegram, connect one private destination, and prove the membership lifecycle with a controlled test member before launch.

Should a public site send buyers straight to a private invite link?

No. The safer path is a controlled setup flow where payment or approval creates access through membership state, access-code redemption, or a trusted backend update.