Ask an operator how many follow-ups they send and you get a number: two, three, five over ten days. Ask what the second one says and you usually get the same answer as the first, with a question mark on the end. That is the actual spam problem. It is not frequency, it is repetition, and no scheduling tool fixes it because scheduling tools are built to repeat.
Scalegram's follow-up behaviour is shaped by a constraint most tools do not have: there is no broadcast button, and there never will be. The reasoning is written up in why Scalegram never mass-sends, and the short version is that a Telegram account that fires identical text at a list is an account with a short life. Everything below is what you do instead.
Recency is the only timing signal you need
Scalegram stores no message content. What it does store is when a contact was last in touch, which stage they sit in, and the tags and notes you or the bot put on them. That sounds like less to work with. In practice recency plus stage answers the only question a follow-up rule really asks: has this person gone quiet at a point in the funnel where quiet means something.
Quiet at the first message is not the same as quiet after a pricing question, and quiet after a pricing question is not the same as quiet after they said they would fund on Friday. Three different silences, three different responses. A tool that only knows "last contacted 6 days ago" treats them identically, which is how a warm buyer gets the same nudge as a tyre-kicker.
One open thread per contact
The rule that prevents most of the damage: a contact may have exactly one follow-up outstanding at a time. If a follow-up has been sent and not answered, another one is not queued behind it. This sounds obvious until you have two flows running, or a flow and a person, and the lead receives two nudges within an hour from what they think is one company. Scalegram tracks whether a follow-up for that thread has already gone out and does not send a second one on top of it, which is the same class of protection as the duplicate reply guards on the reply path.
Every follow-up carries new information
Write the flow so each step has a reason to exist. The first follow-up answers the objection the conversation ended on. The second offers a different route: a call, a document, a person. The third, if you send one, closes the loop honestly and says you will stop. If you cannot write a second message that is meaningfully different from the first, the honest configuration is one follow-up, not three.
Because the bot answers in the contact's own language, this discipline has to survive translation. A follow-up that reads as a polite check-in in English can read as pushy in another market, which is one more reason to keep the count low and the content specific.
The clock belongs to the reader
A message that arrives at 03:00 local time is not a follow-up, it is an alarm. Timing rules should be written against the person receiving them, and quiet hours are worth setting even when they cost you a few hours of speed. The same principle governs every date range in the product: a range picker cuts at the reader's midnight, not the server's.
Nothing in a follow-up may promise a result. Bots are blocked from making promises the business cannot keep, and no follow-up in a trading context should suggest that money is waiting. Trading carries a high risk of loss, and signals or copied trades are tooling, not financial advice.
Know when to stop
The strongest rule in the set is the one that ends the sequence. A contact who has not replied to two follow-ups is not undecided, they are done, and the correct action is to move the stage and leave them alone. They can come back on their own, and in a channel like Telegram they often do, because your channel is still in their list. That only works if the last thing you sent was not the fourth "just checking in".
Stage hygiene is what makes this bearable. If closed-lost is a real stage that people actually get moved into, the pipeline stops filling with ghosts and your saved views stay honest. The mechanics of stages, tags and views are covered in Telegram lead management.
The channel decides the tolerance
One more thing worth saying out loud, because operators moving from email get it wrong for a month. Telegram is a personal space. An email in a promotions tab is ignored at no cost to you. A Telegram message arrives on a lock screen next to messages from family, and the reaction to an unwanted one is not indifference, it is annoyance, and annoyance in Telegram has a button attached to it. Whatever cadence you would run over email, halve it and make each remaining message better.
Where the human belongs
Handover rules matter more in follow-ups than anywhere else, because a silence is ambiguous and a bot resolving ambiguity is a bot guessing. Route the high-value threads to a person after the first unanswered nudge. On a team, per area permissions decide who can write into those threads at all, at read, add, write and delete level, so a new starter cannot quietly restart a sequence on an account that a director has closed.
The measure of a good follow-up system is not how many messages it sends. It is how many contacts it leaves alone correctly.
"The question is never how many follow-ups you are allowed to send. It is whether the second one gives the person something the first one did not. If it does not, you are just reminding them to block you."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- Repetition is the spam problem, not frequency: if the second message says what the first said, send one message.
- Contact recency plus stage is enough to time a follow-up, and it is all Scalegram keeps, because message content is never stored.
- One follow-up may be outstanding per contact at a time, so a lead never gets two nudges from two flows within the same hour.
- The rule that protects the account most is the stopping rule: after two unanswered follow-ups, move the stage and leave the person alone.
Frequently Asked Questions
Can Scalegram send a follow-up to my whole list at once?
No. There is no broadcast or mass-send function, by design. Follow-ups happen inside a conversation with one contact, which is what keeps a Telegram account out of the pattern that gets accounts restricted.
How does it decide who is due a follow-up if it does not read the chat?
From the contact record: the stage, the tags and when that person was last in touch. Message content is never stored, and recency plus stage is enough to tell a cold first message apart from a stalled deal.
What stops two flows from messaging the same person twice?
A contact can only have one follow-up outstanding at a time. If a nudge has gone out and has not been answered, another one is not queued behind it.
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.