Overview
The withdrawal card estimates the selected bot's Telegram Stars state from Telegram balance and transaction data. It is separate from the Telestars wallet, and Telegram remains the authority for actual availability and withdrawal.
- Distinguish Telegram Stars from Telestars wallet funds.
- Read available, pending, and next-unlock information for one bot.
- Verify the final withdrawal state in Telegram.
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
- Select one Telegram bot in the dashboard top bar because withdrawal status cannot be resolved from a combined account view.
- Open the withdrawal card and review the displayed available Stars, pending Stars, and current threshold.
- If a next-unlock time is shown, treat it as an estimate based on the transaction data currently returned by Telegram.
- Open the selected bot in Telegram only when the dashboard provides an enabled withdrawal action.
- Confirm the actual balance, eligibility, and next action inside Telegram before making a payout decision.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Separate balances | Telegram Stars belong to the selected Telegram bot; Telestars wallet funds cover Telestars product charges. |
| Bot-specific state | Available and pending Stars are calculated for the single bot selected in the top bar. |
| Estimate | The dashboard summarizes Telegram data but does not replace Telegram's final eligibility or payout controls. |
| Unavailable state | A missing bot token or unavailable Telegram balance can prevent the estimate from loading without changing historical sales analytics. |
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.