AI vs Human Support in Discord: Which Tickets Go Where

Every version of this question is really two questions wearing one coat. There is the nervous one, will this replace my moderators, and the practical one, which of these tickets should it be touching at all. The first has a boring answer. The second is worth ten minutes of your afternoon.

What follows is our own split, the settings that produce it, and the part nobody warns you about, which is what happens to the tickets the AI leaves behind.

Is AI support better than human support?

Neither. They are good at different halves of a queue, and the halves barely overlap.

Read down either column and the same pattern shows up. One side is repetition, coverage and speed. The other is judgement, action, and being a person. Nothing here has to lose for the other to win.

The reason it matters commercially is that repetition is most of what arrives. Not all of it, and the ratio swings wildly by community, but the pile of tickets asking the same eight questions is real in almost every server past a few thousand members.

What the split actually looks like

Across more than 180,000 tickets over this bot's lifetime, roughly half closed with no human replying at any point. That number is live at /api/stats/global rather than typed into this page, so you can check it against the day you are reading.

It is a share, not a promise, and it is not spread evenly. Roughly, this is where tickets land:

The third row holds most of the value and gets expected the least. A bug report the AI worked through reaches a human with the version, the steps and the screenshot already in the channel, which is a different job from one that says "its broken".

Do AI ticket bots actually work has the fuller numbers, including the servers where this ratio collapses.

Who decides which one answers?

You do, in advance. This is where most comparisons of AI and human support go wrong. The split is not the AI weighing its own confidence mid conversation and deciding whether to bother you. It is a handful of settings, all resolved before the member has typed a word.

A category left unset inherits its panel, which is the sane default and the reason most servers only ever touch one switch.

When a bot should hand off to a human covers priority and role wiring properly.

What happens at the handover

Nothing dramatic, which is the point.

When a staff member claims the ticket or types in it, the AI posts a short note that it is standing down, and stops. Same channel, same conversation, nothing forwarded anywhere. Your staff member reads up instead of being briefed, because the whole exchange is sitting right there. If it turns out to be routine after all, /ticket ai enable puts the AI back on that ticket.

That last message is what switched the AI off. There is no button for it and no separate handover step, which is deliberate: the alternative is a queue full of tickets in an ambiguous state because nobody clicked the thing.

There is a second handover people forget to configure. Each panel sets the most answers the AI may give in one ticket, and on reaching that cap it does not simply go quiet. It posts a handoff and pings the responsible staff role, so a member going round in circles with a bot surfaces to a person instead of being left there. Wire no role and that ping has nowhere to land, which is the most common gap we see.

If you would rather the AI kept helping while your team works, that is the one setting to change, under Settings and then AI. It ships on because two voices answering one member is worse than one.

What the human half looks like afterwards

Here is the part worth planning for, and almost nobody says it out loud. The tickets that are left are harder.

The AI does not take a random half. It takes the repeatable half. What remains is exceptions, judgement calls, disputes and genuinely new problems, so the queue gets shorter and denser at the same time.

The first line is worth saying out loud to whoever reads your stats. Judge the change by average resolution time and you will conclude it went badly, when what really happened is that the ten second tickets left the sample. Judge it by volume, and by what the remaining tickets are.

The fourth line is a real cost rather than a quirk. If new moderators used to learn on easy tickets, they need something else to learn on now, and onboarding a new moderator is that problem solved deliberately. Spotting burnout early is the other half of it, because a shorter queue is not automatically a lighter one.

Which tickets should always go to a person

Short list. Money, access, safety, and anything the AI was never taught.

The first three are policy. Give them their own category with the AI switched off, and the ticket never passes through the wrong hands on its way to somebody who can act. The fourth is a setup gap rather than a limit, and it closes the evening you sit down with your five most common questions, which training it walks through.

There is also a list of things ours is simply not allowed to do, including committing your team to a response time and deciding a harassment case. What AI cannot do in support is that list in full, and how to structure the team around it is the staffing version of the same question.

How to set the line on your own server

That last step is the difference between a bot that plateaus and one that gets better. Nothing is learned in the background here: a closed ticket becomes training only when a person picks that one ticket, and only when staff corrected the AI inside it.

Measuring the result is easier than people expect, because the AI is not hidden inside your numbers. It appears as an ordinary row in the staff leaderboard, next to your humans, with the same handled and closed columns, so your own split is one screen rather than a spreadsheet. One thing to know before reading it: those windows count what finished in the period, not what opened in it. The leaderboard needs Manage Server and a paid plan, while basic ticket stats for the last seven days are free, which is enough to watch the volume move. Support analytics covers which figures are worth tracking at all.

Everything above is checkable. The live split sits at /api/stats/global, the plan limits at /pricing, and the machine readable version at /llm-info.