Scalegram reads your Telegram through connections you own, and there are two kinds. They are not competing options so much as two halves of a whole; understanding what each sees is the fastest way to set up a workspace correctly.
Mode One: Your Personal Account
You sign in with your own phone number and code, exactly as Telegram's own apps do, and Scalegram syncs what that account can see: every existing DM, group and channel, including the full history of every lead you talked to before Scalegram existed. For an operator with years of conversations, this is the mode that makes the product land: the pipeline starts full.
The honest caveat: Telegram's terms frown on third-party automation of user accounts, and accounts doing aggressive automated sending get limited. Scalegram's design keeps this surface small, because it never sends from your account at all: it reads, politely and at a sane pace. The risk is not zero, and the connect screen says so plainly, but it is a fraction of what sender tools carry.
Mode Two: A Bot
Paste a token from BotFather, or let Scalegram create the bot for you. Bots are fully sanctioned by Telegram: zero account risk, ever. The trade is visibility: a bot only sees leads who pressed start and groups it was added to, with no history from before.
What bots lack in hindsight they repay in foresight. A bot link in an ad or bio delivers every new lead pre-attributed: with a tracking link pointing at the bot, the ad click identifier arrives inside the start parameter, and the new contact is born knowing which campaign created it. The bot also serves as your alert channel for new leads and keyword mentions, and it is the same sanctioned door the AI assistant uses to answer your profile.
The Setup That Wins
Run both. The personal connection carries your existing book of business into the pipeline; the bot receives the attributed future. A workspace can hold several of each, and contacts deduplicate on the person, not the door: a lead seen by both connections is one record with one history.
Security note: connection credentials are encrypted at rest, never displayed after creation, and deleted when you disconnect. If you log the session out from your phone, Scalegram shows a reconnect banner rather than failing silently.
"Personal for the past, bot for the future. Nearly every serious workspace ends up on both, and the contact record does not care which door a lead came through."
— Alex Onta, Executive Director, SINGUARD
Key Takeaways
- Personal connections see everything including years of history; bots see only post-start chats but carry zero account risk.
- Scalegram never sends from your personal account, which removes the main trigger Telegram penalises.
- Bots deliver pre-attributed leads via start parameters and host the AI assistant through official doors.
- Run both: one contact record per human, whichever connection saw them first.
Frequently Asked Questions
Is connecting my personal account safe?
Safer than the category's reputation, because Scalegram only reads: there is no bulk sending, which is the dominant ban trigger. A residual risk remains, Telegram's terms are what they are, and the connect flow requires acknowledging it. If zero risk is the requirement, run bot-only.
How far back does history sync go?
As far as your plan's history depth allows, syncing in polite paged batches until the window is filled. Deeper history is one of the natural reasons to sit on a bigger plan.
Can I connect several accounts and bots?
Yes, multiple of each per workspace within plan limits: useful for teams where each closer connects their own account, with every conversation feeding the shared pipeline.