How to Reject a Custom Request Professionally

Reject a custom request professionally by thanking the fan in one clause, stating a clear no, and naming the next step — usually a refund — in a single short message. If the fan has already paid, decline and refund through the platform's built-in workflow promptly, then confirm in writing that the request was declined and the money returned.

Two things separate a professional decline from an evasive one: speed, and a stated payment outcome. Cameo's Terms of Service give a talent "up to seven days or longer (at our sole discretion) to fulfill or decline your request" (Cameo Terms of Service, legal.cameo.com/termsofservice) — an outer limit, not a target. To prevent bad-fit orders in the first place, see how to scope a custom creator request and how to write a creator service offer.

When should you reject a custom request?

Reject a request when it falls outside your listed offer, is underpriced for the work asked, crosses a personal boundary, is too large for one bounded deliverable, or cannot be finished inside your published turnaround. If the request merely lacks detail, ask one clarifying question first instead of declining it.

Reject a request when any of these conditions applies:

• It is outside what you sell. FanBell's Creator Services page states that each service is defined by the creator — "what's included, the price, the turnaround, and how many revisions (if any) come with it" — and that "if a request is out of scope, you can decline and refund it" (Creator Services, fanbell.link/features/creator-services). FanBell editorial heuristic: if the deliverable is not named in your service description, treat it as out of scope.
• It is underpriced for the requested work. FanBell editorial heuristic, not an evidence-backed industry benchmark: decline or re-scope once the request would take roughly half again as long as the work your listed price and turnaround were built for, and one clarifying exchange has not closed the gap.
• It crosses a personal boundary. You do not have to accept a request that is inappropriate, uncomfortable, or otherwise something you do not want to create; no threshold applies, and one message is enough to close it.
• It is too large for one order. FanBell editorial heuristic, not a platform rule: decline when the request cannot be delivered as a single file or message inside your published turnaround, or when it would need more revisions than the revision count listed on your service.
• You cannot meet the stated turnaround. Decline the moment you know you cannot finish inside the delivery window you published, rather than delivering late.

If a request appears to fit your offer but lacks essential details, ask a clarifying question first. Missing information can often be resolved by confirming the format, length, intended use, deadline, or other scope requirements.

What should a professional decline message include?

A professional decline has three parts in a fixed order: one clause thanking the fan, one sentence declining clearly with a short factual reason, and one sentence naming the payment outcome. Keep it to a single paragraph, and say when the money lands — Stripe's refund documentation states that a customer sees a refund "as a credit approximately 5-10 business days later, depending upon the bank" (Stripe Docs, "Refunds," docs.stripe.com/refunds).

1. Acknowledge the request. Thank the fan in one short clause.
2. Decline clearly. Say that you cannot take the request, adding a brief reason only when it is useful.
3. Explain the next step. Confirm the refund or identify an appropriate existing offer.

Template guidance from FanBell, not a universal professional standard: keep the decline to one short paragraph unless the fan genuinely needs a clarification, and avoid a second paragraph that reopens the price or the scope, because a long, apology-heavy explanation reads as an invitation to renegotiate a decision you have already made.

Template for a request outside your scope:

Thanks for sending this over! This one is outside what I offer through my page—I keep requests to [your actual offer, such as "written feedback on a single draft"]. I'm declining and refunding this one so you're not charged.

Template for a project that is too large for one order:

Appreciate you reaching out. This is bigger than a single request can cover, so I'm going to decline rather than deliver something rushed. If you want to break it into a smaller, specific request, feel free to send a new one.

Template for a request that crosses a boundary:

Thanks for the request. This isn't something I take on, so I'm declining and refunding it now — refunds usually show up on your card within 5-10 business days. You're welcome to choose another service listed on my page.

Template when you cannot meet the turnaround:

Thanks for this! I'm currently backed up and can't deliver within my usual turnaround, so I'd rather decline than keep you waiting past what I promised. I'm refunding this request now.

A reason such as "This is outside what I offer" or "I cannot meet the turnaround" is usually sufficient. When a request crosses a boundary, "This isn't something I take on" is a complete professional response.

When should you decline and refund a paid request?

Decline and refund a paid request as soon as you decide not to fulfil it. FanBell house standard, not a legal or platform requirement: reply within 24 hours of deciding and never later than 48 hours after the request arrives, calibrated against the published platform benchmarks in the table below.

Decline-and-refund timing benchmarks

