Modules System

Ticky features a powerful modular system that allows you to extend functionality beyond the core ticket management features. Each module can be enabled or disabled independently and configured to suit your server’s needs.

Overview

Modules are optional features that enhance Ticky’s capabilities. You can manage all modules from the Modules section in your server dashboard.

Accessing Modules

  1. Navigate to your server dashboard
  2. Click on Modules in the sidebar
  3. You’ll see an overview of all available modules

Available Modules

1. Points System

The Points System module allows you to award points to support team members when they claim tickets, creating a gamified experience and performance tracking.

Features

  • Automatic Point Awarding: Points are automatically awarded when a staff member claims a ticket
  • Leaderboard: View rankings of all team members with their points
  • Scheduled Leaderboards: Automatically post leaderboards to a channel on a schedule
  • Point Reset: Option to reset points when sending scheduled leaderboards

Configuration

  1. Enable the Points System module
  2. Configure Leaderboard Schedule:
    • Set the channel ID where leaderboards will be posted
    • Set a cron expression for the schedule (e.g., 0 0 * * 0 for weekly on Sunday)
    • Enable/disable point reset when sending leaderboard
    • Enable/disable the scheduled leaderboard

Cron Expression Format

The cron expression uses the format: minute hour day month dayOfWeek

Examples:

  • 0 0 * * 0 - Every Sunday at midnight
  • 0 12 * * * - Every day at noon
  • 0 0 1 * * - First day of every month at midnight
  • 0 */6 * * * - Every 6 hours

Viewing Leaderboards

You can view the current leaderboard directly in the dashboard. The leaderboard shows:

  • Rank
  • Username
  • Total points
  • Total tickets claimed
  • Last claimed date

2. Auto-Close

The Auto-Close module automatically closes tickets that have been inactive for a specified period, helping keep your ticket system organized.

Features

  • Inactive Detection: Automatically detects tickets with no activity
  • Warning System: Sends warnings before closing tickets
  • Custom Messages: Customize warning and close messages
  • Configurable Timeframes: Set how many days before closing

Configuration

  1. Enable the Auto-Close module
  2. Set Inactive Days: Number of days of inactivity before closing (default: 7)
  3. Set Warning Days: Days before closing to send warning (default: 3)
  4. (Optional) Set Warning Message: Custom message sent before closing
  5. (Optional) Set Close Message: Custom message sent when closing
  6. Enable/disable the auto-close feature

How It Works

  • The bot checks tickets periodically
  • If a ticket has been inactive for the specified number of days, a warning is sent (if configured)
  • After the warning period, the ticket is automatically closed
  • Tickets must be at least 1 day old before being considered for auto-closing

3. Auto-Responder

The Auto-Responder module automatically responds to messages in ticket channels when specific keywords are detected.

Features

  • Keyword Matching: Respond to exact keywords, phrases, or patterns
  • Multiple Match Types:
    • Exact Match: Matches the exact keyword
    • Contains: Matches if message contains the keyword
    • Wildcard: Supports * (any characters) and ? (single character)
  • Multiple Responders: Create unlimited auto-responders
  • Enable/Disable: Toggle individual responders on/off

Configuration

  1. Enable the Auto-Responder module
  2. Click Add New Auto-Responder
  3. Enter:
    • Keyword: The word or phrase to match
    • Match Type: Choose from Exact, Contains, or Wildcard
    • Response: The message to send when matched
  4. Click Add Auto-Responder

Match Type Examples

  • Exact Match: help matches only “help”, not “help me”
  • Contains: help matches “help”, “help me”, “I need help”
  • Wildcard: help* matches “help”, “help me”, “helpful”, etc.

Managing Responders

  • View all existing auto-responders in the list
  • Delete responders by clicking the trash icon
  • Responders are checked in order, and the first match triggers a response

4. AI Assistant

The AI Assistant module provides an intelligent AI-powered helper that can answer questions in ticket channels, powered by Groq AI.

Features

  • Intelligent Responses: AI-powered answers to user questions
  • Trainable: Add custom training data to improve responses
  • Multiple Triggers:
    • Respond when bot is mentioned
    • Respond to questions automatically
  • Custom System Prompt: Define how the AI should behave
  • Multiple Models: Choose from various AI models
  • Context-Aware: Uses ticket context and training data

Configuration

  1. Enable the AI Assistant module
  2. Configure System Prompt: Define the AI’s personality and behavior
  3. Select Model: Choose from available models:
    • Llama 3.3 70B Versatile (Recommended) - Best balance of quality and speed
    • Llama 3.1 8B Instant - Fast responses
    • Qwen 3 32B - Alternative high-quality model
  4. Set Temperature: Controls creativity (0.0 = focused, 2.0 = creative)
  5. Set Max Tokens: Maximum length of AI response
  6. Configure Trigger Settings:
    • Respond when bot is mentioned
    • Respond to questions automatically
  7. Click Save AI Configuration

Training the AI

To improve AI responses, add training data:

  1. Go to the AI Training tab
  2. Click Add Training Data
  3. Enter:
    • Question: The question or prompt users might ask
    • Answer: The expected answer
    • Context (Optional): Additional context for the AI
  4. Click Add Training Data

The AI will use this training data as context when answering questions.

How It Works

  • The AI only responds in ticket channels
  • It responds when:
    • The bot is mentioned (if enabled)
    • A question is detected (if enabled)
  • The AI stays on-topic about Ticky bot and ticket management
  • If asked about unrelated topics, it redirects users to ask human staff

Best Practices

  • Add training data for common questions
  • Keep system prompts clear and specific
  • Use lower temperature (0.5-0.7) for more focused responses
  • Regularly review and update training data

Module Management

Enabling/Disabling Modules

  1. Go to the Modules section in your dashboard
  2. In the Overview tab, you’ll see all available modules
  3. Toggle the switch to enable/disable a module
  4. Disabled modules won’t function until re-enabled

Module Configuration

Each module has its own configuration tab:

  • Points System: Configure leaderboard schedules
  • Auto-Close: Set inactive days and messages
  • Auto-Responder: Manage keyword responders
  • AI Training: Configure AI settings and training data

Important Notes

  • Modules are server-specific - each server has its own module settings
  • Disabling a module doesn’t delete its configuration
  • You can re-enable modules at any time
  • Some modules require additional setup (e.g., Groq API key for AI Assistant)

Getting Started with Modules

  1. Start Simple: Enable one module at a time to understand how it works
  2. Configure Properly: Take time to configure each module’s settings
  3. Test Thoroughly: Test modules in a test server before using in production
  4. Monitor Performance: Check module logs and performance regularly
  5. Update Regularly: Keep training data and configurations up to date

Troubleshooting

Module Not Working

  • Ensure the module is enabled
  • Check module configuration settings
  • Verify you have admin permissions
  • Check bot logs for errors

AI Not Responding

  • Verify Groq API key is set in bot environment
  • Check if AI module is enabled
  • Ensure trigger settings are configured
  • Check if message is in a ticket channel

Auto-Close Not Working

  • Verify tickets are old enough (minimum 1 day)
  • Check inactive days configuration
  • Ensure auto-close feature is enabled (not just the module)

Auto-Responder Not Triggering

  • Check keyword spelling
  • Verify match type is correct
  • Ensure responder is enabled
  • Check if message is in a ticket channel

Next Steps