Run Your First Bulk DM
Prerequisite: at least 1 account (a session account that is not logged in works too; it goes online automatically when sending) and a list of usernames.
If you have no list, harvest a CSV with Member Harvest first, or write a TXT by hand for a trial run:
@your_other_account
t.me/a_friend
For the first run, enter just two or three accounts whose inboxes you can see yourself.
Step 1: Pick accounts
Sidebar Bulk DM (私信群发) → Parameters (参数设置) tab → check accounts under Participating accounts (参与账号).
Set Presets (参数预设) to Conservative (保守). Leave the rest alone for now.
Step 2: Import the list
Switch back to Direct mode (直发模式). In card ① Recipient list (收件人名单), click Import (导入) and choose the file from before. The import result reports how many were added, duplicate and invalid.
Step 3: Write the text
Card ② DM text (私信文案): one message per line, and each recipient gets one line at random:
{Hello|Hi}, I saw you're in the XX group too, {got a minute to chat|I'd like to ask you something}
{Hey|Are you there}, sorry to bother you, I'd like to hear your take on XX
The more lines and variants, the less alike the outgoing messages are.
Step 4: Send
Click Start sending (开始发送) at the bottom. The estimate line at the bottom tells you how many recipients are pending, how many accounts, and roughly how long it will take.
Watch progress in the right column:
| Counter | Meaning |
|---|---|
| Succeeded (成功) | Delivered |
| Failed (失败) | The reason is in the list's Notes (备注) column. It is not resent automatically |
| Contacts-only block (双向拦截) | The recipient only accepts DMs from contacts, so the message cannot get through |
| Remaining (剩余) | Not reached yet |
When it finishes, go back to card ① and click Export (导出) to get each person's status and the account that handled them.
Before a real run
- Messages per account (单账号发送数量) applies to one round only. Start another round and it counts from 0 again. Three rounds a day means three times the volume for one account, so keep track yourself
- An account that hits PEER_FLOOD retries automatically, asks @SpamBot, and recovers when the limit lifts; no manual handling needed. But hitting it often means the volume is too high or the text is too repetitive
- With many accounts, configure many proxies: accounts on the same proxy send in a queue, see Proxies determine concurrency