TicketQuill

Guide

How to set up a Discord ticket system

Right now people probably DM you for help, and you lose track of it. A ticket system gives each person a private channel instead — one your staff can see, and one that leaves a record you can look at later. This page shows you how to set one up, with a picture of every screen. It takes about ten minutes and works on the free plan.

A finished ticket panel in Discord titled Northwind Support, with Get help, Apply for whitelist, and Appeal a ban buttons.
This is what you are making: a message with buttons, posted in a channel you pick. A member clicks a button and their private channel opens.

Before you start

Four things to have ready

Set these up in Discord first. It is much easier than stopping halfway through to make them.

Setup

Nine steps, with a picture of every screen

  1. Add the bot to your Discord server

    Click "Add TicketQuill to Discord" at the bottom of this page. Discord asks which server you want it in — pick your server from the dropdown and click Continue. You have to be the owner of that server, or have the permission called Manage Server. Nothing to pay and no card.
    Discord’s authorise screen, showing what the bot may do and a dropdown to choose which server to add it to.
    Discord asks which server. Pick yours, then click Continue.
  2. Sign in to the website with Discord

    Go to ticketquill.com and click "Log in with Discord". There is no new password to make up. Discord just tells us who you are and which servers you are allowed to set up.
    The TicketQuill sign-in screen, with a single Log in with Discord button.
    One button. There is no TicketQuill password to create.
  3. Find the three pages you will be using

    Everything gets built on the website, down the left-hand menu. You only need three of them, and you use them in this order. Forms is where you write questions. Buttons is where you make the buttons people click. Panels is where you write the message that holds those buttons. None of it is live in Discord yet — you post it at the end with a command.
    The left-hand menu on the TicketQuill dashboard: Overview, Panels, Buttons, Forms, Library and Placements.
    The left menu. Forms first, then Buttons, then Panels.
  4. Write your questions on the Forms page

    Click Forms in the left menu. Any forms you already have are listed; scroll past them to "Create a form". Give it a name — the name is only ever seen by you. Then click "+ Add first question", type the question, pick what kind of answer you want, and click "Save questions" on the right. Skip this whole step if your buttons do not need to ask anything.
    The Forms page listing existing forms, with a Create a form card at the bottom.
    Forms you have already made are listed. "Create a form" is underneath them.
    The Create a form card: a Form name box, an optional description, a No questions configured notice, and an Add first question button.
    Name it, then click "+ Add first question".
    A form question in the builder: the question text, an answer-type dropdown set to Short answer, an optional example answer, and a Required checkbox.
    Each question has an answer type and an optional example. Discord shows up to five questions at a time.
  5. Make your buttons on the Buttons page

    Click Buttons in the left menu, then "Create a new button". Give it a name — this one people DO see — and pick an emoji and a colour if you like. Make one button per kind of request: "Get help", "Apply for whitelist", "Appeal a ban". Keep them separate, because that is what lets you send each kind to different staff later. If this button should ask questions, tick "Attach a form" and pick the form you made. Click "Create button", then do the next one.
    The Buttons page listing existing buttons with Edit links, and a Create a new button row at the bottom.
    Your buttons. "Create a new button" at the bottom opens the settings.
    The top of the new button form: a Button name box and a Panel dropdown set to Not attached.
    The name is what people see written on the button in Discord.
    The Attach a form checkbox ticked, revealing a Choose a form dropdown, with a Create button at the bottom right.
    This is where questions get attached: tick "Attach a form", pick your form, then "Create button".
  6. Write the message people see on the Panels page

    Click Panels, then "Create panel". A panel is the message that holds your buttons. Give it a name (only you see the name), then write the message your members read — say what happens after they click, and say that the channel which opens is private. Then go to step 2 of the builder, "Attach buttons", and add the buttons you just made.
    The panel builder on the website, on step 1 of 3, with a Panel name box and a larger box for the message members will see.
    Step 1 of 3. The name is for you; the message is what your members read.
    The panel builder listing two buttons attached to a panel: Get help and Apply for whitelist, each with a Remove from panel control.
    Step 2 of 3: add your buttons. Taking one off a panel does not delete it — it stays in your account for next time.
  7. Put the panel in a channel using /panel

    Now go back to Discord and click the channel you want members to use. Type /panel in the message box, but do not press Enter yet. A list pops up — click the TicketQuill one. Two boxes appear: "design" is the panel you just made, "target" is the channel. Fill both, then press Enter. The bot posts your panel there.
    The Discord command list showing the TicketQuill /panel command with design and target options.
    Type /panel and this appears above the message box. Click it.
    The /panel command staged in the Discord message box with design and target boxes, and a list of saved panel designs to choose from.
    Then fill the boxes. Discord offers your saved panels — click one.
  8. Tell each button where its tickets go using /setup workflow

    Type /setup workflow in any channel and click the TicketQuill one. Fill in four things: "ticket_type" is which button you are setting up, "category" is the folder the new ticket channels get made in, "transcript_channel" is where the saved copy of the conversation is sent when a ticket is closed, and "staff_role_1" is who is allowed to see and answer it. Press Enter. Then do it again for each button.
    The Discord command list showing the TicketQuill /setup workflow command with ticket_type, category, transcript_channel and staff_role_1 options.
    Type /setup workflow and click the TicketQuill one.
    The /setup workflow command staged in the Discord message box, with a list of this server’s buttons to choose from for ticket_type.
    Discord fills in the choices for you. Click your button, then move to the next box.
  9. Open a ticket yourself to check it works

    Click your own button, the way a member would. If you attached a form you get the questions first. A private channel should then open with your answers already in it and Claim and Close buttons at the bottom. Last thing: check an ordinary member cannot see it — easiest with a second account, or take your own staff role off for a minute and look again.
    The form as a member sees it in Discord: a pop-up titled Get support with two questions filled in and a Submit button.
    The questions come first, as a pop-up.
    A newly opened private ticket channel in Discord, showing the member’s form answers and the Claim and Close buttons.
    Then the private channel opens, with the answers already in it and Claim and Close for your staff.

Reference

Every box the two commands ask you for

You only need two commands, and Discord fills in most of the choices for you. This is what each box means if you get stuck.

CommandBoxWhat to put in it
/paneldesignThe panel you built on the website.
targetThe channel your members will click the buttons in.
/setup workflowticket_typeWhich button you are setting up right now.
categoryThe folder new ticket channels get created in.
transcript_channelWhere the saved copy is posted when a ticket is closed.
staff_role_1 … staff_role_3Who is allowed to see and answer it. You need at least one; you can add up to three.
ping_roleOptional. Who gets notified the moment one of these opens.
/subscribe—See the plans and upgrade. You do not need this to follow the guide.

Common mistakes

Four things people get wrong the first time

Free plan, no card

Set it up while this page is open.

Everything on this page works on the free plan, in as many servers as you like, with saved conversations delivered to your own Discord.