Overview
Employee Statistics combines manual conversation activity, paid-media proposals, attributed purchases, revenue history, and shift context. Supervisors can choose a permitted team scope, while a chatter sees their own performance.
- Compare activity and revenue without relying on one metric.
- Read self and supervisor scopes correctly.
- Connect performance trends with the selected dates, bot, member, and shifts.
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 Employee Statistics and confirm the current bot and date range.
- When member selection is available, choose one chatter or clear the selection for the permitted team view.
- Compare Stars earned, Sales, Messages sent, Average price, and PPV sent for the same scope.
- Review Unlock Rate and Golden Ratio to separate purchase conversion from PPV proposal cadence.
- Inspect Revenue history and shift sections before discussing an individual performance change.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Manual messages | Messages sent by team members in the Fan Inbox for the resolved member and bot scope. |
| Unlock Rate | Attributed paid purchases compared with PPV sends in the report scope. |
| Golden Ratio | PPV sends compared with manual messages sent in the report scope. |
| Visibility | A chatter is limited to their own resolved results; supervisors see only the team and bot scope they are allowed to manage. |
Verify the result
- The selected bot and date range are visible before you compare any values.
- Revenue and conversion values are consistent with the visible paid-send and purchase activity.
- A zero value is treated as no recorded activity in the selected scope, not automatically as an error.
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.