Auto-Respond
Create automated response rules that trigger based on message content, patterns, and conditions.
Auto-Respond enables you to automatically send responses when messages match certain patterns or keywords. Perfect for FAQs, rule enforcement, greeting messages, or automating common responses.
Creating Auto-Respond Rules
Basic Command Syntax
Example: /auto-respond create trigger: "what is the server" response: "Welcome! Check #rules for more info"
Trigger Types
Keyword Matching
Trigger when a message contains a specific keyword anywhere in its content. Case-insensitive and partial match.
Triggers when a message contains "hello" anywhere (e.g., "hello world", "say hello", "hello?")
Exact Match
Trigger only when the entire message exactly matches the trigger (after whitespace normalization).
Only triggers on standalone "!ping", not "!ping server" or "check !ping"
Regular Expression (Regex)
Use powerful regex patterns for advanced matching. Supports capture groups for dynamic responses.
Example: Message "user:John" captures "John" and can use $1 in response
Requires basic regex knowledge. Test patterns carefully before deployment.
Response Types
Text Response
Send a simple text message in response. Supports markdown formatting.
Embed Response
Send formatted embed messages with colors, fields, and rich formatting.
Reaction Response
Automatically react to the message with an emoji. Multiple reactions supported.
Combined
Combine text, embeds, and reactions in a single auto-respond rule.
Conditions & Filters
Channel Filter
Restrict rules to specific channels. Leave empty to apply globally.
Rule only triggers in #general or #support channels.
Role Filter
Restrict rules to users with specific roles. Supports multiple roles.
Rule only triggers if the message author has "Moderator" or "Helper" role.
Cooldowns
Per-User Cooldown
Prevent spam by limiting how often a user can trigger the same rule.
Same user cannot trigger this rule more than once per 60 seconds.
Global Cooldown
Limit how often a rule can trigger across the entire server (any user).
Rule can trigger at most once every 30 seconds, even with different users.
Managing Rules
/auto-respond list
Display all active auto-respond rules with IDs and configurations.
/auto-respond delete <rule_id>
Remove an auto-respond rule by its ID.
/auto-respond edit <rule_id>
Edit an existing rule's trigger, response, or conditions.
/auto-respond test <rule_id>
Test a rule to see if it works as expected before deploying.
Best Practices
- Start with keyword matching and progress to regex for complex patterns
- Always set appropriate cooldowns to prevent rule spam
- Test rules in private channels before deploying to public areas
- Use channel/role filters to target rules to appropriate audiences
- Document complex regex patterns for future reference
- Review and update rules periodically as server needs change