Use these rules to keep the outcome clear:

• Declining and refunding are one action on FanBell. FanBell's How It Works FAQ answers the question "What if I get a request I don't want to fulfill?" with "You can decline and refund it" (how it works, fanbell.link/how-it-works).
• A refund can reverse the platform fee as well as the payment. FanBell's pricing page states that refunds "may reverse the payment, transfer, and platform fee depending on the transaction status," and that the 12% platform fee applies only when a fan actually pays (pricing, fanbell.link/pricing).
• Reply within 24 hours of deciding. Fiverr measures a freelancer's response rate as how often they replied to new messages within 24 hours, over the last 90 days of activity (Fiverr Help Center, "Understanding Fiverr's freelancer levels," help.fiverr.com/hc/en-us/articles/360010560118) — a reasonable benchmark for a paid custom-request inbox.
• Never leave a decided request sitting past 48 hours. Fiverr's help center tells clients that once a cancellation request is sent, "the freelancer has 48 hours to accept or decline. If the freelancer does not respond, the order is automatically canceled" (Fiverr Help Center, "How cancellations work for clients," help.fiverr.com/hc/en-us/articles/12864193979793).
• Treat seven days as the outer limit. Cameo's Terms of Service give a talent "up to seven days or longer (at our sole discretion) to fulfill or decline your request," and state that "if your CAMEO Video request is canceled or not fulfilled, your payment instrument will be refunded" (Cameo Terms of Service, legal.cameo.com/termsofservice).
• Refund before the fan reaches for a chargeback. Stripe's dispute documentation states that "card networks typically allow cardholders to initiate disputes within 120 days of the original payment" and that "you can't issue a refund outside the dispute process while the dispute is open" (Stripe Docs, "Disputes," docs.stripe.com/disputes).
• Remember the fan has a statutory route if you stall. The U.S. Federal Trade Commission advises cardholders to send a billing-error dispute letter so that it "reaches the issuer within 60 days after the first bill with the error was sent to you," after which the issuer has 90 days to resolve the dispute under the Fair Credit Billing Act (FTC, "Using Credit Cards and Disputing Charges," consumer.ftc.gov/articles/using-credit-cards-and-disputing-charges).
• Borrow the seven-working-day refund clock as an analogy, not as compliance. The FTC's business guide to the Mail, Internet, or Telephone Order Merchandise Rule tells merchandise sellers that where the buyer paid by third-party credit card, "you must refund the correct amount within seven working days after the order is cancelled" (FTC, "A Business Guide to the FTC's Mail, Internet, or Telephone Order Merchandise Rule," ftc.gov/business-guidance/resources/business-guide-ftcs-mail-internet-or-telephone-order-merchandise-rule). That rule covers merchandise orders and does not govern creator services, so treat seven working days as a comparison point rather than a deadline that binds you.
• State the refund explicitly, and say when it lands. Write "I'm declining and refunding this request," then set expectations: Stripe's refund documentation says the customer sees the credit "approximately 5-10 business days later, depending upon the bank" (Stripe Docs, "Refunds," docs.stripe.com/refunds).
• Do not counteroffer after a firm boundary-based refusal. If the request is unacceptable at any price or scope, decline without suggesting that more money would change the decision.
• Mention a smaller alternative only when you genuinely offer it. Describe the available option briefly and ask the fan to submit a new, clearly scoped request.
• Treat a revised request as a new decision. Do not continue working from the declined order; review any newly submitted request against your normal scope, price, and turnaround.
• Separate pre-fulfillment declines from post-delivery concerns. A request you should not accept is different from work you accepted and delivered before the fan raised an issue.

For post-delivery concerns, follow the separate process in handling refunds for creator services.

What should you avoid when rejecting a request?

Avoid silence, guilt-acceptance, over-explanation, and any wording that implies a final decision is still negotiable. The costliest mistake is leaving a paid request undecided: Fiverr auto-cancels an order when a freelancer does not answer a cancellation request within 48 hours (Fiverr Help Center, "How cancellations work for clients," help.fiverr.com/hc/en-us/articles/12864193979793), and an unrefunded fan can still open a card dispute up to 120 days after paying (Stripe Docs, "Disputes," docs.stripe.com/disputes).

