🧩
Where to start: accounts and proxies
The most important part — this decides whether your accounts survive
Neurogram acts on behalf of your Telegram accounts. How long they live without bans depends directly on the quality of the accounts and proxies. Read this before launching.
✅ Which accounts to use
- Aged — a few months old, ideally 1 year+. Older accounts are trusted more.
- With a full session — a pair of .json + .session files (Telethon/TData converted to .session).
- With a filled-in profile (name, photo, Premium if possible).
- With 2FA if possible — harder to steal.
❌ Which not to use
- Freshly registered (today/yesterday) — almost immediately hit a spam block.
- Bulk «cheap» accounts from a single source — often already flagged.
- Accounts without a .session (only number/password) — you'll have to re-authorize them.
- Already restricted / with an active spam block.
✅ Which proxies to use
- Residential or mobile — their IPs belong to real providers, Telegram trusts them more.
- An individual proxy per account — don't share one IP across many.
- SOCKS5/HTTP format:
socks5:host:port:user:pass. - Stable, ideally in the country/region matching the account.
❌ Which proxies not to use
- Datacenter (DC) IPv4 — Telegram spots them easily and flags them more often.
- Public/free proxies — unstable and «dirty».
- One proxy for dozens of accounts — a fast path to a mass ban.
- A proxy from a different country than the account's «home» — a sudden geo change is suspicious.
💡 Golden rule: 1 account = 1 individual residential/mobile proxy, aged accounts, soft limits in the first days. Start with 1–2 accounts, watch for a day, then scale.
🛡️
Spam block: what it is and what to do
A restriction, not a ban — and it is usually lifted
A spam block is a restriction Telegram applies after complaints: the account cannot message strangers, everything else still works. It is not deleted and not lost. The status shows on the Accounts tab after you press «Check» — the service asks @SpamBot and reports the answer whatever language the bot replies in.
✅ What to do
- File an appeal straight from the account card. The service walks the whole @SpamBot conversation and passes your text along.
- Write it like a human: who you are, why you message people, why there will be no more complaints. Boilerplate is lifted less often.
- Cut this account back and give it a few quiet days.
- While the restriction stands, leave the account on «AI dialog» only: it replies to people who wrote first, which the restriction does not cover.
❌ What not to do
- Do not file ten appeals a day — it makes things worse.
- Do not keep messaging «around» it: a second restriction is noticeably harder to lift.
- Do not swap proxies hoping to reset it — the block is on the account, not the IP.
- Do not just buy more accounts before finding the cause: with the same settings they go the same way.
💡 The cause is almost always the same: too many messages to strangers in a short time, often with identical text. Warm-up, varied first messages and gentle daily limits solve it before the restriction appears.
🧯
When something does not work
Common breakages and what to check first
Nearly every support ticket is one of a dozen situations. Here they are with their causes — most take a minute to fix.
| What you see | Why, and what to do |
|---|---|
| «Session lost» | The account is logged out: password changed, sessions terminated, or a broken file. Only a fresh .session upload fixes it. |
| Account will not connect, proxy «not responding» | Press «Check proxy». A red dot means the proxy is dead or the format is wrong. Verify socks5:host:port:user:pass and that it is paid for. |
| No comments are written, the log is silent | Check three things in order: the API key is active and funded, channels are distributed in the base, the account is selected as working. |
| «Key does not verify» or the check takes over a minute | The provider is unreachable from your network or out of credit. Groq or Gemini are the free starting options. |
| The module runs but there are few comments | Usually too few channels with open discussions. A channel without a discussion group has nothing to comment on and is skipped quietly. |
| Some comments go through, some do not | That is expected: a closed discussion group, the account banned in that channel, or a post too old. The log says which happened to each. |
| A scheduled or cloned post did not go out | The executing account lost its admin rights in the channel. Restore them and run it again. |
| A module is locked although the subscription is paid | Reload the page — access is fetched when the dashboard loads. If the lock mentions the trial, that module is closed for its duration. |
| You added 200 publics and 50 remain | The free-trial ceiling. The service says so in a message; paying removes it. |
| Accounts get banned one after another | Look at the setup, not the module: datacenter proxies, one IP across many accounts, fresh accounts with no warm-up, identical campaign text. Usually all of them at once. |
💡 Not on the list — write to support from the dashboard and attach a screenshot of the log. The log almost always shows the cause; «it does not work» almost never does.
🚀 Quick start in 6 steps
💡 General workflow: upload accounts and proxies → connect an AI model in «AI & Keys» → collect channels/groups with the parsers → distribute them in the Base → select accounts in a module and launch.
🌡️ Warm-up: a fresh account does not run at full speed — the daily cap grows over thirty days. What that means for your fleet, and when you reach your volume, is what the warm-up calculator works out.