Reviewing

Reviewing

Example review process

1. Check profile

2. Check past applications (if applicable)

3. Check application

4. Review application

The review process starts once a new application appears in intro-logs, the first thing to do is taking a look at the method used. To find out when to verify, deny or limit an application checkout scenarios and explanations for each method

Application methods

Some general things to watch out for on the users profile are their pfp, bio, join dates and linked socials. Another important piece of information is the amount of previous attempts that is visible next to the persons name User #1, at 3 denies it will display an alert

Remember

Ideally no application should be skipped, if you are unsure ask another mod

If a backlog does end up forming, keep it under 2-3 days

Reaction Flags

Reactions can be added to an intro to communicate information about it, ideally also note them in cases it’s something weird/rule breaking

Reaction	Meaning
❓	Noted, this application contains weird content
❗️	Impatient, person opened a ticket to complain/ask about wait time
🅰️	Suspected AI generated content in application (or linked social) or PFP
⬇️	Low quality, the application is fine but lacking in detail (this mainly applies to question method)

User Lookup

Lookup can help find past intros and notes about a user before you review their next attempt, if you want to find a deny reason the best way is to search with their discord id (or mentions:user if you don’t have developer mode enabled), to make it even easier add from:Wypher bot and/or in:log-woa if you want to find the specific deny reason

Lookup Command

Verify

Verifying can be done either via command or button

flowchart LR
	outHigh["Verify"]
	outHigh --- n1["Verify"]
	style outHigh fill:#77DD77,stroke:#77DD77,color:#545454
	style n1 fill:#77DD77,stroke:#77DD77,color:#545454

Verify Command

Deny

Quick Deny

Quick denies are pre-written deny messages that can be used to answer most cases, some of these are method specific. They can be accessed using the dropdown

flowchart LR
	outHigh["Deny"] --- n1@{ shape: "diam", label: "Quick deny reasons" }
	style n1 fill:#FF6961,stroke:#FF6961,color:#FFFFFF
	style outHigh fill:#FF6961,stroke:#FF6961,color:#FFFFFF

Social

• Empty social: Social profile(s) too empty to be verified. Please provide an active social profile. If you don’t have any active social profile(s) please try again with a different verification method.
• Social not found: We couldn’t find your social profile(s) based on the provided details. Please make sure the social(s) submitted are findable.
• Not allowed social: We don’t accept the provided social(s). Please make sure it’s either Instagram, Twitter, Tumblr, Toyhouse, or Bluesky.
• Inappropriate content in social: Your provided social(s) include content that is not allowed in this server.
• No social provided: You haven’t provided a social profile, this can be either a direct link or your username to said social profile. Please provide at least one and make sure it’s either Instagram, Twitter, Tumblr, Toyhouse, or Bluesky.
• Private social: Your provided social(s) couldn’t be verified as they are private, please make sure we can access them.

Question

• Requires more detail: Please be more detailed when answering the questions. Avoid using filler content, don’t artificially inflate the white space, and ensure the questions are sufficiently answered.

General

• Suggest different method: We couldn’t verify you with the method you chose. Please try again with another method that you haven’t used yet.
• General rule violation: Your application/profile violates one or more server rules.

Write Deny

If you can’t find an exact quick deny or want to combine multiple reasons you can write a custom deny reason, when writing the deny reason make sure to stay formal and explain the issue with an understandable level of detail

flowchart LR
	outHigh["Deny"] --- n1["Write Deny"]
	style n1 fill:#FF6961,stroke:#FF6961,color:#FFFFFF
	style outHigh fill:#FF6961,stroke:#FF6961,color:#FFFFFF

Limit

Limiting can be only be done via button, if a user is under 16 or has repeatedly failed to verify due to similar reasons (ALERT shows up) limit them

flowchart LR
	outHigh["Verify"] --- n1["Auctions / Under 16"]
	style outHigh fill:#77DD77,stroke:#77DD77,color:#545454
	style n1 fill:#454FBF,stroke:#454FBF,color:#FFFFFF

Auto Limit

Wypher bot will automatically check the a user submitted age, if it’s 100% confident that a person is under 16 it will automatically limit them

Shadowban

Shadowbans stop people from creating new applications, when they try to start one it will say “This feature is temporarily disabled for you. Please open a ticket if you have further questions.” If a user application violates a high severity rule you can add a shadowban after the deny to ensure they cannot make another application

Using Shadowbanning

Forceticket

Forcetickets are useful for directly confronting a person, if a request in the deny message didn’t work, for example asking them to change an AI PFP or asking for clarification with specific details in someones answers if it’s not enough to ask in a deny message

Using Forceticket

Potential Issues

Button Failure

If the deny or verify button fail to work you can always manually do these using commands instead

Intro Commands

Archive

If a bug occurs that for example posts the same application twice or the user leaves the server, the application can be archived, this means the buttons will be removed to prevent accidental clicks and it will be available in the user lookup

Archive Command