Skip to content

One command and you are live.

Run /setup in your server. It builds everything a working ticket system needs and publishes it. Nothing to configure first.

/setup

Takes a couple of seconds. Only you see the reply.

Not added it yet? Add to your serverOpen the dashboard

What the command builds.

In this order, so you know exactly what is about to appear in your server.

  1. A staff role

    If you already have one called support, staff, helper, team, moderator, mod or admin, it uses that. Otherwise it makes one. That role gets access to tickets.

  2. A private Tickets category

    Where every ticket channel is created. Hidden from members, visible to your staff role. An existing one is reused, never duplicated.

  3. A panel channel everyone can see

    Public to read, locked so nobody can chat in it. The ticket panel lives here, so people know where to go.

  4. A ticket panel, already published

    The menu your members click to open a ticket. Live immediately. You do not have to publish anything yourself.

It never edits channels, roles or messages other than these.

Publishing that panel also turns Premium on for 14 days.

Once per server, the moment its first panel goes live. No card, nothing to cancel, and a message 3 days before it ends.

Before you run it.

You need
Manage Server, in the server you run it in.
The bot needs
Manage Channels and Manage Roles. The invite asks for both, so this only matters if someone unticked them or a role change removed them later.

Opened, answered, closed.

A ticket, from the button to the transcript. None of this needs configuring.

  1. A member clicks a button on your panel

    If that category has a form, they answer it first and the answers open the ticket.

  2. A private channel opens

    Visible to the member, your staff and the bot. Nobody else in the server can see it.

  3. The AI answers first

    From what your staff taught it. About half of all tickets end here with no human involved.

  4. It escalates when it should

    One staff role gets pinged, with a short summary and a priority. Never just because someone is annoyed.

  5. Staff take over

    The moment a staff member replies, the AI stops talking in that ticket.

  6. Closing saves a transcript

    The channel is deleted, the transcript stays at a link, and the member gets that link by DM.

Three things worth doing next.

Your server already takes tickets. These make it good rather than working.

If it does not work.

Four things stop it, and it tells you which one it hit.

It says the server is already set up
/setup only runs on a server with no panels, so it can never overwrite what you built. For another panel, use /panel.
It says it is missing permissions
The bot lacks Manage Channels or Manage Roles. Check its role in Server Settings, or re-invite it with the link above, which asks for everything it needs.
It could not create a channel or a role
A Discord limit, not a bug: 500 channels, 250 roles, or the bot role sits too low to create one. Free up room or move the role higher, then run it again.
I cannot find the command when I type slash
Your Discord app is caching its command list. Fully restart Discord and it appears. On mobile, force close the app.

Before you start.

It reuses rather than replaces. An existing staff role, Tickets category or panel channel gets used as it is, and it never touches your other channels, roles or messages. If your server already has a ticket panel it refuses to run at all.

No. Setup, panels, tickets, transcripts and the AI all work on the Free plan. What the paid plans change is how much AI usage you get and which extra features are unlocked.

It starts on its own when your server publishes its first ticket panel, which is the last thing /setup does. You get every Premium feature for 14 days. There is no card involved, so nothing can be charged and there is nothing to cancel. We message you 3 days before it ends and again when it does, saying which features turned off. The server then drops back to the Free plan and keeps every panel, transcript and thing you taught the AI. One per server, and a server already on a paid plan does not get one.

Yes. The dashboard can create and publish panels too, and gives you more control over how they look. /setup is simply the fastest route to a working server.

Then do not migrate. Keep it, and connect our AI to the tickets it already opens. That is a different one-command setup and it is on the connect page.

Open /panel, pick the panel and delete it there, then delete the category and channel in Discord as you would any other. Nothing is hidden anywhere else.

It’s not just an AI, it’s your AI.

That is the whole setup.

Run it, teach the AI what it should know about your server, and you are done.

/setup

Already running another ticket bot? Keep it and connect the AI instead.