Overview
Telestars has two related billing layers. The organization wallet funds variable runtime and sales charges across the workspace, while each bot independently uses Free, Starter, or Pro with its own subscription and renewal state.
- Know which charges use the shared wallet.
- Understand that plans are selected per bot.
- Distinguish variable usage from recurring subscription billing.
- Find the current pricing and fee rules inside Billing.
Before you start
- An owner or admin role, because wallet, subscriptions, payment methods, and renewal controls are restricted billing data.
- At least one connected bot when you want to select or change a per-bot plan.
- A supported card or cryptocurrency when adding funds.
Step by step
- Open Billing and start on Overview to review the organization wallet balance, recent activity, payment method, and automatic-funding state.
- Open Subscriptions to see the plan, billing source, renewal state, and period information for each connected bot.
- Open Information to compare current plan features, monthly prices, and sales fee rules maintained by the product.
- Use History to trace deposits, subscriptions, paid-media fees, and adjustments independently of the summary cards.
- When diagnosing AI activation, check both wallet readiness and the selected bot’s product setup; a paid plan alone does not remove runtime prerequisites.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Shared wallet | One organization balance is used across the workspace’s bots for applicable variable AI, paid-media, and operational charges. |
| Per-bot plans | Free, Starter, and Pro are selected and displayed for each bot rather than as one organization-wide plan. |
| Separate billing layers | New paid-plan subscriptions normally use Stripe, while the wallet remains available for variable charges; legacy wallet-renewal plans can still appear. |
| Current values | Plan cards and the Information tab are the source of truth for live prices, feature access, fee rates, and any product-specific thresholds. |
| Access control | Owners and admins can view billing data; other roles do not receive access to the wallet and subscription workspace. |
Verify the result
- You can identify the organization wallet separately from every bot’s plan.
- Overview and History agree on the latest completed wallet movement.
- Subscriptions shows the billing source and next renewal action for the intended bot.
Troubleshooting
| If you see this | What to check |
|---|---|
| Billing is not accessible | Only owners and admins can view wallet, subscription, Stripe portal, and renewal data. Ask an authorized member to perform the action. |
| A balance or subscription did not update | Refresh Billing and inspect History. Card, crypto, and subscription payments may have different pending and confirmation states. |
| A payment action fails | Read the returned payment status, confirm the selected method and amount, then retry or use the alternative funding method shown in Billing. |
Best practice
Before making a change, record the bot name, current plan, billing source, and period end shown in Subscriptions. Those four values explain most renewal behavior.