Tips & troubleshooting

The SecBot bot is a private, one-to-one channel. Your alerts come to you as DMs, tuned by the rules you set on the website. A few habits keep it useful.

Private chat only

The bot works only in a private chat with you. Group chats aren't supported: if you add the bot to a group, it replies that it only works in private chat and posts nothing there. Your alerts are tied to your own SecBot account and rules, so each trader links their own Telegram.

How bursts are handled

A busy name can match many events in a short window. SecBot has three protections against that:

• One DM per event. If several of your rules match the same event, you still get one message, from the first matching rule.
• Delivery pacing. Messages to you are paced, and the bot can combine a burst into a single message. When delivery is held back for pacing, the alert log shows it as throttled.
• Auto-pause. If one rule fires more than 15 times inside 10 minutes, SecBot pauses that rule and tells you on Telegram. The rule shows Auto-paused on the website's Alerts tab until you edit it or click Resume. Pausing protects delivery for your other rules.

Practical tips

• Mute when you step away. Send /mute to pause DMs and /unmute to bring them back. Your rules don't change. Alerts that match while you're muted are not sent later.
• Use quiet hours for regular downtime. Instead of muting every night, set a daily window under Delivery & quiet hours. Telegram DMs are skipped during that window.
• Check /status first. It confirms the link, your subscription, and mute state in one message.
• Tighten a noisy rule rather than muting. If one rule keeps getting auto-paused, raise its minimum impact score or narrow its events. See Alert rules.

The alert log has the answer

Every matched alert is recorded with what happened to it: sent, queued, failed, muted, skipped for quiet hours, or throttled. Check the alert log before you assume something went missing.

Related: Connecting and Command reference.