Overview
The main Dashboard is the fastest operational view of a selected Telegram account. Its KPI cards, daily revenue chart, recent sales, and revenue pace all follow the active account and date range.
- Read the four headline KPIs in the correct scope.
- Connect a period total to its daily revenue pattern.
- Distinguish recent confirmed purchases from general conversation activity.
Before you start
- Select the exact Telegram account you want to analyze in the dashboard top bar.
- Choose a date range that matches the business question you are answering.
- Allow real messages, paid sends, and purchases to occur before judging an empty report.
Step by step
- Open Dashboard and choose one Telegram account in the top bar, or use the available combined scope when you intentionally need an organization overview.
- Set the date range before reading Stars revenue, Average sale, Conversion, or New conversations.
- Review Stars by day and compare the chart total with the Stars revenue KPI for the same period.
- Inspect Recent sales to see the confirmed purchases that contribute to the selected view.
- Use Revenue pace to identify the strongest day and average daily pace without treating either as a forecast.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Stars revenue | Confirmed Stars purchase value recorded in the selected account and date range. |
| Average sale | Average Stars value of the paid purchases in the selected scope. |
| Conversion | Purchased paid offers compared with paid offers sent in the same scope. |
| New conversations | Conversations first recorded during the selected dates. |
Verify the result
- Changing the bot or dates updates every visible KPI and chart together.
- The daily chart total matches the period being reviewed.
- Recent sales show confirmed purchase activity rather than unsent or merely offered media.
Troubleshooting
| If you see this | What to check |
|---|---|
| A report is empty | Confirm the selected bot, date range, and whether qualifying activity occurred during that period. |
| Two reports show different totals | Check that both reports use the same bot, dates, metric definition, and attribution scope. |
| The latest data did not load | Use Retry and keep the last visible report separate from a failed refresh. |
Best practice
Keep the bot, dates, and metric definition fixed while investigating a change, then compare one variable at a time.