• Do not leave the request unanswered after deciding. A clear decision tells the fan whether the work will proceed and what will happen to the payment; Fiverr scores freelancers on how often they reply to new messages within 24 hours over the last 90 days (Fiverr Help Center, "Understanding Fiverr's freelancer levels," help.fiverr.com/hc/en-us/articles/360010560118).
• Do not accept out of guilt. If you cannot or do not want to complete the work, accepting it creates an avoidable risk of missing the agreed scope or turnaround.
• Do not over-explain personal boundaries. You can decline without disclosing private information or defending the boundary.
• Do not blame or criticize the fan. Describe the mismatch in neutral terms, such as "outside my listed scope."
• Do not imply that a final decision is negotiable. Avoid "maybe later" or "perhaps if you pay more" when you are unwilling to reconsider.
• Do not promise an alternative you cannot deliver. Refer the fan to another offer only when it genuinely fits the request.
• Do not confuse declining with resolving delivered work. Once work has been accepted and delivered, assess the concern through the post-delivery refund process instead.

Should you reject, clarify, or discuss a refund?

Clarify when the request is vague but plausibly inside your listed scope; reject and refund when it is outside your offer, oversized, or undeliverable in your turnaround; and open a refund discussion only after you have accepted and delivered the work. The table below maps each situation to wording and a payment outcome.

Clear service titles, inclusions, exclusions, prices, and turnaround expectations prevent mismatched requests before payment. If unsuitable requests keep arriving, improve how you write your service offer rather than making every decline message longer.

How can you reduce the need to decline future requests?

Publish the offer in enough detail that a bad-fit request is obvious before the fan pays: exact deliverable, inclusions and exclusions, price, turnaround, revision count, and required inputs. FanBell's Creator Services page documents exactly these settings — title, description, price, delivery time, and how many revisions are included. Responsiveness is a scored asset on marketplaces: Fiverr lists a 90% response rate among the requirements for Top Rated status (Fiverr Help Center, "Top Rated freelancers," help.fiverr.com/hc/en-us/articles/15140188560913), so a fast, clean decline costs less than a slow one.

• Name the exact deliverable and format.
• State what the service includes and excludes.
• Set a price for the listed scope.
• Publish a turnaround you can consistently meet.
• Specify how many revisions are included — FanBell asks you to "decide how many revisions (if any) are included" when you create a service.
• List any information the fan must provide.
• Explain important content or topic boundaries in neutral language.

These details make it easier to distinguish between a request that needs clarification and one that should be rejected. For additional examples, see services content creators can sell.

Frequently asked questions

Short answers to the four questions creators ask most about declining paid custom requests: whether a reason is required, whether declining triggers the refund, whether to offer a smaller alternative, and whether a discount is ever the right substitute for a clean no.

Do I have to give a reason when I decline?

No. You can decline without a detailed explanation. A short factual reason — such as "outside what I offer" or "I cannot meet the turnaround" — may help prevent another mismatch, but "This isn't something I take on" is sufficient when the request crosses a personal boundary.

Does declining a FanBell request issue a refund?

Yes. FanBell's How It Works FAQ answers "What if I get a request I don't want to fulfill?" with "You can decline and refund it", and FanBell's pricing page notes that refunds may reverse the payment, transfer, and platform fee depending on the transaction status. Your message should still state that you are declining and refunding.

Should I offer a smaller alternative?

Offer a smaller alternative only if it matches a service you genuinely provide. Briefly define the narrower deliverable and invite the fan to submit it as a new request; do not leave the declined order open-ended.

Should I offer a discount instead of declining?

Only when price is the actual issue and you are willing to provide a smaller, clearly defined version of the service. A discount does not resolve a mismatch involving your boundaries, skills, capacity, or delivery window.

How fast should I decline a paid request?

Within 24 hours of deciding is a defensible benchmark, because Fiverr scores a freelancer's response rate on messages answered within 24 hours over the last 90 days (Fiverr Help Center), and Fiverr auto-cancels an order if a freelancer does not accept or decline a cancellation request within 48 hours (Fiverr Help Center, "How cancellations work for clients," help.fiverr.com/hc/en-us/articles/12864193979793).

How does declining and refunding work on FanBell?

FanBell's Creator Services let you set a title, description, price, delivery time, and revision count, and state that "if a request is out of scope, you can decline and refund it". Declining a paid request therefore closes it and returns the fan's money in one step, with no separate manual refund to arrange.

Set your price, turnaround, revision count, and decline-and-refund policy before your first request arrives. Create your free FanBell page.