What you can enter
Supports @username, bare usernames, phone numbers and t.me user links, one per line, up to 500 lines at a time.
TGEggBulk DM guide中文
Bulk DMs: choosing between the four target sources
The biggest difference between the four target sources isn't how the message is sent, but where the targets come from and whether another account can take over. Pick the right source first, then set the number of targets per round and the run mode, and the task becomes easy to follow.
The most important rule: none of the four sources will resend to targets that have already been processed. "No round limit" only means the task can keep taking the next batch of unprocessed targets; once all targets are processed, the task ends automatically.
Rate limit reference from real tests: on average, one Telegram Premium account can DM about 10–20 strangers before it may hit restrictions. This is only a rule of thumb, not a fixed quota published by Telegram; account status, registration date, sending pace, content and user reports all affect the actual result.
The short version
| Target source | Where the data comes from | Target ownership | If the account is restricted | Best for |
|---|---|---|---|---|
| Manual list | Pasted usernames, phone numbers or user links | Shared target pool | Switch sending accounts and continue | You already have a specific list of contacts |
| Selected groups | Collected group members | Shared target pool | Switch sending accounts and continue | DMing members of one or more groups |
| Private chats | Each account's own existing private chats | Tied to the original account | Can't be continued by another account | Reaching people you've chatted with before |
| Contacts | Each account's own Telegram contacts | Tied to the original account | Can't be continued by another account | Reaching saved contacts |
1. Manual list
How it's split
The parsed targets are split evenly across the selected accounts. Each target is handled by only one of the accounts, not sent once by every account.
- Select one or more sending accounts.
- Paste usernames, phone numbers or user links into the target list, one per line.
- Set the delay between messages, the per-account limit per round and the run mode.
- If an account gets restricted, right-click the task (on mobile, tap "More actions") and use "Manage accounts" to replace it.
Example
120 targets, 3 accounts, per-account limit of 10: each round handles at most 30 targets, so it takes about 4 rounds.
If one account is restricted, the replacement account only takes over the remaining targets and won't resend to targets that already succeeded or clearly failed.
2. Selected groups
Collect members first
Collect members in "Joined groups" first, then select one or more collected groups. You can select up to 50 groups; duplicate members are merged.
Public members and active posters
Targets are taken from the scope you tick in the task. Bots, deleted accounts and members that can't be resolved are never added as sendable targets.
- In "Joined groups", select the account and group and run "Collect members".
- Create a new DM task, choose "Selected groups" and the member scope you need.
- Select several sending accounts; the system merges, de-duplicates and splits the members evenly.
- If you later need to add or replace accounts, use "Manage accounts" to keep sending to the remaining targets.
Members without a username are the exception: they can usually only be resolved by the original account that collected their access credentials. If you haven't selected that collecting account, those members stay waiting in the target pool and won't be handed to just any other account.
Example
A group has 900 collected members, of which 760 can actually be resolved. With 5 accounts and a per-account limit of 10, each round handles at most 50 people.
If an account is restricted midway, you can switch accounts and continue; each member in the shared pool is still handled only once.
3. Private chats
Where the targets come from
Reads the real private chats the sending account already has, excluding bots, Saved Messages and invalid chats. Before using it, sync the chat list in "Joined groups".
When you select several accounts
Each account gets its own task based on its own private chats. They aren't merged into a shared pool, and account A's chat targets can't be handed to account B.
Example
Account A has 80 valid private chats. With a per-account limit of 10 and "Repeat at interval", it takes about 8 rounds.
Processed chats won't be messaged again, but if account A is restricted, account B can't access those chats on A's behalf, so the task can't continue.
4. Contacts
After selecting the sending account, click "Sync contacts" first, and save the task only after the sync finishes. Contacts are only synced when you trigger it yourself; they no longer update automatically with the chat list.
Targets are frozen at creation
When the task is created, it reads all valid Telegram contacts of the sending account and saves them as targets. Bots and deleted users are filtered out automatically.
Contacts belong to the original account
When you select several accounts, each account gets its own task. Account A's contacts can't be handed to account B to continue.
Example
Account A syncs 200 valid contacts. With a per-account limit of 10, a "Repeat at interval" task takes the next batch of contacts each round.
The task ends automatically once all targets are processed; if the account is restricted, you can't use "Manage accounts" to move these contacts to another account.
Run mode, rounds and per-account limit
1
Run once now
Runs a single round only. If there are many targets but a small per-account limit, targets beyond this round won't continue automatically.
2
Repeat at interval
After each round, waits the number of minutes you set and then takes the next batch of unprocessed targets. It completes automatically when targets run out and never loops back to the start.
3
Manual only
Each click on "Send" runs one round. Useful when you want to check account status before every round.
4
Per-account limit
Controls the maximum number of people each account handles per round, not the total for the whole task. Set it to 0 for no limit in that round.
5
Max rounds
Only limits how many rounds can run. "No round limit" doesn't mean repeated sending; the task still ends once all targets are processed.
Success, failure and continuing with another account
Don't keep pushing when an account is restricted: once the platform confirms via SpamBot that the account is marked blocked or restricted, it pauses the task. Manual list and Selected groups tasks can continue with a different account; Private chats and Contacts tasks usually can't, because their data is tied to the original account.
- Succeeded: never reassigned and never sent again.
- Clearly failed: for example, the user really doesn't exist. These count as processed and aren't retried every round.
- Account-level errors: for example, the account is restricted or its session has expired. The target itself isn't used up; shared-pool tasks can continue with another account.
- Before deleting a Telegram account: replace or remove it in "Manage accounts" first, so the targets assigned to it aren't deleted along with the task.
FAQ
With no round limit, will it keep messaging the same people?
No. Every source skips targets that already succeeded or clearly failed. Rounds just split a large target pool into batches, and the task ends automatically when targets run out.
If I change the per-account limit, does it start over from the first target?
No. The change only affects how many people the next round takes. Targets that already succeeded or clearly failed keep their records and are still skipped.
Why is the target count different from the total sent?
The target count is the number of targets currently assigned to the task; the total sent records the successes, failures and pending sends so far. When accounts are changed in a shared pool, targets may be reassigned, but the history stays.
Why can't some group members be assigned to a new account?
Members without a username need the access credentials saved by the original collecting account. A new account without those credentials can't resolve them, so they wait until the original collecting account is added back to the sending accounts.
When should I use "Only message users with an existing chat"?
Turn it on when you want to lower the risk of messaging strangers. It only sends to users the sending account has already chatted with, so there are fewer targets, but it's usually safer.