Getting Help
QBXWatcher is the first responder in the QuickBox.IO Discord server. It never replaces a human — every support thread is read by the team — but it can often unblock you in the minute before someone arrives.
Support thread answers
Reads your thread and replies with a conversational, cited answer drawn from the docs, or says so honestly when it is unsure
/ask
Answers a question from the QuickBox documentation and lists its sources
/troubleshoot
Guided, symptom-led diagnostic for a specific app on your linked server
/help
Browse the application help topics and the bot command list
/quick-support
Turn temporary staff access to your server on and off yourself
Escalation
Suggests a better-fitting forum when a thread lands in the wrong lane
Posting a support thread
The Get Support forums mirror this documentation. There is one forum for each application category in the Applications catalog — Media Servers, Download Clients, Indexers & Trackers, and the rest — plus three general forums: Getting Started & CLI, Self-Hosting & Hardware, and Dashboard. Open a thread in the forum that best matches your problem.
QBXWatcher reads your opening post and, when it can help, replies almost immediately with a conversational answer drawn from this documentation and the QuickBox knowledge base. The answer is grounded and cited — it links the pages it drew from and shows a confidence rating — and it never invents. When it cannot find a confident answer it says so plainly, shows whatever it did find, and leaves the thread for a human.
| When | What it posts |
|---|---|
| It found a confident, sourced answer | A conversational reply that answers your question, cites the docs pages it used, and carries a confidence rating |
| It is not confident | An honest reply saying it could not find a solid answer, plus whatever it did find — never a guess |
| It could not tell what you are asking about | A holding reply asking for the exact command you ran, the error text, and which app is involved |
Follow-up questions in the same thread continue the conversation — QBXWatcher remembers what you have already discussed. Once a member of the team replies, QBXWatcher goes quiet and leaves the thread to the human, so it never talks over staff.
If the thread looks like it belongs in a different forum, the reply includes an Is this in the right forum? note suggesting where it might fit. That is a suggestion, not a move — your thread is answered either way.
The bot classifies your thread from what you wrote. Naming the app, quoting the exact error, and saying what you ran gets you a targeted first reply instead of a generic one — and it is exactly what the human who picks up the thread needs too.
Answers the bot posts in threads carry rating buttons. Using them tells us when an answer missed, which is how the knowledge base improves.
The Support Playbook covers which forum lane to choose, what to attach, and why bumping a thread pushes it down the queue.
Asking a documentation question
/ask query:How do I move rTorrent to a second disk?QBXWatcher searches the QuickBox knowledge base and this documentation site, then answers with the sources it used and a confidence rating.
| Option | What it does |
|---|---|
| query | Your question, between 5 and 500 characters. Required |
| tier | Minimum confidence required before an answer is shown — any (default), high, medium, or low |
If nothing clears the bar you asked for, the bot says so plainly rather than guessing, shows what it did find, and suggests rephrasing or asking a staff member.
Set tier:high when you are about to run something destructive. You will get fewer answers, but only well-sourced ones.
Browsing help topics
/helpOpens a private menu with two branches:
- Application Help Topics — the application browser described below
- Bot Commands List — search the commands you can run
Mentioning the bot with a help keyword opens the same browser, and adding a topic jumps straight to it:
@QBXWatcher help
@QBXWatcher help sonarrThe application browser
The browser opens on an alphabetical dropdown of every help topic — around 85 in total, covering both the QuickBox applications and the qb commands. Because Discord caps a dropdown at 25 entries, the list is paged, and each page button is labelled with the range it holds (for example Page 2: Duplicati – Kavita) so you can jump without hunting.
Two buttons sit under the dropdown:
| Control | What it does |
|---|---|
| The app dropdown | Pick any topic on the current page. Each entry shows its category underneath |
| Page buttons | Move between pages of 25. Labelled with the first and last topic on the target page |
| Browse by Category | Switch to a category list — pick a category, then an application within it |
| Search for Topic | Opens a search box and matches your text against every topic |
Search is forgiving. It matches an exact name first, then known synonyms, then close spellings — and it tells you which kind of match you got, so a result labelled suggestion is a guess you should sanity-check rather than a direct hit. If nothing matches it says so and points you back at the category browser.
Opening a topic also surfaces related topics, so a question about one application leads naturally to the ones it usually sits alongside.
The menus, buttons and prompts follow your language. The help articles themselves are written in English only, and the bot says so when it shows one.
Guided diagnostics
/troubleshoot app:sonarr/ runs a symptom-led diagnostic for one app. The app option is required and autocompletes from the QuickBox catalogue. After you pick the app, choose the symptom that matches:
| Symptom | Use it when |
|---|---|
| Can't start / service offline | The app will not launch, or its service is stopped |
| Running slowly / high CPU | The app responds but the box is straining |
| Permission denied errors | The app cannot read or write files it should own |
| Web UI unreachable | The service is up but the web interface does not load |
| Configuration question | You need to change a setting and want the right file and value |
What you get depends on whether you are verified and whether you linked a server:
| Your state | What /troubleshoot gives you |
|---|---|
| Not verified | Documentation-led guidance for the symptom you picked, plus a prompt to verify |
| Verified, no server linked | A prompt to run / so live checks become possible |
| Verified with a linked server | Live triage — service state, port health, and targeted recovery steps for your box |
The debug option dumps the raw status payload and is restricted to moderators and admins.
QuickSupport
QuickSupport is a temporary support account on your server that you switch on yourself when staff need to look at something directly.
/quick-support host:myserver status:true
/quick-support host:myserver enable:true
/quick-support host:myserver disable:true| Option | What it does |
|---|---|
| host | Which of your linked servers to act on. Required, autocompletes from your saved servers |
| status | Report whether QuickSupport is currently enabled |
| enable | Turn QuickSupport access on |
| disable | Turn QuickSupport access off |
| dm_staff_member | DM the connection details straight to a specific staff member instead of showing them to you |
You must pass at least one of status, enable or disable — the bot asks you to choose an action if you pass none. The command requires the Verified role and a linked server; if you have not linked one yet, the reply gives you a button to set that up.
QuickSupport exists for the length of a support session. Run / once the issue is resolved. Nothing else on your server changes when you toggle it.
The reply is private to you, and dm_staff_member sends the connection details by DM. Access details are never posted into a public thread.
Best practices
Do
- Name the app, quote the exact error, and say what you ran — in the first message
- Use the rating buttons on the bot's answer so we learn when it missed
- Try
/before opening a thread; it often names the causetroubleshoot - Use
/when you need a well-sourced answerask tier:high - Disable QuickSupport as soon as the session ends
Don't
- Do not open one thread for several unrelated problems
- Do not bump a thread — the queue is FIFO within each forum and bumps push you down
- Do not paste credentials, keys, or full config files into a public thread
- Do not treat a low-confidence answer as authoritative; rephrase or wait for a human
FAQ
Related pages
Join the Community
Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.
- Dedicated Support
- Feature Previews
- Community Configs
- Active Discussions