How many accounts can I add?
The number of accounts depends on your subscription plan. Check the subscription section to see your limits.
Everything you need to work with the platform: step-by-step guides, tool manuals, and solutions to common issues.
Follow these steps to launch your first campaign in 15–30 minutes.
Add Telegram Accounts
Import accounts via file, archive, or session folder. Make sure the accounts are active.
Set Up Proxies
Add proxy servers and verify their availability. 1 proxy per 1–2 accounts is recommended.
Organize Accounts into Categories
Categories help manage accounts and distribute load across tasks.
Build an Audience
Use the parser to collect a target audience from Telegram groups, channels, and chats.
Create Your First Task
Choose a tool (tagging, masslooking, inviting) and launch a task.
Monitor Task Progress
Track task progress in real time, view logs and results.
Handle Common Errors
Review the troubleshooting section to quickly resolve failures.
Detailed instructions for each platform module.
The basic path from account and proxy setup to the first task, logs, and result analysis.
The platform works as a system: accounts and proxies form the infrastructure, audiences define direction, tasks perform actions, and analytics shows the result.
How to prepare a channel, chat, or profile before traffic: name, avatar, description, pinned post, and next step.
Platform tasks bring attention to your Telegram project, but conversion happens in the channel, chat, profile, or offer. Prepare the destination before sending traffic.
How to add Telegram accounts using supported session formats and verify them before tasks.
Account import brings working Telegram sessions into the platform and prepares them for tasks. Check the files, format, and source before uploading so that fewer accounts are skipped.
How to use categories, statuses, bulk actions, and logs to keep your account base organized.
The accounts section keeps your working pool organized: statuses, categories, bulk actions, logs, and verification codes all live in one place.
How to separate working accounts from problematic ones, account for geo, error history, and project boundaries.
An account in the platform is a working unit that performs actions. The better the account pool is prepared, the more stable tasks become.
How to add, test, and bind proxies to accounts before launching tasks.
Proxies reduce block risk and help distribute network load across accounts. Before tasks run, add, test, and bind proxies correctly.
How to reduce errors: proxy geo, load per address, pre-launch checks, and failure diagnostics.
A proxy gives accounts a separate network route. If it is unavailable, overloaded, or mismatched, a task can stall, slow down, or produce repeated errors.
How to collect users from relevant sources, apply filters, and prepare lists for tasks.
Audience collection creates the user base for later tools. Result quality depends on source relevance, filters, and careful deduplication.
Why list size is not the same as result, and how to compare audiences for tagging, inviting, and masslooking.
A good audience is not just a large list. It is a list of people who already have interest in the topic of your project.
How to configure a tagging task: audience, accounts, mentions per story, pace, and monitoring.
Story tagging attracts audience attention through mentions. The tool is sensitive to account quality, pace settings, and clean input data.
A checklist for launching a story with an offer: audience, unrestricted accounts, proxies, moderate pace, and result review.
Story tagging attracts attention from selected audiences. The user sees a mention, opens the story, and can move to your profile, channel, chat, or offer.
How to run story views for a target audience and prepare the profile for visits after contact.
Masslooking views stories from the selected audience through your accounts. It is a softer contact tool, but limits and account quality still matter.
How to choose an audience, prepare accounts, run a test, and scale only combinations that bring visits.
Masslooking shows your account to an audience through story views. It is a soft contact: the user chooses whether to visit your profile, channel, chat, or another destination.
How to invite an audience to a channel or chat, configure pace, and track joins, errors, and outcomes.
Inviting adds users to selected communities. It is one of the most limit-sensitive tools, so audience quality, account rights, and pace settings are critical.
How to prepare the destination, pinned post, target audience, and gradually increase invitations without chaotic errors.
Inviting brings an audience into your channel or chat. It works best when the destination is ready and has a clear pinned post and next step.
How to prepare target lists, choose accounts, and control joins without unnecessary restrictions.
Joining tasks help accounts enter selected chats and channels. Target list quality, account health, and a moderate pace directly affect the result.
How to handle FLOOD_WAIT, temporary restrictions, pauses, and gradual load growth.
Telegram can restrict accounts for frequent or suspicious actions. Safe work is based on stable task execution, not maximum speed.
How to review task, account, and campaign statistics while separating technical errors from a weak offer.
Analytics helps evaluate task, account, and campaign performance. Use it after completion and during execution to catch problems early.
Metrics to review after a task: actions, errors, pauses, audience quality, visits, subscriptions, and leads.
After launch, do not look only at completed actions. Analytics should show what worked: audience, accounts, offer, tool, or task settings.
How to build the user path from first contact to target action through audiences, accounts, tasks, and analytics.
Effective Telegram promotion is not built around one tool, but around a combination. A combination is the user's path from first contact to subscription, lead, visit, dialogue, or another target action.
How to check audience, accounts, proxies, target destination, CTA, logs, and the chosen tool.
If a task runs technically but brings no business result, the problem is usually not automation itself. Review the full chain: audience source, offer, packaging, task settings, and account quality.
Solutions to common problems encountered by platform users.
Task stuck in preparation
Accounts are busy with another task or proxies are unavailable.
Many FLOOD_WAIT errors
Operation speed is too high for the current accounts.
Account requires re-authorization
Account session has expired or was terminated by Telegram.
Proxy fails verification
Proxy server is unavailable, expired, or incorrect credentials.
Account import did not complete
Wrong file format, corrupted sessions, or limit exceeded.
No verification codes arriving
Connection issue, SMS service problem, or account is blocked.
Audience collection returned too few users
Sources are small, filters are too strict, or groups are closed.
Campaign finished but results are low
Low audience quality, irrelevant content, or suboptimal settings.
Accounts get restricted quickly
The pace is too high for account age, history, or current condition.
Proxy passes checks but the task still errors
The proxy may be unstable under load or unsuitable for the selected account group.
Masslooking gets views but no visits
The audience is irrelevant or account profiles do not explain the next step.
Inviting brings too few joins
The chat or channel is not prepared, the audience is too broad, or the pace triggers restrictions.
Quick answers to the most common questions.
The number of accounts depends on your subscription plan. Check the subscription section to see your limits.
We recommend 1 proxy per 1–2 accounts to reduce the risk of blocks.
Speed is limited by Telegram API limits and safety settings. Too high a speed can lead to FLOOD_WAIT errors.
The platform supports .session (Telethon) and .tdata (TDesktop) formats. Import as files or archives.
Yes, but one account can only be used in one task at a time. Distribute accounts across tasks.
Contact support via the Support section or message the team in the Telegram chat.
Start with accounts and proxies: import accounts, check statuses, bind working proxies, then build an audience and run a small test task.
Large volume makes diagnostics harder and exposes account limits faster. First test the full combination: audience, accounts, proxies, offer, and pace.
Both matter, but a large account pool does not compensate for an irrelevant audience. A task can run technically and still bring weak results.
Check the full chain: audience source, offer, channel or profile packaging, chosen tool, pace, account errors, and proxy errors.
If errors repeat on accounts using the same proxy, a task stalls in preparation, or network failures appear, start diagnostics by checking and replacing proxies.
Reduce pace when FLOOD_WAIT grows, account errors repeat, proxies are unstable, re-authorizations appear, or successful actions drop sharply.