Support Tickets

The ticket system creates controlled support channels with category-specific staff access, priorities, and participant management.

• Create ticket staff roles and keep them below Airwavy's role where role management is needed.
• Choose a category where Airwavy can manage channels and permission overwrites.

1. Open Support Tickets in the dashboard.
2. Configure ticket categories, staff roles, priorities, and the channel location.
3. Save, publish or use the configured ticket entry point, and open a test ticket.

• Each ticket category can define its name, description, priority, parent category, panel channel, opening message, ticket limit, single-ticket behavior, and staff roles.
• Members open tickets from the published panel; configured staff can claim, unclaim, or close them.
• Use /add and /remove inside a ticket to manage participants without exposing the channel to the whole server.
• Test parent-category inheritance and every staff role with a normal member account before publishing the panel.

• Premium can warn about and close inactive tickets automatically, track first-response targets, and create bounded transcripts.
• Configure transcript retention from 7 through 90 days and keep dashboard transcript access limited to authorized support staff.
• Authorized staff can create and revoke private transcript share links; revoke access when it is no longer needed.
• Transcripts can contain member messages, attachments, embeds, component interactions, and edits, so publish a retention and access policy appropriate to the support data you collect.

• A ticket opens with access limited to the requester, configured staff, and Airwavy.
• Staff can add or remove ticket participants using the ticket commands.

The command reference is continuously checked against Airwavy's active commands. Use the linked entries for current options, cooldowns, and Discord permissions.