How to Organize Incoming Paid Fan Requests

Organize incoming paid fan requests by giving each one four tracked fields — request type, payment status, deadline, and delivery status — in one list sorted by due date, not arrival time. Separating paid orders from free messages the moment they arrive keeps a fan who already paid from getting lost behind unpaid DMs.

A paid message looks identical to a free one in most inboxes: same platform, same font, same unread badge. The only difference is that one already has money attached to it, and treating a paid order like just another DM is how it sits unanswered for a week. A tracking system doesn't need to be complicated — it needs to make paid work visible, and it needs to hold up even on the day a post takes off and the same four fields suddenly have to sort hundreds of requests instead of a handful — see how to handle a flood of requests after going viral.

What counts as a "paid fan request" you need to track?

A paid fan request is any purchase that obligates you to reply or deliver something: a Paid Private Question, a Creator Service order, or a Personalized Shoutout. Tips and Wishlist or Project Support pledges carry no reply obligation attached to the payment, so they belong in an income log rather than in a work queue you actively triage.

Each offer carries a different obligation, and the media rules differ with it. A Paid Private Question is text-only from the fan, and the creator answers inside a private thread rather than by sending a file (FanBell: Paid Private Questions, "What format are the replies?"). A Creator Service delivery, by contrast, is a written note plus up to 5 files — video, audio, images, PDF, Word, Excel, or PowerPoint, with video or audio up to 20 minutes — and/or a private link for anything larger. A fan ordering a Creator Service can also attach their own files at checkout, such as a track, a resume, or a screenshot. A Brand Collaboration Inquiry is a lead form that collects budget, timeline, and deliverables into a separate brand inbox rather than a purchased deliverable, so a Brand Collaboration Inquiry belongs in that separate inbox and not in the paid-work queue.

Tips and Wishlist pledges still belong in an income log even though they carry no work obligation: for a U.S. creator, a third-party settlement organization is not required to file Form 1099-K unless gross payments to that payee exceed $20,000 and the number of transactions exceeds 200, the threshold restored by the One Big Beautiful Bill Act (IRS: FAQs on the Form 1099-K threshold under the One Big Beautiful Bill). Money a U.S. creator receives below that $20,000 reporting threshold is still taxable income, which is why a tip or a pledge needs a logged row even when no 1099-K ever arrives.

When does the clock start on a paid request?

The clock on a paid request starts when payment and every required detail are both in hand, not when the fan's message appears in your notifications. An order missing a reference file, a recipient name, or a target date is waiting on the fan, and labeling that state keeps a stalled order from counting against your promised turnaround.

Federal guidance for U.S. sellers uses the same starting point: the seller's shipping window begins only after a "properly completed order," meaning payment or charge authorization plus the buyer's required details are both in hand (FTC business guide to the Mail, Internet, or Telephone Order Merchandise Rule). A U.S. seller who made no shipment representation when soliciting the order has 30 days to ship after a properly completed order (FTC business guide to the Mail). The FTC's 30-day window becomes 50 days only in the narrower case where the seller made no shipment representation and the buyer applies to the seller for credit to pay for the merchandise in whole or in part, which is the extra time the rule allows for processing a credit application (eCFR: 16 CFR §435.2(a)(1)(ii)).

The FTC Mail, Internet, or Telephone Order Merchandise Rule was written for shipped merchandise, not custom digital work like a private reply or a recorded shoutout, so neither the 30-day nor the 50-day figure is a legal requirement for a FanBell order. The rule's underlying idea still transfers: if a fan pays for a Creator Service and hasn't sent the file or reference you asked for, the order isn't actually late yet — it is waiting on the fan. On FanBell, a fan pays the full price upfront and their request lands in the creator inbox as a private thread with the details attached, so most requests arrive complete and ready to start (How FanBell works, step 4: "Fans pay for interactions").

What's the simplest system for tracking paid requests?

The simplest working system is one running list in which every paid request occupies a single row with four fields: what was purchased, who paid, the deadline you promised, and its current status. A spreadsheet, notes app, or project board all work; having one place you check first matters far more than which tool you pick.

The habit worth adopting — a recommended workflow rather than a platform rule — is adding a request to the list the moment payment clears, before you have read it closely. The rationale for logging on payment is simple: an order that exists only as an unread notification is invisible to every later triage pass, and a row created in ten seconds survives the week that reading it carefully does not. Note the deadline in your own local time, since a turnaround promised in hours is easy to miscount across a busy week. Creator Services on FanBell are scoped by the creator, who sets the title, price, and delivery time for each service, and the product caps that stated delivery window at 120 hours, so the deadline column should mirror the window you actually offered rather than a vague "soon." Promising a window you can hit is also the federal standard for U.S. sellers: 16 CFR §435.2(a)(1) bars soliciting an order unless the seller has, at the time of solicitation, a reasonable basis to expect it can ship within the time clearly and conspicuously stated in the solicitation, or within 30 days if no time is stated (eCFR: 16 CFR §435.2).

Log the purchase date alongside the deadline, because a dated row stays useful long after delivery. Under U.S. Regulation Z, a cardholder generally must notify the creditor of a billing error no later than 60 days after the creditor transmitted the first periodic statement showing the alleged error (CFPB: Regulation Z §1026.13).

How should you label a request as it moves through your queue?

Label a paid request with one of six statuses — new/paid, needs fan input, in progress, delivered, delayed, or declined and refunded — and update the label whenever the request changes hands. Six labels cover a paid request's whole life cycle and let you filter to "what's overdue" or "what's waiting on me" in seconds.

