Slash Commands, Buttons, and Modals: Better Bot Interactions

Use the smallest interaction that does the job

Use familiar verbs and put required inputs first. Prefer a channel or role picker over asking people to paste an ID. If a command needs several paragraphs of instructions, split it into smaller steps.

Reply before the interaction expires

Discord requires an initial response within three seconds. If work takes longer, defer promptly and then edit the reply. Interaction tokens can be used for follow-ups for 15 minutes. See the interaction response reference.

await interaction.deferReply({ flags: MessageFlags.Ephemeral });

try {
  const result = await createReport();
  await interaction.editReply({ content: result.summary });
} catch {
  await interaction.editReply({
    content: "The report could not be created. Please try again shortly.",
  });
}

This handler fragment assumes MessageFlags is imported from discord.js and that createReport has a timeout. Use private replies for account details or setup errors that only the requester needs to see.

Open a modal as the initial response

1. 1

   The user runs /feedback

   Show a short form with a clear title and only the fields needed to understand the issue.
2. 2

   The user submits the form

   Validate the values and permissions again. If saving takes time, defer this new submission interaction.
3. 3

   Confirm what happened

   Say whether feedback was saved and where any reply will arrive. Preserve useful input if an error requires the user to try again.

Component layouts and supported modal fields evolve. Check the component reference for your chosen layout rather than applying older message-row limits to every component.

Treat every click as a new request

• Check the user, server, and permissions on the server before applying a change.
• Use a short-lived identifier for saved interaction state; do not put secrets in custom IDs.
• Make repeated clicks safe and disable controls once their action is complete.
• Confirm destructive actions with the target and effect spelled out.
• Handle expired controls with a clear way to start again.

A hidden button or a command’s default permissions is not enough to authorize a sensitive operation. Permissions may have changed since the message was sent.

Test the awkward cases

Try the flow on mobile, with a long channel name, with missing permissions, and after the bot restarts. Click twice. Open an old message. Cancel halfway through. These cases reveal more than repeatedly testing the happy path.

Keep the final reply specific: “Reminder saved for Friday at 18:00” is more useful than “Success.” For access checks, see Discord permissions explained.