Skip to main content
Buttons turn the welcome message into a guided ticket flow. The flow must contain at least one top-level option and supports up to five options in each layer.

​
Add and edit options

  1. Select Add option after the greeting.
  2. Enter a required Button label. Use a customer-facing action such as Billing, Bug report, or Partnership.
  3. Optionally add a Unicode emoji or a Discord custom emoji.
  4. Use Move earlier and Move later to control the order shown in Discord.
The last top-level option cannot be deleted. Option IDs stay stable when labels change, so edit the existing option instead of recreating it when you only need new copy.

​
Add a branch

Use the small + on the right side of an option to add a sub-option. A flow can have one sub-option layer: Greeting → option → sub-option. Each sub-menu also supports up to five choices. A parent with sub-options becomes a branch. When a customer selects it, Discord replaces the current choices with its sub-options and prompts them to pick again. The branch does not run its own form, priority, routing, or follow-up message. Configure those settings on each terminal sub-option instead. Removing every sub-option turns the parent back into a terminal option.
Only the person who opened the ticket can select intake options. After a terminal choice is completed, intake cannot be submitted again.
Use Discord preview to click through every branch and confirm that each path ends with the intended action.