How to open a Discord ticket for another member

Before you start

• Use an online Build Discord Bots bot with Tickets enabled in the Discord server you are configuring. Choose a current human member and a staff account for a controlled test; do not use a bot account as the ticket owner.
• Open the bot’s Tickets settings in the dashboard and select the intended server before saving. The setting is per server, so enable it only where your staff has agreed to use this workflow.
• Make sure the bot can create and manage ticket channels in the chosen setup. The staff account must have the configured support role, Manage Channels, Manage Server, Administrator, or be the server owner.

1. Turn on staff ticket opening in the dashboard

   In the dashboard, open your bot, choose Modules, open Tickets settings, and select the correct server. Find Let staff open tickets for members, turn it on, and save the Tickets settings. It starts off, so the command remains unavailable until a manager enables this switch for that server.

   Leave the setting off in servers where staff should use only the member-facing ticket panel. The switch enables one slash-command route; it does not add a DM intake route, automatically claim tickets, or give staff Discord permissions. Keep the support role and channel permissions limited to the people who should handle private requests.

2. Check the Free and Pro ticket limit

   Tickets is a Free module, and staff opening is available when the setting is enabled. On Free, a member can have one open ticket at a time. If the chosen member already has an open ticket, close or resolve it before opening another one for them.

   Pro removes the one-ticket cap and uses the per-member limit saved in Tickets settings. It also has unlimited ticket categories and access to transcripts and priority controls; those separate capabilities are not required to use /ticket open. Do not promise a second open ticket on Free.

3. Open the ticket for the member

   In the configured Discord server, use /ticket open. Set the required user option to the member who should own the ticket. You may add the optional reason, for example /ticket open user:@Sam reason:Follow-up on billing. The command confirms its result privately, so the reason and result are not posted to the channel where the staff member ran it.

   Choose someone who is currently in that server and is not a bot. The bot fetches the current server member rather than accepting a stale mention. It rejects a member who has left the server or a bot account with a private reply instead of creating a ticket.

4. Verify who can see the private ticket

   Open the channel named in the private result. The selected member owns the ticket and can view it. The bot can work in it, the configured support role can help, and the staff member who opened it receives access as well. The opening staff member is recorded separately and does not automatically claim the ticket.

   Test with the selected member and a staff account before relying on the workflow. If your staff model uses a support role, make sure the actual helper has that role. Server administrators can still see private channels through Discord permissions, so use Discord role and administrator access carefully for sensitive support work.

5. Fix the usual staff-opening problems

   Command missing: confirm Tickets is enabled, Let staff open tickets for members is on for the selected server, and the generated bot has been regenerated if it was created before this command existed. Then wait for the bot to be online and try the command again in that server.

   No permission: check the staff account against the configured support role, Manage Channels, Manage Server, Administrator, or server owner access. The switch does not grant any of those permissions. Also check the bot’s ticket setup and channel-management permissions before retrying.

   Member not found or is a bot: select a current non-bot member of the same server. A user who left, a bot account, or an invalid selection is intentionally rejected without creating a ticket.

   Ticket not visible: use the private reply to open the returned channel, then check that the selected member, configured support role, and opening staff account have the expected Discord access. Review the ticket category and the bot’s channel permissions with !ticketcheck if the channel could not be created or staff cannot enter it.