Staff workflow
Handle member requests, take over from AI and deal with repeated misuse without exposing tickets to the wider server.
Who can access a ticket
The staff role configured by a server manager determines which support team members should be able to view tickets. Check Discord channel permissions as well. Staff actions should be limited to the relevant private channel.
When a member wants a person
A member can request a person in normal language, such as asking to speak to staff. The ticket assistant can arrange a staff handoff and provide a short case summary, without requiring the member to use a stop command.
Once staff takes over, AI replies should stop so a staff member is not competing with the assistant. If a handoff has already been requested, the bot should avoid sending duplicate alerts.
Review the existing conversation
- Read the member's first question and any later corrections.
- Check screenshots, attachments and the AI replies the member already received.
- Confirm what troubleshooting was attempted and which steps worked.
- Respond directly when a decision or server permission is required.
Ticket conduct warnings
Mang Kanor has a ticket-specific three-warning system for repeated misconduct, targeted harassment and disruptive messages. It is not a server-wide moderation system. The third warning can request human staff assistance.
Warning counts are stored for the individual ticket. Avoid interpreting a member's quotation of abuse they are reporting as if it were necessarily misconduct by that member.
Staff ticket controls
Authorized support staff can request the ticket controls in an open ticket using the existing command below. Staff permissions are required.
mk ticket controlsDo not close a ticket while important information is missing. Confirm the outcome and make sure the transcript is archived before removing the private channel.