How to Turn the AI Off in a Discord Ticket Bot: Three Switches

Most servers that want the AI off do not want it off everywhere. They want it off on appeals, on staff applications, on the one category where the first thing a member needs is a decision from a person rather than an answer. That is supported, and it is a ten second change.

What trips people up is the shape of it. There is no single server-wide off, the AI's state lives on the ticket rather than on the server, and a switch you flip this afternoon does nothing at all to the tickets already open.

Can you turn the AI off in a Discord ticket bot?

Short answer: yes, at three levels, and there is no single switch for the whole server. A panel decides whether the AI answers in the tickets it opens. Any category on that panel can override it. And inside one ticket, a staff member can flip it either way with a command. Each one is free on every plan, including the free one.

The missing row is the interesting one. There is no server-wide off, and that is a design choice rather than a gap. A switch like that would either have to leave every open ticket alone, which is exactly what the panel switch already does, or reach into live conversations and change what they are halfway through. The second is not a setting. If you want the AI off across a Discord ticket bot install entirely, turning it off on each panel is the honest version, and on most servers that is one panel.

Where each switch lives

The panel switch sits in the panel's AI card, in the dashboard panel editor or through /panel. It is on by default, and it shares a card with the two settings it is genuinely related to: the reply cap, which is how many times the AI may answer before it hands the ticket to your team, and the responsible staff role, which is who gets pinged when it does.

The category switch has three positions rather than two, and the third one is the one to understand.

Leaving a category on Default is not the same as setting it to On. Default follows the panel, so if you later switch the panel off, every Default category goes with it. Setting it explicitly pins it, and it stays pinned whatever the panel does afterwards. The usual arrangement is a panel with the AI on, and the two or three categories that are about people rather than problems pinned to Off. Ticket categories and routing covers the rest of what a category decides.

Which switch wins, and when it is decided

A category overrides its panel when it is set to On or Off, and inherits when it is on Default. That much is what you would expect. The part that is not obvious is when the question gets asked.

It is resolved once, at the moment the ticket is created, and the answer is stored on the ticket. From then on the ticket's own flag is the only thing the bot reads before deciding whether the AI should answer. The panel and the category are not consulted again for the life of that ticket.

That is almost always what you want, because the alternative is the AI disappearing mid-sentence from conversations it is halfway through. It is worth knowing anyway, because it is the difference between "I turned it off and it is still answering" being a bug and being the design.

What a human reply does on its own

Most of the time the AI goes quiet, nobody touched a switch. The server setting called "Pause when your team steps in" is on by default, and with it on the first message from anyone who is not the person who opened the ticket ends the AI's turn there. Claiming the ticket counts. A saved reply counts. A message sent from the dashboard counts.

Two details in that sentence do real work. The first is that the AI only ever replies to the person who opened the ticket, and never to anybody else in the channel, which is true whether the setting is on or off.

The second is that the check is "not the opener", not "is staff". Somebody you pulled into a ticket with /ticket people to look at one detail stands the AI down by saying hello, and so does a second member added to a shared issue. If that matters to you, adding a person to a ticket is worth reading alongside this.

Whatever stopped it, the reason is recorded on the ticket, which is what /ticket ai reads back when you ask. What an AI support bot will not do lists the reasons it stands down on its own, and claiming covers the claim half, including how to stop claiming from ending the AI's turn at all.

Can you turn the AI back on mid-ticket?

Yes. /ticket ai again, and the card shows the current state and the reason before you flip anything, which is usually enough to decide: a staff member replying and the server running out of AI allowance are different situations and only one of them is worth undoing.

What comes back is the AI answering the member again. What does not come back is the part of the conversation it missed. The AI's record of a ticket is built from the member's messages and its own replies, and nothing else is ever sent to it. Everything your staff wrote while it was off never reached it, so it resumes from the last thing the member said to the AI, not from where your team left the conversation.

So re-enabling is the right move on a ticket where the AI was switched off by accident, or by a claim that turned out to be a glance at the channel. It is the wrong move on a ticket your team has been working for twenty minutes, where the person holding the context is already in the room.

Two things it deliberately does not undo:

That second row cuts both ways and is worth saying plainly. If the AI stopped because it hit the panel's reply cap and a staff member turns it back on, the cap will not stop it a second time in that ticket. The cap is a circuit breaker, not a budget.

The one case that recovers by itself is a ticket stopped because the server ran out of AI allowance. Topping up brings those tickets back on quietly, with no notice posted in any of them, because they were stopped by an accounting fact rather than a decision. What an AI ticket bot costs covers the allowance itself.

Will members notice that the AI is off?

Only if it stops in front of them.

A ticket that opens in a category with the AI switched off says nothing about the AI at all. No notice, no apology, no "the AI is unavailable here". It opens as an ordinary staff ticket, because the member never expected an assistant and telling them one is missing informs nobody. The same is true of a ticket opened while the server is out of AI allowance, which stands down silently for the same reason.

A conversation that stops halfway through is the opposite case and does get a message, because a member mid-answer would otherwise be waiting on something that is not coming. When the cause was the allowance running out, that message also pings the responsible staff role, since the AI going quiet is otherwise invisible to everyone except the person waiting.

The takeover message itself is yours to write. It is one of the panel's editable messages, and a server that would rather the handover be silent can empty it, in which case nothing is posted and the next thing the member sees is a human typing.

When switching the AI off is the wrong fix

The left column is policy and the right column is a symptom. The commonest one in the right column is the third: a server that wants the AI to open the ticket and then get out of the way does not want it off, it wants a reply cap of one or two, which hands over on a timetable instead of on a guess.

The second commonest is the first row, and it is worth being honest about. An AI that answers wrongly in your server is nearly always one that was never told the thing it got wrong, and the fix is teaching it rather than removing it. Switching it off is the right call while you do that, and a poor place to stop. Which tickets belong to AI and which to people is the longer version of that argument.