Join the MikuBot Discord server for help, updates and feedbackJoin the server

MikuBot documentation

Everything you need to set up and run tickets in your Discord server.

MikuBot gives your server a ticket system. Members click a category on a panel, answer a few questions, and get a private channel with your staff. When the ticket closes, a transcript is saved.

Commands start with *, for example *setup. Most settings can also be changed from the dashboard.

New here? Follow Add the bot, Setup, Categories and The panel in that order and you’ll have tickets working in a few minutes.

Add the bot

You need the Manage Server permission to add a bot to a server.

Add to Discord

The invite already selects every permission the bot needs. Keep them all ticked. See Permissions for what each one does.

Setup

Run *setup in any channel. The bot asks three questions:

  1. Which channel should transcripts be logged in? Mention the channel or send its ID.
  2. Which role can access tickets? Mention the role or send its ID.
  3. Which channel should MikuBot announcements go to? Mention the channel or send its ID, or type skip and the bot picks the channel most members can see.

Type cancel to stop. Each question waits 60 seconds and gives you 3 tries. Setup doesn’t create channels or roles, so you choose everything. Run it again any time to change your answers, or use *setlogs #channel to change only the log channel.

The ticket role can see every ticket and use the Claim and Close buttons.

Categories

A category is a type of ticket, like Purchases or Player Report. Run *categories to open the manager.

Add a category

Delete a category

The panel

The panel is the message members use to open tickets. Run *sendpanel #channel, or just *sendpanel to post in the current channel. You need a finished setup and at least one category.

Tickets

What members do

  1. Click a category on the panel.
  2. Fill in the form if you added questions.
  3. Get a private channel, for example players-support-john, and use the Open ticket button to jump to it.

Each member can have one open ticket per category. If they already have one, the bot links it.

What staff can do

Ticket channels are only visible to the member, the ticket role and the bot. Anyone with Administrator can always see them.

Closing and transcripts

*transcript makes a transcript at any time without closing the ticket.

Transcripts look like a Discord chat and include up to the last 2000 messages, embeds, your server’s name and icon, and images. About 12 MB of images fit in one transcript. Extra images show a “failed” picture, and other file types appear as links that may expire.

Customize

Run *customize, or use the dashboard. Pick what to edit from the dropdown at the bottom: the panel, the default ticket message, or any single category. Then use the buttons:

Placeholders

In ticket messages you can use {user}, {type} (the category name), {open} (open tickets in that category) and {server}. The panel supports {server}.

Categories inherit

Anything you don’t change for a category uses the default ticket message. A category can override the title, description, image and color on its own. The color set on the panel applies to every message the bot sends, while a category’s own color only affects that category’s ticket message.

Every message also shows your server’s name and icon at the top.

Images

You can add an image to the panel, the default ticket message, or any category.

  1. Run *customize and choose what to edit.
  2. Click Image.
  3. Within 60 seconds, upload a picture or paste a link in the same channel.

In the dashboard, choose a file or paste a link and click Upload image.

If an image can’t be loaded, the bot shows a picture saying “Image failed to upload” instead of a broken image. Try a smaller PNG or JPG.

Questions

Each category can ask members questions before their ticket opens.

  1. Run *customize and choose the category.
  2. Click Questions.
  3. Add questions, remove one from the list, or clear them all.

You can add up to 5 questions per category, 45 characters each, and answers can be up to 1000 characters. All questions are required. Answers appear at the top of the ticket and in the transcript. A category with no questions opens a ticket straight away.

Access

Two groups of people can use the bot’s commands.

Admins

The server owner, anyone with Administrator, and anyone with Manage Server can use every command: *setup, *categories, *customize, *setlogs, *allowuser, *denyuser, *allowrole, *denyrole and *resetall, plus the staff commands.

Allowed people and roles

Give your staff access to the staff commands with:

They can use *sendpanel, *tickets, *claim, *addmember, *removemember, *rename, *transcript, *close, *perms, *checkperms and *help. They can’t use the admin commands.

The role you pick in *setup is separate. It lets people see every ticket and use the buttons. For a normal staff team, use *allowrole on that same role. Members who open tickets don’t need any access.

Dashboard

The dashboard lets you manage the bot from a web page.

  1. Pass the quick check that you’re not a bot, then log in with Discord. Discord asks you to allow MikuBot to see your name and the list of servers you’re in.
  2. Pick a server. You see servers where you have Manage Server or Administrator. Servers without the bot show an Add bot button.

Commands

Admin commands

Staff commands

*claim, *addmember, *removemember, *rename, *transcript and *close only work inside a ticket channel. *resetall removes your categories, open tickets, panel and settings for the server, and can’t be undone.

Permissions

The invite link already selects these. Run *checkperms any time to see what’s missing.

Required

Optional

When the bot creates a channel it sets permissions on it, and Discord only lets a bot give permissions it has itself. If one required permission is missing, creating a ticket fails with Missing Permissions. Administrator also works, but isn’t required.

The bot also needs View Channel, Send Messages, Embed Links, Attach Files and Read Message History in the channel you use for the panel and in your log channel.

Troubleshooting

The bot doesn’t answer

Commands start with *. Make sure the bot can see the channel and that you’re the server owner, an admin, or have Manage Server.

It says it’s missing permissions

Run *checkperms. It lists everything the bot lacks, including in the current channel, the log channel and the panel channel. Fix each item and try again. If everything looks fine, a channel or category permission override may be blocking the bot, or its role may be below a role it needs to manage.

A member can’t open a second ticket

Each member can have one open ticket per category. They can open one in another category or close the current one first.

A member didn’t get the transcript by DM

Their DMs are closed. The transcript is still in your log channel.

The panel shows the wrong counts

Send a fresh panel with *sendpanel. The bot needs Send Messages and Read Message History in the panel channel to keep it updated.

An image shows the failed picture

The image may be too large, an unsupported type, or the link couldn’t be downloaded. Try a smaller PNG or JPG, then add it again.

How do I start over?

Run *resetall, then *setup again.

Limits

Enjoying MikuBot?Vote on top.gg