Submit FAQ

Contribute Knowledge

Help improve our AI support by submitting FAQ entries. Your submission will be reviewed by an admin before being added to the knowledge base.

How to Submit an FAQ

When a customer asks a question or encounters an error, the bot searches its knowledge base. By adding FAQs, you help the bot respond instantly without using AI.

Field Explanations

  • Product: Select which DUSA product this FAQ is about.
  • Question / Trigger Phrase: The question customers might ask. The bot matches this text.
  • Error Patterns: Error messages that should trigger this FAQ (comma-separated).
  • Answer / Solution: The detailed response the bot will give.
  • Notes: Internal notes for the admin reviewer (not shown to customers).

Example Submissions

Example 1: Common Question
Product: DUSA Tablet
Question: How do I change the tablet keybind?
Error Patterns: (leave empty)
Solution: To change the tablet keybind, open config.lua and find the Config.OpenKey option. Change it to your preferred key (e.g., 'F5' or 'F6'). Save the file and restart the resource with /ensure dusa_tablet.
Example 2: Error-Based FAQ
Product: DUSA Mechanic
Question: Why do I get a database error when opening the mechanic menu?
Error Patterns: SCRIPT ERROR: @dusa_mechanic, attempt to index a nil value, oxmysql error
Solution: This error occurs when the database tables are not created. Run the SQL file located at dusa_mechanic/sql/install.sql in your database. Make sure oxmysql is properly configured in your server.cfg with the correct database credentials.
Example 3: Framework Compatibility
Product: DUSA Bridge
Question: Is DUSA Bridge compatible with QBCore?
Error Patterns: framework not detected, QBCore not found
Solution: Yes, DUSA Bridge supports ESX, QBCore, and QBOX frameworks. Make sure dusa_bridge starts AFTER your framework in server.cfg. The bridge auto-detects your framework. If detection fails, you can manually set it in config.lua with Config.Framework = 'qb' (options: 'esx', 'qb', 'qbox').

FAQ Details

The question customers typically ask. Be specific and use natural language.
Comma-separated error messages. The bot will match these when customers share error logs.
Write as if you're directly answering the customer. Be clear and include specific steps.
These notes are only visible to admins during review, not to customers.