Run a prop firm for a month and the shape of the inbound becomes obvious. There is a large, repetitive band of pre-sale traffic: what the daily loss limit means, whether news trading is allowed, what happens over the weekend, how long a payout takes, whether the fee comes back. Then there is a much smaller band that is genuinely specific: a trader disputing a breach, a payout that has not landed, somebody who wants to argue about a rule interpretation on their own account.
The first band is answerable from documents you have already written. The second must never be answered by a machine. Scalegram is built around exactly that split.
The rules are seeded, not improvised
A model left to answer prop firm questions from general knowledge will confidently invent a drawdown rule, and a trader will screenshot that answer during a dispute. So the bot does not work from general knowledge. Your rules, your programme names, your fee treatment and your policy language are seeded as facts, and the bot answers from that set. It is the same discipline as writing a support macro, and it is covered in setting up pricing and policy into a bot and facts and snippets.
When a rule changes, you change the fact once. The alternative, which most firms live with, is a Telegram admin quoting an old limit from memory at midnight.
Anything contested goes to a person
The handoff is the feature that keeps this safe. A conversation that moves outside the seeded material, or that touches an account decision, is handed to a human, and the bot stops talking rather than filling the gap. When a member of your team types into the chat, the bot pauses on its own so nobody gets two answers to the same message. The mechanics are in handing a conversation to a human.
A bot must never tell a trader they passed, that a breach will be reversed, or what they can expect to earn. Those are firm decisions and firm liabilities. Scalegram blocks promises the business cannot keep at the message level, which is the only place a block actually holds.
The challenge was bought on your checkout, and the community still knows
Prop firm sales almost never close inside Telegram. The conversation happens there, the card is entered on your own checkout, and the two records sit apart. Scalegram matches confirmed purchases back to the contact, so the person who asked three questions on Tuesday and bought on Thursday is one record rather than two guesses, and the purchase value goes back to your pixels with the campaign parameters that produced it.
For a firm buying paid traffic, that is the difference between optimising against a Telegram join and optimising against a sold challenge. The join is a vanity number.
Community access with a condition attached
Plenty of firms run a members-only room for funded traders or for buyers of a particular programme. Doing that by hand means an admin cross-checking a name against a dashboard, which is slow and gets skipped under load. Scalegram issues access off a verified condition instead: a confirmed purchase, or a broker-side check where the programme runs on a live account. Nothing is granted because somebody said they qualified.
Support staff, permissions and one place to connect
Prop firms hire community managers early and hire them cheaply, which makes access control a real question rather than a theoretical one. Permissions are per area and per action: read, add, write, delete, granted separately. A community manager can answer and file without holding the ad account, the pixel connection or the checkout integration.
All of those connect on one Integrations page and nowhere else. Every other screen picks from what is already connected, which means there is exactly one list to review when somebody leaves. See everything connects on the Integrations page.
What Scalegram is not
It is not a rules engine and it does not watch trades. It cannot decide that an account breached, it does not read positions, and it has no opinion about consistency rules or news windows. That work belongs in the firm's own platform and risk stack, and for firms running on our software that is the Prop Firm CRM rather than this. Scalegram sits in front of it, on the sales and community side, where the questions arrive.
The other thing it does not do is keep your conversations. No message content is stored at all. The record is a contact, its recency and a link into the real Telegram chat, which for a firm holding a lot of upset traders in a lot of chats is a smaller liability than an archive would be.
The community side, which most firms underrate
A prop firm's Telegram community is an acquisition asset and a retention asset at the same time, and it is normally run as neither. People join during a promotion, ask their questions, buy or do not, and then sit there quietly for months while the firm treats the group as a broadcast channel for discount codes.
What changes with a pipeline underneath is that the group stops being anonymous. A person who asked about the two-step programme in March and never bought is a contact with a stage rather than a name in a member list, and the next campaign can reach them as a conversation instead of a mass post. Tracking links carry the campaign parameters into that conversation, so the firm can also see which creative filled the room in the first place. Broadcasts still have their place, and the distinction between the two is worked through in broadcasts compared with one to one DMs.
None of this changes the trading side of the business. A challenge is still passed or failed by the rules engine, payouts are still a firm decision, and no piece of community tooling should be allowed near either.
"Ninety per cent of a prop firm's Telegram traffic is six questions about the drawdown rule. The other ten per cent needs a human, and the whole trick is telling them apart quickly."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- Repetitive pre-sale questions are answered from rules you seeded, so a bot cannot invent a drawdown limit a trader will screenshot later.
- Contested cases and account decisions hand off to a human, and the bot pauses the moment a teammate types into the chat.
- Confirmed challenge purchases made on your own checkout are matched back to the Telegram contact, with the value reported to your pixels.
- Scalegram does not watch trades or judge breaches; that belongs in the firm's platform and risk stack, not in a community tool.
Frequently Asked Questions
Can the bot decide whether a trader breached a rule?
No, and it should not. It answers rule questions from the text you seeded. Account decisions, breaches and payouts are firm decisions and are handed to a person.
Does it replace a prop firm CRM?
No. It runs the Telegram sales and community layer in front of the firm. Challenge accounts, risk rules, payouts and audit trails belong in the firm's own platform.
What happens to the chat history of a dispute?
It stays in Telegram. Scalegram stores no message content, only that a contact exists, when they last made contact and a link back to the real conversation.
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.