Understand the Ticket Menu
Understand the choices members see and how each one leads to your support team.
The Ticket Menu helps members choose the right kind of support. A choice can open a ticket or reveal a submenu. You arrange those choices on Ticket Menu in your bot's Modmail dashboard.
What members see
Members who message the bot see your menu message with buttons or a dropdown. A menu group reveals more choices; an action opens a ticket linked to a category. If Ask before opening a ticket is on, members confirm first.
The simplest style, No categories, uses one action and skips the choice between topics. Categories offers a flat list, while Nested Categories adds submenus up to five levels deep. Buttons appear in rows of up to five; long labels can be shortened by Discord, so keep wording concise.
Panels in server channels offer another starting point. Their choices come from your menu when you send them, but already-posted copies keep the choices captured at send time. Read message panels and static panels before changing a menu used by published panels.
How a choice reaches your team
An action links to one category in your library. That category decides where the ticket opens, who can answer, which messages are sent, and where the transcript goes. Menu entries can override the visible name, description, and emoji without changing that destination.
For example, an "Appeal a decision" action can lead to your Appeals category. The member sees the clear action label; the ticket opens for the staff team you've assigned to Appeals.
Keep navigation easy to follow
Use the fewest levels members need to find the right team. Order groups and
actions with the builder's drag handles. They share one order at each level.
The builder marks deeper branches with badges such as Level 4/5 and won't
save a branch beyond the five-level limit.
If Your nested menu was repaired appears, review the moved entries before saving. Entries may have moved up because their parent disappeared, a group looped back into itself, or a branch exceeded the depth limit. Put them where members can find them, then save.
Keep destinations connected
Every action needs a valid category. You can't delete a category while menu entries still use it, and you can't save actions without a valid destination. Removing an entry from the menu leaves its category available in the library.
Next steps
Build your Ticket Menu, or compare categories and the Ticket Menu to find the right place for your next change.
Last updated on