Player Requests are post/listing of sporting events that are in need of an athlete(s) created by a Ringr member. They appear on every member's dashboard, rendering as digital cards. They render inside of our Player Request Module.
See sample Player Request Module below:
Each Player Request Card may contain:
*Notes section will still render on the card even if the member doesn't utilize it. The space below for the content will be blank or with an ellipses.
As a Ringr member, when creating a Player Request, you want to follow our best practices to optimize results . That being said, here are some guidelines and policies when creating a Player Request...
Communicate well
It is imperative that you communicate effectively through your Player Requests. The Player Request's headline is what members will read first and should be used to describe what you are looking for. For this reason, be sure to write language in this field that communicates exactly what you are looking for. See a good and a bad example below:
A Good Example: "Need a Pitcher for our Mens league game"
This is a good example because not only it gives you details on the type of player they need but also they are letting you know that the game is part of an organized league.
A Bad Example: "Need player for our game"
Unless you dont care who will respond to your Player Request, this is a bad example because it is very vague. You might get interested members who may not qualify for what you are looking for.
Avoid giving too much details about the location of the sporting event
To avoid having someone show up uninvited to your sporting event, avoid giving too many details about the location of your event (This is likely done in the notes section). The player request form only asks for a zip code for where your sporting event will take place. This is to simply give the Ringr members an idea of how far they will need to travel. Once you connect with a member and determine that you want this member to attend, this is when you would want to give the exact address.
DO NOT spam the player request feed
DO NOT create a multitude of Player Requests in an effort to spam the Player Request feed. Our algorithm is set up in such a way that no one user will dominate the Player Request feed.
If you are requesting multiple players/athletes, you can use the same Player Request to gather multiple interests.
Members may have up to 30 active Player Requests at any given time. The platform will prevent you from having more than 30 active Player Requests in our system. If you have reached the limit, you may create a new Player Request once one of your active Player Requests expires.
DO NOT be missleading
Be sure to make any information in your Player Request congruent to what you are looking for. Do not set a random Date, Time, and/or Location for the Player Request. Player Requests are actually removed from our database automatically once the current date has passed the Player Request's date.
Give yourself a time buffer
We understand sometimes, in a time crunch, our members might need an athlete to participate in their next sporting event. Our Platform tries its very best to find and connect you with a member who may be interested and willing to participate. Ideally, though, you still want to give yourself the most time possible to allow members to find and respond to your Player Request. This will give you the best chance for success. For example, we recommend teams who are in organized leagues to have great communication with each other and for their players to let their team know in advance if they cannot participate. **This way a player on the team may use our Platform with plenty of time to find a replacement for that game.
**We are not responsible for any violations committed against your league's rules in regards to using a non-rostered player. Be sure using a non-rostered player is within compliance with your league's rules. See Terms of Service for more information about this.
Helping our members find and connect with an athlete for thier next sporting event is what Ringr is all about—however, there are a few types of communities/events that we cannot support on our platform due to safety, legal, or ethical reasons. If Ringr determines that your Player Request event fall into any of the following categories, we may remove the Player Request at our sole discretion.
Ringr does not support events related to any of the following themes...
Violent, dangerous, or criminal behavior
Player Requests must not contain content or promote events that could promote or facilitate illegal or violent activity, such as:
Player Requests must not contain content or promote events that could threaten public or personal safety, including:
Player Requests must not contain content or promote events that incite hate, violence, or harassment against individuals or groups of people based on personal attributes such as race, color, religion, descent, national or ethnic origin, sexual orientation, gender, gender identity, age, disability, or a medical or genetic condition.
Player Requests must not advance conspiracy theories that promote hatred or violence against individuals or groups based on any of the above personal attributes. Conspiracy theories that diminish or deny the documented suffering of a group of people are not permitted.
Player Requests must not contain content or promote events that organize, promote, provide for, distribute services for, or recruit for terrorist organizations.
Targeted to individuals under 18
Ringr members must be at least 18 years old. Player Requests must be only targeted to people over the age of 18.
Harmful misinformation
Player Requests must not contain content or promote events that contain misinformation. This includes medical misinformation such as:
Player Requests must not contain content or promote events that contain financial guarantees, including:
Misrepresentation or concealed intentions
Player Requests must not contain content or promote events that conceal or misrepresent the primary purpose of the Player Request or its events, including:
Sexual exploitation
Player Requests must not contain content or promote events that promote or facilitate sex trafficking, prostitution, or any other type of sexual exploitation.
Pornography, nudity, or sexual content
Player Requests must not contain pornography or publicly shared nude or sexual photos or sexual language.