Use case
Shoutouts for creators
Shoutouts are a natural one-off creator product when scope and safety rules are clear.
Define scope
Creators should define define scope in plain language before taking a request. Fans need to understand what information to include and where the creator's responsibility ends.
FanPing keeps the price, request details, status, and creator decision together instead of scattering them across social messages.
What fans should include
Creators should define what fans should include in plain language before taking a request. Fans need to understand what information to include and where the creator's responsibility ends.
FanPing keeps the price, request details, status, and creator decision together instead of scattering them across social messages.
Pricing
Start with a price that makes the creator's time worth it. If demand is high, raise prices or use waitlists instead of accepting unlimited requests.
Pricing should be creator-controlled because each audience, niche, and request type has different value.
Creator approval
Creators should define creator approval in plain language before taking a request. Fans need to understand what information to include and where the creator's responsibility ends.
FanPing keeps the price, request details, status, and creator decision together instead of scattering them across social messages.
Safety and boundaries
Creators need control before access opens: age gates, request limits, block/report tools, expiry windows, and off-platform payment restrictions.
FanPing keeps payment state, request state, and creator decisions in one place so fans understand what they submitted and creators can protect their time.