How every TGBLAST feature works

The minimum path every new user goes through. Every step has its own page with the fields, tips and gotchas.How it looks in numbers — the funnel on 40 accounts.

1. 01

   Sign up

   On the /register page fill in "Login", "Email — for account recovery", "Password", "Confirm password" and click "Sign up". You land in the "Subscription" section right away.

2. 02

   Pay for the plan

   In the "Subscription" section ("Account" menu) click "Pay", use the "Copy" button to copy the wallet address and the exact amount, then send USDT on the TRON network (TRC20). In 1–3 minutes the status turns "Active" and the dashboard sections open.

3. 03

   Add proxies

   "Proxies" section ("Resources" menu) → "Add proxy" → paste the list (one proxy per line) → "Add" → "Select all" → "Check". Upload proxies before accounts.

4. 04

   Upload accounts

   "Accounts" section → "Upload folder" → "Select the folder with accounts" (inside it — subfolders with tdata or .session). After a couple of minutes click "Refresh", then select the accounts and run the "SpamBot check".

5. 05

   Warm up the accounts

   In "Accounts" select them and click "Assign group", then in the "Warm-up" section ("Automation" menu) click "Start warm-up", pick the group and wait for the "Completed" badge.

6. 06

   Collect an audience

   "Scraping" section → "New scrape" → pick the mode and enter the chat/channel → once the status is "Done" click "To audience". You can also run the username list through the "Checker" and save it with the "Save to audience" button.

7. 07

   Launch the campaign

   "Campaigns" section → "New DM campaign" → fill in "Campaign name" and "Message template", pick "Audience for the campaign", set "Max sends per account per day" to 3–5 → "Create campaign" → click "Start" in the list. Read replies in "Inbox" (the "Fetch" button) and "Conversations"; the results are in the "Send log" and "Stats".

Sixteen pages: what the section is for, the step-by-step run-through, every field explained, tips and common mistakes. Open the one you need — or start with the quick start above.

Session (.session, session string)

A file or a string that stores the login to a Telegram account. TGBLAST uses it to act as that account without entering a code from an SMS. You upload it in the "Accounts" section via "Upload folder" (a *.session file) or "Import session:proxy (.txt)" (a session string). If Telegram has revoked the session, the account gets the "Invalid" status.

tdata

A folder with login data from the Telegram Desktop app. The second way to upload an account: put the tdata folder into the account's subfolder and upload it with "Upload folder". tdata from Telegram Desktop 6.x is not supported; you need version 5.x.

Proxy

An intermediate server (ip:port) that the account uses to reach the internet, so that Telegram does not see many accounts from one address. The proxy pool is kept in the "Proxies" section, and accounts are linked to proxies in the "Accounts" section ("Assign proxy", "Distribute proxies (round-robin)"). An account without a working proxy is left out of the campaign.

TDLib

Telegram's official library (Telegram X runs on it) that the CRM uses for everything: campaigns, checks, conversations, scraping, warm-up and the commenter. An account signs in to TDLib by itself, with a QR code confirmed by its own session, after upload or on its first operation. If Telegram asks for an e-mail, 2FA is on with no known password, or the session was revoked, the account gets the reason "Could not sign in to TDLib: …" and is taken out of work. The proxy must be SOCKS5 or HTTP.

Warm-up

A simulation of live activity: accounts in a group message each other using built-in scripts (the "Warm-up" section). After a warm-up the account gets the "Warmed-up account" badge (a flame icon). Warmed-up accounts are required for the "Checker" and are safer in campaigns.

Account group

A folder for accounts, created in the "Accounts" section via "Assign group". You pick the group when you start a warm-up and in campaigns, stories, the group checker and the AI commenter, so that only the accounts you need are used.

FloodWait

A temporary ban from Telegram: "wait N seconds/hours" for acting too often. The account is automatically marked "Restricted" until the pause ends, and its campaign tasks move to other accounts. It lifts by itself once the time is up (when the "Auto-lift restrictions" toggle in "Settings" is on).

Spam block (freeze)

A Telegram restriction for complaints: the account cannot write to people it does not know. In the dashboard that is the "Restricted" status (until a date) or "Frozen" (indefinite, an appeal is needed). It is checked with the "SpamBot check" button in "Accounts", and the appeal is filed by hand in "Conversations" via "Open @SpamBot".

@SpamBot

Telegram's official bot that tells you whether an account has restrictions and accepts appeals. TGBLAST queries it automatically (the "SpamBot check" button, the "Auto-check via SpamBot" toggle), and you chat with it in the "Conversations" section.

Appeal

Your request to Telegram to lift a restriction, sent to the @SpamBot bot. In the dashboard it is a flag: the "Appeal filed" button in the @SpamBot chat in "Conversations", the "Appeal filed" filter in "Accounts". The flag is cleared with the "Restore to active" button.

Per-account limit ("Max sends per account per day")

How many messages one account may send within a rolling 24 hours inside a campaign. 3–5 is recommended. When every account has hit the limit, the campaign moves to "Paused" on its own; click "Resume" later.

Anti-spam delay ("Delay between messages (sec)")

A random pause between two messages from the same account, 30–600 seconds by default. Together with "Working hours (Sleep Mode)" and the daily limit it is the main protection against a block. There is no separate "anti-spam" screen — everything is set in the campaign form.

Scraping

Automatic collection of people from public chats and channels (the "Scraping" section): chat members, people who posted, commenters, a channel's audience. The result is saved with the "To audience" or "CSV" button.

Audience

A list of recipient usernames (the "Audiences" section). The audience is exactly what you pick in the "Campaign audience" field when you create a campaign, and also for tags in stories and mentions in group campaigns.

Segment (part of an audience)

A small audience of 20–50 people cut out of a large list: the "Split into parts" button in "Scraping" or the "Split" tab in the "Checker". Parts are convenient to hand out to different accounts and to run as separate campaigns.

Checker

A check of a username list run by live warmed-up accounts (the "Checker" section): it weeds out non-existent users, bots, people who have not been online for a long time, and premium users. The "Group checker" is a different check: whether you can join a chat and whether messages with links get deleted there.

Spintax

The {option1|option2} notation in the "Message template": each recipient randomly gets one of the options, the texts come out different, and the spam filter triggers less often.

Persona

A profile template (first name, last name, bio, avatar) from the "Personas" section. It is picked in the "Persona (account identity)" field when you create a campaign — before sending, the accounts take on its data.

USDT TRC20

The USDT stablecoin (1 USDT = 1 dollar) on the TRON network. The only way to pay for a subscription. When you withdraw from an exchange or a wallet, always pick the TRON (TRC20) network; the system will not see other networks (ERC20, BEP20).

Transaction hash (TxID)

A unique 64-character code for a transfer. You can take it from your wallet or exchange history or from tronscan.org and paste it into the "Transaction hash (optional)" field after the "I have paid" button, so that the system finds the payment faster.