Advertisement
Guest User

Untitled

a guest
Jul 18th, 2018
85
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.81 KB | None | 0 0
  1. How it works
  2.  
  3. The user creates the ticket by doing !ticket
  4. The ticket gets created and sends a message in the channel where the command was done saying,
  5.  
  6. “Your ticket has been created! Please enter your ticket for more information. #ticket-XXXX”
  7.  
  8. The bot sends a message in the ticket saying,
  9.  
  10. “Thank you for choosing Dino Discords! If you would like to talk to a sales representative, please react with :person_with_blond_hair:. If you would like to order a premade discord, please react with :mailbox:. If you would like to talk to a bot developer, please react with :tools:.”
  11.  
  12. If the user reacts for the sales rep, the bot will send two messages. One in the ticket and one in the #request-sales-rep channel.
  13.  
  14. “A sales representative will be with you shortly. Thank you for your patience!”
  15.  
  16. “#ticket-XXXX has requested a sales representative! Please react with :white_check_mark: to accept the request.”
  17.  
  18. If a user reacts for a bot dev, it will send two messages. One in the ticket and one in #request-bot-dev.
  19.  
  20. “A bot developer will be with you shortly. Thank you for your patience!”
  21.  
  22. “#ticket-XXXX has requested a bot developer! Please react with :white_check_mark: to accept the request.
  23.  
  24. If the user reacts for a premade discord, it will send a couple messages. First off it will ask a couple questions.
  25.  
  26. “I will now be asking you a couple questions. What type of community do you run?”
  27.  
  28. “What package would you like? The raptor package includes the premade setup of your choice and two bots. The T. rex setup includes the premade setup of your choice, unlimited bots, and one custom made bot. React with :one: if you want the raptor package or react with :two: if you want the T. rex package.”
  29.  
  30. “Here are the current available discords that match your answers. React with the number you want to buy.
  31.  
  32. List
  33. 1. (Discord link)
  34. 2. (Discord link)
  35. 3. (Discord link)”
  36.  
  37. “Thank you for answering my questions! The following questions I am not able to ask. My boss, Rex, will be with
  38. It will now send a message in #request-ceo saying,
  39.  
  40. “#ticket-XXXX would like to purchase a premade discord. Discord they want to purchase: Discord ID. Please react with :white_check_mark: to accept the request!”
  41.  
  42. Commands
  43. !addlisting (community type) | (Discord link) | (description) | (price) | (ID) - This command will make a channel called (community type)-(ID) under the premade category. In the channel it will say,
  44.  
  45. “Community type: (community type)
  46. Discord link: (discord link)
  47. Description: (description)
  48. Price: (price)
  49.  
  50. If you would like to purchase this discord, please create a ticket.”
  51.  
  52. !dellisting (id) - This command deletes the listing and channel under the premade category.
  53.  
  54. !adduser (user) (#ticket-XXXX) - Adds a user to a ticket.
  55.  
  56. !close ((#ticket-XXXX) Deletes a ticket.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement