Invite
Add Resell Intel with the requested channel permissions. The bot never needs Administrator.
Bot field manual
From first invite to fine control.
Every command is a Discord slash command: type /, choose the command, and Discord walks you through its options. Configuration commands require Manage Server; read-only diagnostics are available to everyone.
First five minutes
The shortest path to your first live scan
Open setup
Run /help for a private next step, then /setup and choose the categories your server actually follows.
Map channels
Choose one destination for everything, or route each category to its own channel.
Test delivery
Run /test_alert. The labeled sample checks the mapped channel and bot permissions; it does not scan sources or test your thresholds.
Check new drops
Run /check_drops for an immediate scan of enabled sources. Already-posted drops are not reposted or edited, and one scan serves every configured server.
Read a quiet run
Zero alerts can simply mean nothing cleared your rules or every qualifying drop was already posted. Check /health for setup or source issues and /skipped for recent filtered products. For a deliberate replay, use /run_all_sources. It probes every registered live source and freshly reposts every qualifying route.
Measure alert quality
Members can choose Good lead, Bought, or Not useful on each live alert. /health shows the server's 30-day feedback summary; gross spread remains a model estimate, not realized profit.
Troubleshoot by symptom
Trace the signal before changing settings
Start with the row that matches what you see. These checks are read-only until a step explicitly tells a server manager to change a route, permission, or billing state.
Your server is missing from the control room
Sign in with a Discord account that owns the server or has Manage Server or Administrator. If you do not have either permission, ask the server owner to grant access, then sign in again.
The server appears, but bot controls are locked
Invite Resell Intel from the control room, then refresh after it joins. The invite requests channel permissions and slash commands; it never requests Administrator.
Setup is open, but no alert destination is ready
Run /setup and map at least one category. Mapping enables that category and its attached automatic sources; anything left unmapped stays off. Reopening setup preserves existing choices.
A test alert did not reach the mapped channel
Run /test_alert for that category. It reports a missing route or missing View Channel, Send Messages, and Embed Links permissions. Fix the bot role or channel override, then retry the sample.
/check_drops finished with zero new alerts
This can be normal: no new product cleared every rule, or qualifying products were already delivered. Use /health for route and source readiness, then /skipped for recent filter decisions. Do not use the exhaustive replay as a repair step.
Alerts are paused after a subscription issue
Open the control room, select the affected server, and choose Manage billing. After the subscription is active, run /resume; saved channels, thresholds, and filters remain in place.
Complete reference