Documentation / Tickets
Let members privately contact staff, and manage the tickets they send.
Send a ticket through the ticketing system to the staff of the server. You will be DM'd and given a time limit to send in your ticket. You may attach up to 1 image or attachment to your ticket.
!send
!send
/sendNo options.
“Wait... you actually trust the mail system to deliver your mail?”
Configure the ticketting system.
Channel: Where a record of new tickets is posted. Everytime a ticket is created this channel will be notified
Category: Where all ticket handling channels will be created. When opening a ticket and assigning it, a channel will created under this category.
Agelimit: How old the account, in days, has to be before being allow to open tickets.
Responsetype: Should the response to users who send in tickets be an embed or text.
Newmailtype: Should notifications of new mail be in an embed or text.
Forcedump: After closing a ticket should the entire channel be archived in a text format, html format, or not at all?
Newmail: The new mail message to be sent. Either in text or discohook link form.
Response: The response message to be sent. Either in text or discohook link form.
NOTE: For new mail and response you may use the following tags to quick replace.
%name: The name of the ticketer
%tag: The mention of the ticketer
%id: The ID of the ticketer
%date: The date the ticket was received
%tid: The new ticket ID
Newmail message may also use %content to copy and paste the content of the ticket
Reponse message may also use %guild to post the server name
To put the senders avatar in either the thumbnail or image use 'https://%user'
!pobox current !pobox channel/category channel !pobox agelimit number !pobox responsetype/newmailtype text/embed !pobox newmail/response text/discohooklink !pobox forcedump off/text/html
!pobox current !pobox channel #channel !pobox category #Category !pobox responsetype/newmailtype text !pobox newmail Ticket Recived !pobox forcedump html
“Ha, and you thought fedex and UPS were bad...”
Assign a staff member to an open or resolved ticket. If a ticket is resolved, you will be asked if you wish to reopen it. If the ticket is not in progress already, I will create a channel to handle the ticket.
!assign member ticketid
!assign StaffMember 12
/assign| Option | Type | Description |
|---|---|---|
staff required | User | Staff member to assign the ticket to |
ticketid required | Number | The ticket id to assign the member to |
“The perks of being in charge, telling other people to help instead.”
Unassign a staff member from a ticket. This will remove their channel override from the ticket channel.
!unassign member ticketid
!unassign StaffMember 12
“The downside of being in charge, realizing everyone else is useless.”
Close an open ticket, marking it as resolved. You may also output the entire log of the channel into either a text or HTML format. If you don't add a ticket ID it will close the ticket associated with the current channel. Note if dumping has been forced you can not choose which output type.
!closeticket [ticket id] [html/text/none]!closeticket !closeticket 12 !closeticket html
“The current record for ticket handling is 12 seconds, needless to say, that was funny.”
Post the status of a ticket to the current channel. This will include the ticket details, content and attachment. You can also get a list of 'pending' tickets that are unassigned and in the 'open' state by adding 'pending'.
!ticketstatus pending
!ticketstatus ticketid!ticketstatus pending !ticketstatus 12
“Status Mr. Scott! Nobody cares captain! Excellent, just as planned!”
Will block a member from sending tickets to the ticket system.
!blockticket member!blockticket Member
“I'm not against this, please, continue.”
Will unblock a member from sending tickets to the ticket system.
!unblockticket member!unblockticket Member
“I'm against this, please, stop.”