🧩
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.
🚀 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.