Use case
Custom fan requests for creators
Some fan ideas are too specific for a standard menu. A custom request lets the fan propose the work and budget while the creator keeps control of scope, timing, and acceptance.
Fans propose context
A useful custom request explains the desired outcome, relevant links, timing, and budget. 'Review this two-minute song demo' is easier to assess than 'help me with music.'
FanPing puts that context beside the proposed amount so the creator can make one informed decision.
Creators can counter
A creator may like the idea but need a smaller scope, later date, or higher amount. A counter keeps the negotiation explicit without moving payment or private details off-platform.
The fan can review the revised terms before deciding whether to continue.
Pricing
Use a minimum that filters out requests too small to be worth reviewing. Price can then rise with complexity, urgency, or the amount of creator time involved.
Creators set their own minimums in FanPing and can pause custom offers when they are unavailable.
Safety and boundaries
Custom does not mean anything goes. Creators should refuse harassment, impersonation, sexual exploitation, doxxing, deceptive endorsements, and requests that require unsafe contact.
Keep the agreed scope in the FanPing request so both sides can refer to the same terms.
How FanPing fits
FanPing provides the public request link, credit payment, proposal details, counter flow, status history, and creator controls.
The creator gets flexibility without publishing personal contact information or accepting every request.