The first version of the Scalegram panel had more charts on it than the current one. That is usually how it goes. Someone asks for a number, it gets a tile, and eighteen months later the page is a wall of squares that nobody reads because no single square ever changed a decision.
What survived the trim was the set of numbers that come from things the system actually confirmed: a contact record that moved, a link that was clicked, a join that was verified, a purchase that arrived from a checkout or an integration. Everything that would have required guessing was cut, and the panel is shorter for it.
Contacts and stages
The pipeline view counts contacts by stage over the selected range. It is the closest thing to a sales report the product has, and its accuracy depends entirely on stage hygiene. A stage that people enter and never leave is not a metric, it is a landfill, which is why closed stages matter as much as active ones.
Because the CRM stores contact recency rather than message text, the panel can also tell you how much of the list has gone quiet and where it went quiet. That single cut is more useful to most operators than any conversion percentage, and the design decision behind it is explained in the no-message-storage article.
The funnel events
Four events carry the acquisition story: a click on a tracking link, a verified join, a registration, and a purchase with a value attached. Each one is a confirmed fact rather than an inference, and each one is fired to the connected ad pixels with its UTMs still attached so the platform learns from the same event you are reading. The plumbing is described in how conversion events are fired.
The gaps between those four numbers are where the reading happens. Clicks with few joins means the landing page or the channel promise is wrong. Joins with no registrations means the flow that greets a new member is not doing its job. Registrations with no purchases is a pricing or an objection problem, and it is the one operators most often misdiagnose as a traffic problem.
Why every time series is a line
Every chart in the panel that has time on the horizontal axis is drawn as a line. Bars are reserved for one thing, the ranked comparisons covered in reading the rank bars. The rule sounds cosmetic and is not.
Bars invite you to compare individual days against each other, which is exactly the wrong instinct for a business that runs on daily volumes small enough to be noisy. Tuesday being double Monday means almost nothing in a channel doing a handful of joins a day. A line shows the direction, which is the only signal at that sample size. Fixing the chart type fixed a class of bad conclusion we watched people reach in the first version of the panel, and it is now a house rule across every SINGUARD product.
None of these numbers are performance figures for trading. Scalegram measures messages, contacts, clicks, joins and purchases. Nothing on the dashboard says anything about how a trader's account performs, and no product from SINGUARD promises a result.
Ranges, and the clock they are cut on
Every range picker in the panel opens on Today. Not the last seven days, not a rolling twenty four hours, and not the server's idea of today. Today, cut at the midnight of whoever is reading the screen. An operator in Dubai and a partner in Bucharest looking at the same account should each see their own day, and a rolling window quietly mixes two days together and makes yesterday look different every time you refresh. The full argument is in why ranges default to today.
What the panel deliberately does not show
There is no message volume chart, because there are no stored messages to count the words of. There is no engagement score, because we could not define one that was not a guess dressed as a number. There is no revenue forecast, since forecasting from a Telegram funnel with weekly ad changes produces a confident line that is wrong in both directions.
There is also no combined figure that merges purchases from different integrations into one number without saying which came from where. A purchase synced from a checkout, one claimed from a Whop sale and one confirmed through a broker deposit check are three different events with three different confidence levels, and flattening them into one tile would hide the only thing worth knowing when the number looks odd. How each arrives is a separate subject, and each keeps its own label on the record.
The number that is not on the page
Operators ask for one metric more than any other: how many of my contacts are actually alive. There is no tile for it, because the answer depends on a definition only the operator can supply. Alive in a signals community that posts daily is a contact who spoke this month. Alive in a business selling a high value programme with a six week sales cycle is a contact who spoke this quarter. A single vendor definition would be wrong for most of the people reading it.
What the panel gives you instead is the cut. Filter contacts by stage and by how long they have been quiet, and the number you get is one you can defend, because you chose the threshold. That is the general pattern across the whole page: the product supplies confirmed counts and the operator supplies the judgement.
Reading it like an operator
The panel is worth ten minutes a week, not ten minutes a day. Look at the direction of the line, not the height of yesterday. Take the biggest gap between two consecutive funnel events and treat it as the week's single problem. Then go and read three actual conversations in Telegram, because the numbers say where to look and only the conversation says what happened.
Operators who do that consistently end up editing their flow copy rather than their ad budget, which is usually the cheaper of the two fixes and almost always the one that was needed.
"A dashboard tile is a promise that the number underneath it is true. We deleted every tile we could not keep that promise for, and the page got better."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- The panel only shows numbers built from confirmed facts: a stage that moved, a click, a verified join, a registration, or a purchase that arrived from an integration.
- Four funnel events carry the acquisition story, and the gaps between them tell you which part of the flow to rewrite.
- Every time series is drawn as a line so nobody reads meaning into one noisy day; bars are reserved for ranked comparisons.
- Range pickers default to Today, cut at the reader's own midnight, so two people in different countries each see their own day.
Frequently Asked Questions
Does the dashboard show how many messages my bot sent?
It shows activity in terms of contacts, stages and funnel events rather than message bodies. Scalegram stores no message content, so there is nothing to count words or transcripts against.
Why is there no engagement score?
Because every definition we tried was a guess presented as a number. The panel sticks to events the system confirmed, and leaves interpretation to the operator reading it.
Can the dashboard tell me which ad produced a paying customer?
Yes, when the tracking link and pixel setup are in place. The click, join, registration and purchase events carry their UTMs through, so a purchase can be attributed back to the campaign that produced the click.
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.