How to Reject a Custom Request Professionally

Reject a custom request professionally by thanking the fan, stating a clear no, and explaining the next step in one brief message. Give a short reason only when useful. If the fan has already paid, use the platform’s decline-and-refund workflow promptly, then confirm in writing that the request was declined and the payment will be refunded.

Last verified: August 2026.

Use one short paragraph unless the situation requires clarification. A direct answer, a brief reason, and a clear payment outcome help the fan understand that the decision is final and what happens next.

When should you reject a custom request?

Not every awkward or incomplete request needs to be declined. Some requests only require a scope conversation, as explained in how to scope a custom creator request.

Reject a request when any of these conditions applies:

• It is outside what you sell. The requested deliverable, format, or skill does not match your listed Creator Services offer.
• It is underpriced for the requested work. The fan wants meaningfully more than your stated price and turnaround cover, and clarifying the scope has not resolved the mismatch.
• 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.
• It is too large for one order. The request involves ongoing work, an open-ended commitment, or a project that cannot be reduced to one bounded deliverable.
• You cannot meet the stated turnaround. Decline when you already know you cannot complete the work within the delivery window you offered.

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 should contain three elements in this order:

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.

Avoid a long, apology-heavy explanation. If your decision is final, the message should not sound like an invitation to negotiate.

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. 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 determine that you should not fulfill it. On FanBell, declining a paid request also refunds it through the documented request workflow (how it works, verified August 2026).

Use these rules to keep the outcome clear:

• Respond as soon as practical. Do not leave a request pending after you have decided not to accept it.
• Stay within your stated response expectation. FanBell Creator Services include a response-time setting alongside price, turnaround time, and revision count (how it works, verified August 2026).
• State the refund explicitly. Write “I’m declining and refunding this request” even when the platform handles the refund through its built-in workflow.
• 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?

• 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.
• 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?

Clear service titles, inclusions, exclusions, prices, and turnaround expectations can 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?

Define the offer before a fan pays:

• 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.
• 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

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. On FanBell, declining a request also refunds it through the platform’s built-in request workflow (how it works, verified August 2026). Your message should still state that you are declining and refunding the request so the fan knows the outcome.

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 does declining and refunding work on FanBell?

FanBell’s Creator Services provide a built-in decline-and-refund control alongside service settings for price, turnaround time, response time, and revision count (how it works, verified August 2026). A creator can therefore close an unsuitable paid request through the platform workflow instead of arranging a separate manual refund.

FanBell is free to start, has no monthly fee, and charges a 12% platform fee only when a fan pays (pricing, verified August 2026).

Get started free and set the terms — including your decline-and-refund policy — before your first request comes in.