Overview
The notification bell is the in-dashboard activity feed. It groups recent events into conversations, purchases, and system activity, links conversation-scoped alerts to Fan Inbox, and keeps a per-user unread state.
- Review recent activity without leaving the current workspace.
- Filter notifications by operational category.
- Open the related conversation when one is available.
- Clear individual or all unread indicators.
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
- Select the bell in the dashboard navigation and review the unread badge and recent list.
- Choose All, Conversations, Purchases, or System to narrow the visible events.
- Open an unread row; Telestars marks that item read and opens its Fan Inbox conversation when a conversation ID is available.
- Use Refresh when you need an immediate fetch instead of waiting for the periodic update.
- Choose Mark all read when you have reviewed the queue, then confirm that the unread badge clears.
- Use the settings icon to open the Notifications page and adjust channels or event toggles.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Categories | Purchases have their own filter, new messages and new fans are Conversations, and handovers, script exhaustion, and wallet states are System activity. |
| Conversation routing | When event metadata includes a conversation, selecting the row opens that exact conversation in Fan Inbox. |
| Read state | Opening an unread item marks it read, while Mark all read advances the user’s read cursor for all accessible events. |
| Unread display | Large unread totals are visually capped in the badge while the API records that the count is capped. |
| Refresh | The bell refreshes periodically and also provides a manual Refresh action. |
Verify the result
- The filters show only the expected notification category.
- Opening a conversation event routes to the corresponding Fan Inbox thread.
- The item or global unread count updates after the read action.
Troubleshooting
| If you see this | What to check |
|---|---|
| The unread badge does not clear immediately | Use Refresh after the read action and confirm that the request completed before repeating it. |
| A notification opens Settings instead of a conversation | Only events with a conversation identifier can deep-link to Fan Inbox; other events open notification settings. |
| The list is empty | Clear the active filter, confirm in-app delivery and event preferences are enabled, and generate a permitted test event. |
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.