Start with a useful request.
A ticket panel gives members a clear place to ask for help. Categories and opening forms collect the information staff need before the conversation begins, instead of starting with an unexplained ping.
Use the panel description to say what the queue is for. Moderation appeals, community support and technical questions may need different forms or staff teams. Clear scope helps members choose the right route.
Set up the Discord spaces.
When the ticket module is enabled, Sentinel’s automatic setup can create missing support resources and reconcile its configured channels and panel. This requires the relevant Discord permissions; it is not a request for unrestricted Administrator access.
Setup needs Manage Channels. Creating a staff role also needs Manage Roles, or an existing suitable non-administrator staff role must be available. Review the resulting category, channel and staff permissions before inviting members to use the queue.
- Choose the server in the dashboard and open Tickets.
- Enable tickets in the module settings and review the generated resources.
- Configure categories, forms, staff access and the opening panel.
- Test a ticket with a non-staff account before announcing it.
Make ownership visible.
Staff can claim and work through tickets rather than duplicating replies. Ticket states, staff alerts and service-level signals help the team see which conversations need attention.
Keep staff access narrow and confirm that a member cannot see someone else’s ticket. Discord administrators and staff with the relevant access are still privileged; a private ticket is not a promise that no administrator can read it.
Close the loop, keep the right history.
Transcripts preserve the conversation for authorised review. Configure retention, reopening and feedback options to fit the community’s support policy. Avoid asking people to post passwords or other unnecessary sensitive information.
Disabling tickets stops creation and workflows while preserving existing history and channels. It is not the same as deleting past support conversations.