Almost every limit in software is a meter. Messages sent, contacts stored, seats occupied, events fired. Scalegram has none of those. Clients, tags, notes and conversations are unlimited, and the plan has exactly two countable things: up to 10 Telegram bots and up to 10 tracked websites.
People read those numbers and ask the wrong question, which is whether ten is enough. The better question is what a bot and a site each represent, because once that is clear most operators discover they need three of one and seven of the other.
What a bot is
A bot is a Telegram identity that talks to your audience with its own persona, its own facts and its own rules. Not a copy of a script, a separate presence with a separate name, a separate set of saved replies and a separate flow.
The four reasons operators need more than one are consistent. Different brands, because two businesses cannot share one voice. Different languages, when a market is large enough to deserve a bot whose persona and material are written natively rather than translated on the fly. Different products, where a signals audience and a course audience need different answers to the same question about price. And different stages, where a public entry bot and a private members bot behave nothing alike.
What does not need its own bot is a variation in tone, an offer that changed, or a seasonal campaign. Those are handled inside one bot by its persona, its facts and its flow blocks. Spinning up a second bot to run a promotion doubles the material you have to maintain and halves the consistency of what customers hear, which is a bad trade.
The expensive part of a bot is never the slot in the plan. It is the persona, the facts and the flow behind it, all of which somebody has to write and keep current. Ten is generous precisely because nine well maintained bots is already a lot of work.
What a tracked site is
A tracked site is a web property carrying the tracking code, so that a visit, a tap through to Telegram and everything that follows can be tied together with the UTMs intact. That is what makes it possible to say which campaign produced a paying customer instead of guessing, which is the whole argument in Telegram ad attribution.
Sites tend to be spent differently from bots. A single brand often runs a main site, two or three campaign landing pages, and a page per market. The hosted bridge pages that run on your own domain fall into this budget too, since each is a property with its own address, its own card and its own conversion path.
What does not consume a site is a path on a domain you have already connected. A domain with six landing paths under it is one property. Operators who assume otherwise plan for a limit they will never touch.
Allocating them for a real operation
Take an affiliate business running two brands in three languages. The naive plan is six bots, one per brand per language, and it is usually wrong. Language is a property of the reply, not of the identity: the assistant answers in the language the customer wrote in, so a second bot is only justified when the persona and the material genuinely differ, not merely the words. That business more often ends up with two or three bots and spends its allocation on sites instead, one per market landing page, because that is where attribution needs the separation.
The opposite case is an operator running several unrelated offers under different names with almost no web presence, driving traffic straight from ads into Telegram. They may use six or seven bots and two sites. Both shapes fit inside the same plan, which is the point of counting two things rather than metering everything.
The limits that are not there
It is worth naming what is uncapped, because the absence is the actual design. Contacts are unlimited. Conversations are unlimited, though none of their text is stored, only contact recency and the link back to the real Telegram chat. Team members are unlimited, with rights granted per area. Conversion events are not metered. Broadcasts are not metered.
That means the price does not rise when the operation works. Handling four times the volume next quarter costs what it costs today, and the only variable that moves is what your own AI provider bills you for the model you brought your key for.
What to do if ten is not enough
A retirement habit helps here. When a campaign ends, decide immediately whether its bot becomes part of the permanent lineup or is switched off, and record that decision somewhere your team reads. Bots do not decay visibly. One that quietly answers with a price you changed four months ago looks healthy from the outside and is doing damage every day, which is a larger problem than any limit in the plan.
Before asking for more, audit what you have. In our experience an operator who has run out of bots usually has two or three that duplicate each other, built during a campaign and never retired, still consuming maintenance nobody has budgeted. Merging those back into one persona improves the answers customers get, which is worth more than the slot.
If the count is genuinely short after that, it is a conversation rather than a hard wall, and the place to have it is with the current terms in front of you at scalegram.io. What we will not do is meter the things that are currently unlimited to sell you more of the things that are counted.
"If you have run out of bots, nine times out of ten you have three that should be one. The limit is not the constraint, the material behind each bot is."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- The plan counts two things only: up to 10 Telegram bots and up to 10 tracked websites. Clients, conversations, team members and events are uncapped.
- A separate bot is justified by a separate brand, product or audience stage, not by a language, since replies already come back in the customer's own language.
- A tracked site is a web property carrying the tracking code, and multiple paths on one connected domain count once.
- Running out of bots usually means duplicates built during old campaigns, and merging them improves the answers customers get.
Frequently Asked Questions
Do I need a separate bot for each language?
Usually not. The assistant replies in the language the customer wrote in, so a second bot is warranted only when the persona and the underlying material genuinely differ for that market, not when only the wording does.
Does every landing page use up one of the ten sites?
No. A tracked site is a web property. Several landing paths on a domain you have already connected count as one, while a separate domain, including a hosted bridge page on your own name, is its own property.
Is there a message or contact limit?
No. Contacts, conversations, team members and conversion events are not metered. The only variable cost is what your own AI provider charges for the key you connected.
About the Author
Roman Onta is an Executive Director at SINGUARD. He builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals side by side with his brother Alex Onta, and he helped on the design of eTrader, the division Alex built and leads. His ground is worldwide payment processing, AML compliance and the corporate structures brokers are built on, work the two of them carry together, shaped by executive roles in the UAE and international corporates. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.