Browse documentation
    bbradar Pro guide

    Set up Pro notifications

    Understand Telegram, Discord, event streams, opportunity and dupe-risk filtering, and which setup fits your workflow.

    5 min read

    Choose a channel

    Telegram — personal alerts
    Private direct messages filtered by your own notification rules. Telegram is the best choice when you want selected platforms, program tiers, target scores or labels, dupe-risk levels, rewards, or change types.
    Discord — shared Pro access
    A Pro role in the bbradar community server with shared channels. Discord messages are not personalized by your Telegram notification rule.
    Capability
    Delivery
    Telegram
    Private 1:1 bot chat
    Discord
    Shared server channels
    Capability
    Personal filters
    Telegram
    Yes
    Discord
    No
    Capability
    Connection
    Telegram
    Single-use bot start link
    Discord
    Discord OAuth and server role
    Capability
    Best for
    Telegram
    Focused, actionable alerts
    Discord
    Community and broad shared updates

    Choose event streams

    Stream
    New
    What it means
    A newly launched current program.
    Default
    On
    Stream
    Upcoming
    What it means
    A future-dated program visible to Pro.
    Default
    On
    Stream
    Older
    What it means
    An existing program discovered after its launch.
    Default
    On
    Stream
    Suspended
    What it means
    A program became unavailable or inactive after stability checks.
    Default
    On
    Stream
    Reactivated
    What it means
    A previously inactive program returned.
    Default
    On
    Stream
    Target changes
    What it means
    Material additions, updates, re-additions, and confirmed removals.
    Default
    On
    Stream
    Repository changes
    What it means
    A monitored GitHub branch head changed.
    Default
    Off — opt in

    Delivery behavior

    Alerts are delivered from durable queues, so ingestion does not wait on Telegram or Discord. Transient Telegram failures are retried under global and per-chat rate limits. If Telegram reports that the bot is blocked, the chat is disabled until you reconnect.

    Target and repository notifications are separate streams. Browser WebSocket refreshes are not a durable notification transport, and repository events are not currently pushed to the browser over WebSockets.