Six labels is a recommended ceiling rather than a measured optimum: every additional label needs its own rule for when it applies and when it clears, so a ten-status board tends to cost more upkeep than the extra precision returns. The two labels worth defending are "needs fan input" and "delayed." A "needs fan input" label protects you from being blamed for a fan's missing information, and a "delayed" label forces an actual decision — a new date or a refund — instead of a request going quiet.

How long should you keep records of paid fan requests?

Keep a record of what each fan paid for, when they paid, and what you delivered as long as that record could matter on a tax return. In the United States, the baseline is three years from filing the return or two years from paying the tax, whichever is later (IRS: How long should I keep records?).

"Keep records for 3 years if situations (4), (5), and (6) below do not apply to you." — U.S. Internal Revenue Service, "How long should I keep records?"

The same IRS guidance extends the retention period to six years for a taxpayer who did not report income that should have been reported and where that omitted income exceeds 25% of the gross income shown on the return (IRS: How long should I keep records?). Those are U.S. federal periods and general information rather than tax advice; creators outside the United States report under their own country's self-employment rules, so confirm retention rules with a tax professional in your own jurisdiction.

A dated tracker matters most when a payment is disputed, because a dispute can arrive months after delivery and the reply deadline is short. Stripe documents that card networks typically allow cardholders to initiate disputes within 120 days of the original payment, with more time allowed in some situations (Stripe: How disputes work). Stripe tells merchants that the window to respond to a dispute is usually 7 to 21 days, depending on the card network (Stripe: Respond to disputes). Stripe also documents that after evidence is submitted the card issuer usually takes 60 to 75 days to decide the outcome, again depending on the card network (Stripe: How disputes work).

What should you do if you can't meet the turnaround you promised?

Message the fan before the deadline passes and either propose a new delivery date or decline and refund the request. Silence past the promised window is the one option to rule out. Federal guidance for U.S. sellers encodes the same principle: notify the buyer, obtain consent to the delay, or refund automatically if the buyer does not consent.

"If you cannot obtain the customer's consent to the delay... you must, without being asked, promptly refund all the money the customer paid you for the unshipped merchandise." — U.S. Federal Trade Commission, Business Guide to the Mail, Internet, or Telephone Order Merchandise Rule

The same FTC guidance sets the refund speed: a U.S. seller who is also the creditor must credit the buyer's account within one billing cycle, and a seller refunding by cash, check, or money order must send the correct amount within seven working days after the order is cancelled (FTC business guide to the Mail). The FTC refund-timing rule is written for shipped merchandise rather than custom digital work, so it is not a legal requirement on a FanBell order — but going quiet is the outcome to avoid either way, because a late delivery with no explanation is what tends to turn into a dispute. FanBell lets a creator decline a request and refund it rather than deliver something rushed or out of scope. A tracker that flags "delayed" before the deadline passes, not after, is what makes that choice possible.

How do you keep paid requests separate from free DMs?

Keep paid requests and free DMs apart by redirecting free-DM asks to your priced offers and limiting the paid-work tracker to actual purchases. FanBell does not read or charge inside an Instagram or TikTok DM inbox; a creator points followers to a FanBell link, and paid requests arrive in the FanBell creator inbox.

Keeping free DMs and paid orders in separate lists is what makes a tracker manageable, because a paid order stops being distinguishable once it sits in the same feed as the noise. Instagram's own Help Center documents that messages from people you do not follow land in a Message Requests folder and have to be accepted there before they appear in your Chats list — a hidden folder is the last place a request someone paid for should be waiting. A short saved reply, such as "I answer questions like this here: [link]," does the redirecting for you. How to avoid creator DM burnout covers the triage side of the same problem. If you're already turning away more paid requests than you can take, how to manage a waitlist for custom requests covers that next step, and should creators require a deposit upfront covers collecting payment before starting custom work.

Frequently asked questions

No special software is required to track paid fan requests, U.S. creators should keep payment records for at least three years, and a request you cannot finish on time should be renegotiated or refunded before the deadline rather than left silent. The answers below cover each of those points, plus what FanBell charges to take a paid request.

Do I need special software to track paid fan requests?

No. A spreadsheet, notes app, or project board is enough as long as it has four fields — what was purchased, payment status, deadline, and delivery status — and you add every paid request to it as soon as payment clears.

How long should I keep records of what fans paid me?

In the United States, the baseline is three years from the date you filed the return or two years from the date you paid the tax, whichever is later (IRS: How long should I keep records?). Creators outside the United States follow their own country's rules; confirm specifics with a tax professional.

What if I can't finish a paid request in time?

Contact the fan before the deadline and either agree on a new date or decline and refund the order rather than let the request go silent. FanBell supports declining a request and refunding it when the work is out of scope or cannot be completed.

Does FanBell tell me the moment a fan pays?

A paid request lands in the creator inbox as a private thread once the fan pays, so the request can go straight into a tracker instead of being discovered later in a general inbox.

What does it cost to take paid requests on FanBell?

FanBell is free to start with no monthly fee, and a 12% platform fee applies only when a fan actually pays (FanBell pricing). Stripe's payment processing fee is charged separately by Stripe.

What's the difference between organizing requests and running a waitlist?

Organizing is the day-to-day tracking system for requests you've already accepted. A waitlist is a separate mechanic for when you're at capacity and need to queue new requests before accepting them — see how to manage a waitlist for custom requests for that specific setup.

A tracker only has to do one job: make sure a fan who already paid never waits behind one who didn't. Create your free FanBell page and give every paid request a queue built for it from day one.