Creating Custom Content:
The Request

When a user requests a custom, get as many details as possible. This helps you determine whether you can do it, what price to set, and how long you need to make and deliver it. Remember that “to assume makes an ass out of u and me,” and maybe they’re a tit man 😆

As much as we want to keep collecting those per-message dollars, we also don’t want to ask question after question, one at a time. This behavior is more likely to turn off and annoy the user, potentially pushing them elsewhere. (This can also be seen as a bait-and-switch tactic, as it may start to feel that you have no intention of actually fulfilling the request.) Instead, ask a few questions in one message to allow the user to respond to everything they can in fewer messages. Of course, you may need to ask follow-up questions. You just don’t want to come off as scammy.

For example, if a user asks for a pic of you with your middle finger and booty, you might think that means they want you to flip them off while your behind faces the camera. But they might mean they want your middle finger in that booty. That’s a pretty big difference!

If a user requests something that you aren’t comfortable doing, you do not have to agree to do it. You could suggest an alternative or simply turn down the request. If a user asks for something that violates the Code of Conduct, attempt to redirect them to safe territory. If they continue to push for this content, report them and feel free to block them.