A Discord auto responder bot watches for specific words or phrases in a message and replies automatically, without staff typing anything. "How do I pay" gets an instant payment guide, "refund" gets your refund policy, "!price" gets the price list - all before a human even sees the message. Noxyr's auto-responders live inside the ticket system and support three match modes, three scopes (tickets only, all channels, or a chosen list), and text placeholders that fill in per-user. This guide covers the setup that actually reduces repeat questions instead of misfiring.

A keyword is matched in chat, an FAQ auto-reply pops up, then a cooldown ring depletes and refills. Does anyone have the invite link? FAQ Here's our invite: discord.gg/noxyr

Match modes: contains, starts-with, exact

Every auto-responder is compared against the whole message, lowercased, so matching is never case-sensitive:

  • Contains (the default). Fires if the trigger appears anywhere in the message. Loosest option - a trigger of "pay" also matches "payment" and "paypal." Good for broad topics, risky for short words that show up inside other words.
  • Starts with. Fires when the message begins with the trigger. Suits command-like phrases such as "!price" or "how do i" without catching every mention of that phrase mid-sentence.
  • Exact. Fires only when the entire message is exactly the trigger, nothing more. The safest choice for short single words, since it can't accidentally catch a sentence that happens to contain that word.

Only the first responder that matches fires - one reply per message, never a wall of triggered responses stacking on each other.

Scopes: where a responder is allowed to fire

  • Tickets (default). Only inside ticket channels. This is the safest scope for support-style answers and the one to use for anything you don't want firing in general chat.
  • All channels. Every channel the bot can read. Fine for something universally useful like a rules link, risky for anything narrow.
  • Chosen channels. Pick specific channels - useful for a #help channel that isn't a ticket but gets the same repeat questions.

Outside ticket channels, a responder fires at most once every 15 seconds per channel, so a busy chat can't be turned into spam by one trigger word coming up repeatedly. Inside tickets there's no cooldown - a support conversation is one-on-one, so repeated legitimate questions should all get answered.

Placeholders that make it feel less canned

Responses can include placeholders filled in automatically when the reply sends:

  • {user} mentions the person who triggered it, {username} is their name without a ping.
  • {channel} and {userId} work on general (non-ticket) responders.
  • {ticketId} works on ticket responders, useful for "reference {ticketId} when you follow up."
  • {server} is the server name, for responses that get copied across multiple servers.

Anything the bot doesn't recognize is left exactly as typed, so a typo in a placeholder just shows up literally rather than breaking the message.

Setting one up

  • 1. Open the dashboard, go to Tickets → Auto-responders, and add one with a name, a trigger, a match mode and a response.
  • 2. Pick a scope. Start with Tickets if you're not sure - it's the lowest-risk option.
  • 3. Use the active toggle to pause a seasonal or promo-specific responder without deleting its history.

Changes can take up to about 15 seconds to apply since the bot caches the list briefly - if a just-saved responder doesn't fire immediately, wait a moment before assuming it's broken.

Where auto-responders can go wrong

  • Trigger words that are also common English. A contains-mode trigger of "help" will fire on nearly every support message. Use starts-with or exact for anything short and common.
  • Too many responders competing for the same words. Only the first match wins, so order and specificity matter - a broad "refund" responder can eat a message meant for a narrower "refund policy" one if it's checked first.
  • Using it as a substitute for staff instead of a filter. Auto-responders are for the questions asked constantly, not every question. A member with a real problem still needs a person; an auto-responder should reduce the volume of repeats staff have to type out by hand, not replace answering.

Messages from other bots never trigger a responder, and Noxyr's anti-spam check runs before auto-responder matching, so a message flagged as spam won't also fire a reply.

Auto-responders vs the FAQ command

These solve the same problem two different ways. An auto-responder fires the moment a trigger is seen - no effort from the member. An FAQ entry waits to be searched with /ticket faq - the member has to ask. Use auto-responders for the handful of questions that come up so often you want them answered instantly, and the FAQ for a longer library of answers members can browse or search on their own. Our FAQ bot guide covers that side in detail, and both live under the same auto-responders & FAQ docs if you want the exact reference.

Common questions

Can an auto-responder reply with an image or embed? Responses are plain text with placeholders; there's no separate embed builder for auto-responder replies.

Do auto-responders work if the Tickets module is off? No - both auto-responders and the FAQ belong to the Tickets module, so turning that module off stops them from answering anywhere.

Can I have more than one active at a time? Yes, there's no fixed limit mentioned in the setup - add as many as you need and use the active toggle to manage which ones are live.

Is this feature free? Yes, auto-responders are part of Noxyr's free ticket system.

Will it fire twice if two triggers match the same message? No, only the first matching responder replies per message.

Add Noxyr to start building your auto-responder list, or check the ticket bot page for everything else it does.