Accept the refusal and close the current offer. If the creator has welcomed the business conversation, further contact is permitted under applicable rules, and they have not asked you to stop, you may ask one optional feedback question. Record only what they tell you. Liking your brand does not mean they want to negotiate, explain their decision, or receive another pitch.
The practical test is whether you can accept no answer. If your next step would be to chase the feedback or rebut it, skip the question.
Read the decision before writing back
A friendly reply can contain a complete refusal. Read the part about the offer separately from the compliment.
The following messages are illustrative:
| Creator's reply | What you know | Your next action |
|---|---|---|
| "I love the brand, but I'll pass." | This offer is declined; no reason given | Close it; consider optional feedback only if appropriate |
| "I can't meet that deadline." | Timing is a stated obstacle | Close it unless they invite a different date |
| "Could we do one video instead?" | They propose a change | Treat it as an active scope discussion |
| "Please remove me from your outreach." | They want contact to stop | Apply the opt-out; do not ask for feedback |
A reason is information, not an invitation to solve it. A creator can name budget as the problem and still want the conversation to end. If they propose a change themselves, use the separate process for negotiating a partnership by changing the scope.
Remove the declined offer from scheduled follow-ups before replying. Otherwise, a polite closing message can be followed by an automated request to reconsider.
Ask one question, without a second offer
Use this illustrative message only in a creator-welcomed business conversation where that reply is permitted and there is no stop request:
Thanks for letting me know. I'll close this offer. If you're comfortable sharing, what was the main reason this proposal didn't fit? No need to reply, and I won't follow up on the question.
The question leaves the creator free to describe the issue in their own terms. It avoids forcing them to choose between your preferred explanations, such as price or timing.
Do not append a discount, a smaller deliverable, a booking link, or a request for a call. Each adds a new decision after they have already made one. Do not ask why they like the brand if they will not work with it. Affection for a product creates no obligation to accept paid work.
Skip the question when the reason is already clear, the creator sounds frustrated, or the thread has already involved repeated persuasion. A suitable illustrative closing reply is:
Thanks for letting me know. Understood. I'll close this offer and stop the follow-ups about it.
Modash's relationship guide recommends hearing creators' perspectives and keeping team communication consistent. It mainly discusses working partnerships. The one-question limit here is an editorial recommendation for handling a refusal, not a rule established by that article.
Keep feedback separate from permission to contact
A creator who explains their decision has supplied feedback. They have not necessarily invited a revised proposal or agreed to future marketing. A public email address, an available DM button, or the absence of an opt-out does not establish permission.
Keep two separate fields in your records:
- Offer outcome. Declined, counterproposal received, or accepted.
- Contact instruction. Stop requested, a specific future invitation recorded, or no future invitation recorded.
The last value must never trigger automatic re-enrolment. Any later contact still needs its own permitted basis and must respect the creator's stated boundaries.
For US commercial email covered by CAN-SPAM, the FTC's compliance guide says senders must honor opt-outs within 10 business days. It also says business-to-business email has no blanket exemption. As an operational practice, act on a stop request immediately and do not condition it on answering a feedback question. That legal deadline is no reason to continue sending while the team processes the request.
These are limited US email points, not a determination that a particular message is lawful everywhere. If the creator asks to stop, follow the process for handling opt-outs across every outreach list, rather than seeking another route to them.
Record the reason without inventing the motive
Use a small set of reason codes. These are recommended internal categories, not email-provider statuses or claims about the creator's character.
| Reason code | Use only when stated | Do not infer |
|---|---|---|
| Timing | The proposed schedule does not work | They will be available next month |
| Compensation | The payment or payment model does not fit | A higher offer will secure acceptance |
| Work required | The format, volume, or workload does not fit | They are unwilling to work |
| Rights or exclusivity | Requested reuse or restrictions are the obstacle | Their other agreements or partners |
| Product or audience fit | They say the product or brief does not fit | Their private beliefs or personal circumstances |
| Other stated reason | They give a reason outside these categories | A more specific explanation than they supplied |
| Not stated | They provide no reason | The reason most convenient for your report |
Allow more than one code when the creator names several reasons. Do not force a primary reason if they do not identify one. Keep the offer date and a brief factual summary so a future teammate can distinguish an old refusal from a current preference.
The ICO's UK GDPR accuracy guidance says records should make the source and status of personal data clear. It also distinguishes opinions from facts. For this workflow, avoid speculative notes such as "probably fishing for a better rate." The guidance is UK-specific and currently carries an under-review notice following the Data (Use and Access) Act.
Turn a reply into a bounded record
Consider this hypothetical exchange. The creator says they like the product but cannot meet the launch deadline. They do not suggest another date.
| Record field | Entry |
|---|---|
| Offer outcome | Declined |
| Reason code | Timing |
| Evidence summary | Creator said the launch deadline does not work |
| Future invitation | None recorded |
| Current offer follow-up | Stopped |
| Team action | Review lead time for later briefs |
There is enough information to improve planning. There is no need to ask when they are free, why they are busy, or whether another teammate can convince them.
When reviewing several refusals, retain the "Not stated" category. Report stated reasons separately from unanswered feedback requests. A silent creator has not confirmed your theory, and people who choose to answer may differ from those who do not.
Before sending your reply, close the offer, remove its scheduled follow-ups, and check whether the creator already gave the information you need. If they did, thank them and leave the decision closed.
