Open a Telegram account that has been selling for a year and count the threads that end with your message. Someone asked what it costs, you answered, and then nothing. Someone said they would fund on Monday and it has been three Thursdays since. The pile grows quietly because nothing in Telegram ever marks a conversation as finished. It just scrolls down.
That pile is the cheapest inventory the business owns. These people found you, spoke to you, and stopped for a reason that was often boring: a busy week, a phone reset, a question you answered slightly too late. The work is deciding which of them to reopen and what to say, and that is a data problem before it is a writing problem.
What Scalegram knows about a thread that went quiet
Less than you might expect, on purpose. Scalegram stores no message content at all. There is no transcript table, no archive of attachments, no copy of what either of you said. What sits on the contact record is who the person is, the stage they are in, your tags and notes, anything synced in from a checkout or a broker integration, and two timestamps: when they last spoke to you and when you last spoke to them. The reasoning behind throwing the text away is written up in why the CRM stores no messages.
Recency plus stage turns out to be enough for this job. A revival decision needs to know where in the funnel the silence started, not the exact sentence that preceded it. And when you do need the sentence, the contact row deep-links straight into the real chat in your own Telegram app, which is the point of opening the conversation where it lives rather than reading a stale mirror of it.
Triage before you type
Sorting the pile by age is the wrong first move. Sort it by where it stopped. A silence at the first message and a silence after a pricing answer are different events with different correct responses.
| Where it went quiet | What the silence usually means | What the reopening message has to do |
|---|---|---|
| After the first reply | Curiosity, no intent yet | Give one concrete reason to care, then stop |
| After a price question | Sticker shock or comparison shopping | Answer the objection they never said out loud |
| After a stated intention to buy | Something practical got in the way | Remove the obstacle, offer a person, ask nothing else |
| After a complaint | They are annoyed and gone | A human writes it, or nobody writes it |
Saved views make this bearable at volume. A view for contacts in the pricing stage with no contact in fourteen days is a work queue. A view for contacts who reached a deposit intent and then stalled is a different queue with a different owner. Stage and tag hygiene is what makes those queues honest, and it is the difference between a work queue and a guess.
The rules that keep a revival from reading as spam
Scalegram has no broadcast button for exactly this reason. A revival is not a campaign, it is a set of individual messages that happen to be sent in the same afternoon, and the constraints on it are the ones that already govern follow-up behaviour.
One open thread per contact. If a nudge has gone out and gone unanswered, a second one is not queued behind it. Every message carries information the previous one did not, and if you cannot write a genuinely different second message, the correct configuration is one message rather than three. Timing is cut at the reader's clock, not yours, because a revival arriving at three in the morning local time is an alarm with a business attached.
Nothing in a reopening message may promise a result. In trading niches especially, a message hinting that money is waiting is the fastest way to a complaint you deserve. Trading carries a high risk of loss, and signals or copied trades are tooling, not financial advice.
What the bot may do here, and what it may not
An AI flow block can carry the routine half of this: reopening a first-message silence, answering the pricing objection with the exact wording you wrote, and moving the stage when the person replies. It answers in the contact's own language, which matters more on a cold reopening than anywhere else, because a phrase that reads as polite in English can read as pushy translated word for word.
The bot is hard-blocked from flirting, romantic framing and promises the business cannot keep, and those blocks matter most on old threads, where a model with no transcript to lean on is tempted to be charming instead of specific. Anything that grants access, costs money or reopens a complaint stops for a human. Where the line sits is described in handing a conversation to a person.
Knowing when to close it instead
The strongest rule in a revival programme is the one that ends it. Two unanswered reopenings is not indecision, it is an answer. Move the stage to closed and leave them alone. People come back on their own in Telegram far more often than they do in email, because your channel is still sitting in their list and your name is still in their search. That only works if the last thing they received from you was not a fourth check-in.
On a team, this needs enforcing rather than agreeing. Per area permissions run at read, add, write and delete level, so a new starter cannot quietly restart a sequence on an account a director has already closed. Per area permissions are the mechanism.
Measured properly, a revival programme is not judged on replies. It is judged on how much of the dead pile it correctly retires. A list of four hundred stalled threads that becomes forty live conversations and three hundred and sixty honestly closed records is a better outcome than four hundred threads still sitting there because nobody wanted to admit they were over.
"Nobody wants to reopen a dead chat because they think they need to remember what was said. You do not. You need to know where it stopped and how long ago, and then write one message that earns the reply."
— Alex Onta, Executive Director, SINGUARD
Key Takeaways
- Scalegram keeps no message text, so a revival runs on contact recency, stage, tags and notes, with a deep link into the real Telegram chat when you need the words.
- Sort stalled threads by where the silence started rather than by age, because a first-message silence and a stalled deposit need different messages.
- One open follow-up per contact, timing cut at the reader's local clock, and no message that promises a result.
- Two unanswered reopenings means the thread is finished: move the stage to closed and let the person come back on their own.
Frequently Asked Questions
Can Scalegram show me what was said in a conversation that went quiet?
Not inside the CRM, because no message text is stored. The contact record carries the stage, tags, notes and the timestamps of the last message each way, and a link that opens the real chat in your own Telegram app where the history has always been.
Can I mass-message every contact who went quiet?
No. Scalegram has no broadcast button by design. A revival is sent as individual messages under the same follow-up rules as everything else, with one open thread per contact at a time.
Should the bot or a person reopen an old conversation?
The bot can handle routine reopenings, in the contact's own language, using wording you wrote. Complaints, anything involving access or money, and high value accounts go to a person, and the handover rules decide that automatically.
About the Author
Alex Onta is an Executive Director at SINGUARD. He built eTrader, the terminal, the mobile apps, eTrader Broker, Copytrading, Business and Community, along with the worldwide clustered-server infrastructure it all runs on, with his brother Roman Onta helping on the design, and he leads that division today. Together with Roman he builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals, and the two of them carry worldwide compliance, payment processing and international business structuring side by side. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.