Set it up · Support server · All our bots

Support tickets in your members' DMs

This is Ayako's ticket system as its own bot. Members can open a Discord support ticket in their DMs. Staff answer from a private thread in your server. Start with /settings ticketing.

Add to Discord

13 permissions · 47 settings · 10 logged events · 8 ticket events shown in transcripts

Set up in 3 steps

1. Run /settings ticketing and create a ticket system.
2. Pick a type: Thread, or DM to Thread for tickets in DMs.
3. Pick the channel where the threads open.

What you get for free here

This is the same ticket system the main Ayako bot runs: tickets in DMs, support levels, saved replies, transcripts. The main Ayako bot also moderates servers. This bot only does tickets, and it asks for no moderation permissions.

Everything it does

• Tickets inside DMs. The member writes to the bot in DMs. The bot copies the conversation into a private thread. Staff answer there, and the member gets the reply in DMs.
• Staff notes in the same thread. Start a message with the reply prefix, and the bot sends it to the member. A message without the prefix stays staff-only.
• Edit a message to take it back. Remove the prefix from a message you already sent. The bot deletes the member's copy and removes the delivery mark.
• Support levels. Each level has its own staff roles. The bot pings them when a ticket reaches that level.
• Move a ticket up. The ticket gets a new forum tag, or it moves to a new thread. The bot closes the old thread and saves a transcript of it.
• Saved replies with two versions. One version for the member, one only staff can see. The bot fills in {{user}}, {{staff}}, {{claimer}}, {{server}}, {{kind}} and {{ticket}}.
• Private staff threads. On Thread tickets, staff get an extra thread just for them. The member never sees it.
• Reminders that warn first. The bot reminds staff about tickets nobody claimed and tickets with no new messages. It always warns before it closes a ticket.
• Transcripts. The bot builds a transcript from everything it saw, and sends it when the ticket is deleted. It marks 8 kinds of events, for example created, claimed or closed.

Commands

There are almost none, and that is the point. Members press a button or send a DM. Staff work inside the ticket with a reply prefix.

Command	What it does
/settings ticketing (id)	Create or edit a ticket system.
/tag (tag)	Send a saved reply in the current ticket, or manage your saved replies.

[required] · (optional)

Questions people ask

Is this ticket bot really free? Yes. There is no paid version, no trial, and no locked features.

Can members open a ticket in their DMs? Yes. That is one of the 2 ticket types.

What happens to a ticket nobody claims? The bot sends a reminder and pings the staff roles for that level.

Are ticket transcripts saved? Yes. The bot builds one from everything it saw and sends it when the ticket is deleted.

Does it need ban or kick permissions? No. It asks for no moderation permissions at all. It asks for 13 permissions, and all of them are for tickets.

Add to Discord