Overview
Event preferences filter activity before it is delivered to enabled channels. Telestars also scopes bot activity by membership and assignments, and hides financial events from roles that cannot view billing.
- Enable only the operational events that matter to your role.
- Understand the six visible preference groups.
- Recognize wallet top-ups as part of the financial alert family.
- Diagnose missing alerts caused by access scope rather than delivery failure.
Before you start
- An active Telestars workspace membership.
- At least one connected bot with a Telegram username when enabling Telegram delivery.
- A valid account email when enabling email delivery.
Step by step
- Open Notifications → Events and review the active count shown in the panel header.
- Enable Purchase for fan purchases and paid-media unlocks, and New Message for new conversations or unread fan replies.
- Enable AI Stopped for handovers that need review, New Fan for new audience entries, and Script Exhausted for completed script paths.
- If your role can view billing, enable Low Balance to receive wallet attention and wallet top-up financial activity.
- Review channel settings so each enabled event has at least one intended delivery destination.
- Trigger a safe test for the selected event and confirm that the authorized member receives it while out-of-scope members do not.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Event groups | The settings page exposes Purchase, New Message, AI Stopped, New Fan, Script Exhausted, and Low Balance preference rows. |
| Wallet top-ups | Wallet top-up notifications share the financial preference used for low-balance activity. |
| Financial access | Low-balance controls and financial events are hidden from members whose role cannot view billing. |
| Bot scope | Owners and admins can receive bot-scoped events across the organization; other members receive events for directly assigned bots or assigned creators. |
| Channel independence | Turning off an event suppresses it across in-app, Telegram, and email for that user, regardless of which channels are enabled. |
Verify the result
- The Events summary matches the number of enabled visible rows.
- A test event arrives for a member with the correct assignment and channel settings.
- Financial events remain unavailable to roles without billing access.
Troubleshooting
| If you see this | What to check |
|---|---|
| Low Balance is not listed | Your resolved role does not have billing access. An owner or admin must manage and receive financial alerts. |
| An assigned operator misses bot alerts | Confirm the direct bot or creator assignment and that both the event toggle and delivery channel are enabled for that member. |
| Too many email alerts arrive together | Disable noisy event categories or use in-app/Telegram for urgent monitoring. Email throttling reduces bursts but does not replace event selection. |
Best practice
Keep in-app alerts enabled as the audit trail, then add Telegram or email only for the events that require attention away from the dashboard.