Move a creator conversation from DMs to email when both sides want to discuss a specific partnership and the next step needs a brief, several decisions, or another person in the thread. Ask which address to use and what you may send. Then carry over the agreed context in a short summary. Treat that permission as limited to the discussion, with any newsletter or unrelated campaign mailing handled separately.
Choose a reason to move
A channel change should solve a problem the creator recognizes. "Our team uses email" explains your preference, but "I can put the scope and open questions in one message for you and your manager" explains the benefit.
Use this decision table as an editorial recommendation, not a platform rule.
| What is happening in DMs? | Suggested next step |
|---|---|
| The creator asks one question about the offer | Answer it in the existing conversation. |
| The creator asks to see the brief or proposed scope | Offer to send it by email and ask for their preferred address. |
| Fees, dates, deliverables and revisions are getting mixed together | Ask to move those decisions into a single email summary. |
| A manager needs to join | Ask whom to include and whether the creator wants to stay copied. |
| The creator prefers DMs for this discussion | Keep the discussion there or explain which document your process needs by email. |
| The creator has not replied or has declined | Do not treat that as permission to switch channels and restart the pitch. |
Modash's communication-channel guide recommends asking creators about their preferences and using email for details that need a formal record. That supports offering a move. It does not establish that email suits every creator or that switching will produce a reply.
This procedure assumes an existing, welcomed business discussion and applicable rules that permit the messages. A visible DM button or public email address does not establish permission to market. If you are still deciding whether to use an address you found, start with reviewing public contact data before importing it into a CRM.
Ask for the address and the purpose together
Avoid asking for an email address without saying what will arrive. Name the campaign, the material you want to send, and the reason for moving.
Illustrative transition message for a hypothetical partnership:
Thanks for being open to the autumn recipe partnership. May I email the proposed scope and the questions we still need to settle? That would keep the details together for review. Which address should I use, and would you like your manager included?
If the creator already said "email my manager," follow that instruction. Do not ask them to repeat an answered question. Confirm an unclear address or recipient before sending, and keep the creator copied only if they want that.
If the reply is "send it here," send the relevant information in the current channel where practical. You can explain that a later document will need a separate process. Avoid making access to the proposal depend on joining a mailing list.
Record the creator's reply with its date, the address they supplied, and the purpose they agreed to. A note such as "asked for autumn recipe brief by email" tells a colleague more than a broad "opted in" label.
Carry forward decisions without inventing agreement
Before writing the email, split the DM discussion into three categories:
- Confirmed points: things both sides explicitly accepted.
- Proposals: things one side suggested and the other has not accepted.
- Open questions: decisions that still need an answer.
Do not turn "sounds interesting" into an accepted fee, reserved production slot, or permission to reuse content. The email should preserve those differences. This is an operational record, not a substitute for the parties' agreement process.
Use a subject that makes the thread recognizable. For the hypothetical example below, "Autumn recipe partnership: scope for review" is more useful than "Following up" or "Exciting opportunity."
Illustrative conversation-summary email for the same hypothetical partnership:
Hi Sam,
Thanks for asking me to send the details by email after our Instagram conversation. I'm Alex, the partnership contact you spoke with there.
Confirmed so far: you would like to review the autumn recipe idea before deciding whether to take part. You asked us to keep the initial discussion with you.
Proposed scope: a recipe video using the seasonal product. The format, fee, production schedule and any reuse of the content remain open.
Your question: you wanted to know whether you could choose the recipe. Our proposal is that you suggest the recipe for us to discuss.
Next step: please tell me whether this summary matches our conversation and what information you need to consider the scope. Once that is clear, we can discuss your fee and availability.
We will use this thread for this partnership discussion. We have not added you to a newsletter or unrelated campaign mailing.
Thanks, Alex
This example is message-body guidance. Use your real identity and add the sender details and notices required for your actual message and jurisdiction. Do not invent a compliance footer or treat a template as a legal classification.
For your own summary, replace the hypothetical facts with the creator's actual statements. Attach or link the promised brief only after checking that it matches the summary. If your brief adds a deadline or a usage request that never appeared in DMs, label it as a proposal.
Keep mailing permission separate
A creator's request for a brief describes a particular purpose. Do not expand it into permission for weekly product news, every future campaign, or marketing from another brand your agency represents.
The legal rules depend on the jurisdiction and the message. In the UK, the ICO's detailed electronic-mail guidance distinguishes requested messages from unsolicited marketing. It says consent must cover the type of marketing, and silence cannot establish consent. Publicly available contact details do not establish consent either. Different rules apply to individual and corporate subscribers.
In the US, the FTC's CAN-SPAM guidance focuses on the email's primary purpose and covers business-to-business commercial email. An ongoing commercial relationship does not automatically make every message transactional. Calling a thread "partnership admin" cannot settle that question on its own.
As a team policy, keep the campaign conversation separate from broader mailing subscriptions. If you want to offer another subscription, use a separate, clearly described choice through a process permitted by the applicable rules. Do not preselect it because someone requested a brief.
If the creator asks you to stop, record what they asked to stop and act on it. Use the opt-out workflow across creator outreach lists so another teammate does not restart the same outreach.
Finish the handoff inside your team
Give the email thread an owner. Record the original DM location, the agreed email address, the scope of the request, and the next action. Mark the conversation as moved so a colleague does not send another introduction in DMs.
For teams sharing responsibility, prepare the outreach inbox for shared ownership before assigning someone else to reply. They should be able to see what remains undecided without reading an unrelated private conversation.
An unanswered email is not a reason to chase the creator through every available channel. Use a DM reminder only where the creator welcomed that business contact and applicable rules permit it. Keep it tied to the agreed discussion, and respect any stop request.
Before moving your next conversation, write the purpose of the first email in one sentence. Ask permission for that purpose, then draft the summary with confirmed points and open decisions kept separate.
