Discord Auto Responder Bot: Replies to Trigger Words, Instantly

The questions that eat your day

Every support team has the same five questions. How do I pay, where is my order, what is your refund policy, when are you open, how do I verify. An auto responder answers them before a person reads the message, which leaves staff for the questions that really need judgment.

One thing to know first: auto-responders and the FAQ belong to the Tickets module. If that module is off, neither will answer anywhere.

Pick a match mode

Noxyr compares your trigger against the whole message in lower case, so capitals never matter. The match mode decides how strict the comparison is.

Only the first responder that matches fires, and only one reply is sent per message, so two triggers never stack into a wall of replies.

Pick a scope

Each responder has a scope that decides where it watches.

• Tickets is the default. It only fires inside ticket channels, which is right for support answers.
• All channels covers every channel the bot can read. Use it for something universal, like a link to the rules.
• Chosen channels limits it to the channels you pick, such as a public help channel that is not a ticket.

Outside tickets a responder fires at most once every 15 seconds per channel, so a busy chat cannot turn one word into spam. Inside tickets there is no cooldown.

Make replies feel less canned

Replies can include placeholders that are filled in when the answer is sent. Anything the bot does not recognize stays exactly as typed, so a typo shows up literally instead of breaking the message.

• {user} mentions the person, and {username} uses their name with no ping.
• {server} is the server name.
• {channel} and {userId} work on general responders.
• {ticketId} works on ticket responders only.

Create one

1. Open the dashboard, pick your server, and go to Tickets, then Auto-responders.
2. Add a name, a trigger, a match mode and the response.
3. Pick a scope. If you are unsure, leave it on Tickets.
4. Save. A change can take up to 15 seconds to apply, because the bot caches the list for a few seconds.

Each responder has an active switch, so a seasonal answer can be paused without deleting it.

Mistakes that cause misfires

A contains trigger on a common word like help will fire on nearly every support message. Use starts-with or exact for short, common words. A broad responder can also win over a narrower one, since the first match fires, so keep your specific triggers specific. Messages from other bots never trigger a responder, and the anti-spam check runs first.

Replies are plain text with placeholders. There is no embed builder for them.

Responder or FAQ

An auto responder answers by itself. An FAQ entry waits to be searched: members run /close faq and get matching answers privately. Use responders for the handful of questions that come up constantly, and the FAQ for a longer library. If you want a model to write answers for you instead, try the AI chatbot.

A starter set to copy

Begin with three responders and grow from there.

1. Payment help. Trigger: how do i pay. Mode: contains. Scope: tickets. Reply with your accepted methods and a link to the shop.
2. Price list. Trigger: !price. Mode: starts with. Scope: chosen channels, such as your help channel.
3. Hello. Trigger: hi. Mode: exact. Scope: tickets. Reply with {user}, staff will be with you soon, and a reminder to describe the problem.

Read each reply as a customer would. If it does not fully answer the question, rewrite it, because a half answer is worse than no answer. Review which responders fire most, then turn off the ones that fire at the wrong time using the active switch.

Next steps

See the auto-responders and FAQ docs and the auto responder guide for wording ideas, or the FAQ bot guide. It all sits inside the ticket bot. Add Noxyr to begin.