AI Support Bot vs Human Tickets: What Each Should Handle

The short answer

Ask one question about each message: could a wrong answer cost someone money or trust? If yes, a human answers. If the answer is a fact you have already written down, an AI can handle it.

Side by side

What to give the AI

• "How do I verify?" and "Where are the rules?"
• "What do you sell and how much?" when your catalog is written into the prompt.
• "How long does delivery take?" if you state the time.
• Basic how-to questions about your community, game or product.

What to keep human

• Money. Refunds, chargebacks and order disputes.
• Moderation decisions. "Why was I banned" needs a person who can look at the log.
• Upset or sensitive members. A fast reply is the wrong reply here.
• Anything new. If nobody documented the answer, the AI will guess.

How Noxyr combines the two

Noxyr's AI chat is off by default. Turn it on with /aichat setup and you can choose a channel where the bot answers every message, let it answer when mentioned, and add an AI Help button to new tickets. A system prompt (up to 1,500 characters from the command) tells it who it is and what to refuse. The setup details are in the AI chat docs.

In a ticket, the member presses AI Help, the bot asks them to mention it with the problem, and the reply lands inside the ticket. Staff still own the ticket. The ticket system handles claiming, closing and transcripts as usual.

Built-in guard rails: up to 6 AI replies per minute per server, replies capped at 2,000 characters, messages with @everyone or @here ignored, and a clear message if every AI provider is down. Each message is answered on its own, so multi-step troubleshooting should move to a human.

A sensible rollout

1. Write the facts first. Prices, delivery, rules, refund policy. Put them in the system prompt.
2. Tell it to escalate. "If unsure, tell the member to open a ticket."
3. Start in one channel. An ask-the-bot channel before you add AI Help to tickets.
4. Read the answers for a week. Fix the prompt where it guessed.
5. Add AI Help to tickets once the answers are reliable.

The message text goes to a third-party model. Do not turn AI chat on in channels where people post private information.

Signs your balance is wrong

Too much AI

Members open tickets saying "the bot told me X and it was wrong", or they stop using the AI channel and ping staff directly. Tighten the prompt, shorten the list of topics it covers and add a firm "I am not sure, open a ticket" rule.

Too little AI

Staff answer the same five questions all day, and ticket response times creep up. Move those five questions into the system prompt and send members to the AI channel before they open a ticket.

Hand-off that does not work

If the AI says "open a ticket" but members cannot find the panel, fix the panel, not the AI. Put the ticket panel and the AI channel next to each other and mention both in your rules channel.

Staff time, not just speed

The real gain from AI support is not the speed of one answer. It is that staff stop answering the same question for the tenth time and spend the day on tickets that need judgment. Track it: the ticket analytics guide shows how to see volume and response time, so you can tell whether the AI is really removing work or only adding another channel to watch.

Writing the hand-off line

Give the AI one sentence to use when it cannot help, so members are never stuck: tell the member which channel or ticket panel to use and that staff will take it from there. Keep it friendly and short. A bot that always knows where to send people feels helpful even when it does not know the answer.

Keep reading

Prompt writing and cooldown tips are in AI chatbot for Discord support, and the feature page is Discord AI chatbot. For the human side, see support ticket best practices.