The outreach owner needs to know whose address this is, where it came from, what the creator welcomes there, and whether this specific message can proceed. Pass that information in a contact handoff card with an owner and a next action. Keep permission review separate from source confidence. An exported address alone cannot answer either question.
Give the next person a decision
A researcher can identify a published business address without knowing whether the team may use it for a proposed campaign. The handoff should preserve that uncertainty.
Modash's article on communication bottlenecks describes problems with missed details, unclear next steps and scattered communication. Apply that lesson at the point where research ends. The outreach owner should receive enough context to accept the contact, return it for research, or stop the proposed message.
Use these fields as a creator contact handoff template. They are workflow recommendations, not platform requirements.
| Field | What to pass |
|---|---|
| Creator identity | Creator name, profile link and internal creator record |
| Recipient role | Creator, manager, agency team or unknown; evidence for that role |
| Contact route | Exact address or approved business form, plus any routing instruction |
| Source and date | Page URL, location on that page, observation date and evidence reference |
| Source confidence | What you confirmed and what remains uncertain |
| Stated purpose | The business inquiries the creator or representative welcomes |
| Proposed use | The named campaign and message the team wants to send |
| Contact restrictions | Opt-outs, prior objections, active conversations and known limits |
| Send review | Approved for the stated use, pending review, or do not send; reviewer and date |
| Next action | One responsible person, one action and its due date |
Keep unknown values explicit. A blank recipient-role field invites someone to assume the mailbox belongs to the creator. Write "recipient role unknown" and name the evidence needed to resolve it.
For the evidence record behind this card, use the guide to recording where each creator email came from. Link that record instead of copying a full research history into every export.
Separate the published purpose from send approval
YouTube's Business Inquiry Emails help page explains that an address is visible only when the channel owner has supplied one. It describes opening the channel's About section and selecting the email-address option. This establishes the source of that contact route. It does not establish the recipient's role, your campaign's suitability, or compliance with the rules that apply to your message.
Keep two fields even when they appear to say the same thing:
- Stated purpose. What the creator or representative says this route is for.
- Send review. Your team's recorded decision about the proposed message, recipient and applicable rules.
For UK electronic-mail marketing, ICO guidance says public contact details do not establish consent. The rules distinguish individual subscribers, including sole traders and ordinary partnerships, from corporate subscribers. Unsolicited marketing to individual subscribers requires consent or an applicable soft opt-in. The details of the recipient and message matter.
Treat that as a reason to record the review, rather than guess legal status from a business-looking address. Where classification or permission is unclear, hold the message for qualified review. The public-contact import checklist helps identify questions to resolve before using the record. This handoff is an operational record, not legal advice.
Three completed hypothetical handoff cards
All names, addresses, dates and evidence records below are fictional. The .example domains illustrate completed fields; they are not live sources or contact targets. These cards demonstrate different decisions without asserting that a real creator welcomes contact.
Card A: published business address, review pending
| Field | Hypothetical entry |
|---|---|
| Creator and recipient | Cedar Bench Studio; creator team mailbox, individual reader unknown |
| Contact route | partnerships@cedarbench.example |
| Source | Creator-owned cedarbench.example/contact, linked from the matching YouTube profile; checked 2026-09-27; evidence C-01 |
| Confidence | Creator-to-site connection confirmed; mailbox reader and delivery status unknown |
| Stated purpose | Paid woodworking-tool partnership inquiries |
| Proposed use | Ask about a paid hand-tool demonstration for the Autumn Workshop campaign |
| Restrictions and history | No previous conversation; no suppression match found on 2026-09-27; recipient's business status unresolved |
| Send review | Pending. Published invitation fits the subject; applicable sending rules remain unreviewed |
| Owner and next action | Outreach owner Maya to obtain the required review before scheduling any email; due 2026-09-28 |
The researcher has finished the identity and source work. The contact still stays out of a send queue. Finding no suppression match records a check; it supplies no positive evidence of permission.
Card B: representative requests a specific proposal
| Field | Hypothetical entry |
|---|---|
| Creator and recipient | Field Notes Kitchen; representative Rowan at Pantry Talent |
| Contact route | rowan@pantrytalent.example, in existing thread T-08 |
| Source | Creator-owned fieldnoteskitchen.example/work names Pantry Talent; representative's reply in T-08 requests this proposal; checked 2026-09-27 |
| Confidence | Published representation and reply agree; future availability remains unknown |
| Stated purpose | Reply with the proposed kitchenware brief, budget and timing |
| Proposed use | Send the requested Autumn Table sponsorship proposal in T-08 |
| Restrictions and history | Keep Rowan as recipient; no separate creator email; restriction check complete on 2026-09-27 |
| Send review | Maya recorded approval on 2026-09-27 for the requested reply only, after the team's applicable-rule review |
| Owner and next action | Maya to reply in T-08 with the agreed proposal by 2026-09-28; no newsletter enrollment |
The scope is one requested reply. A later campaign needs its own review. If representation is unclear in a real record, use the manager-routing guide before choosing a recipient.
Card C: directory address with no source confirmation
| Field | Hypothetical entry |
|---|---|
| Creator and recipient | Little Loom Journal; recipient identity unknown |
| Contact route | Directory candidate hello@littleloom.example; excluded from sending tools |
| Source | Third-party directory export D-14, reviewed 2026-09-27; no supporting creator-owned page found |
| Confidence | Creator-address connection unconfirmed; current use unknown |
| Stated purpose | Unknown |
| Proposed use | Invite the creator to discuss a paid textile campaign |
| Restrictions and history | No existing thread; restrictions check incomplete |
| Send review | Do not send from this record |
| Owner and next action | Researcher Ellis to look for a creator-published business route by 2026-09-29, then return the card or close the research task |
Do not turn the missing source into a guessed address or an unsolicited DM fallback. A fallback belongs in the card only when the creator welcomes that business inquiry there and applicable rules permit it. In the UK, the ICO's electronic-mail guidance includes social-media direct messages within these rules.
Accept the handoff before starting outreach
The outreach owner should open the evidence, check the proposed message against the stated purpose, and review current restrictions. Then record acceptance or return the card with the unresolved question. Preserve the source date and the send-review date separately.
When exporting, keep the decision and its scope beside the address. If the destination accepts only addresses, transfer only records approved for that specific use and retain a link to their cards. Exclude pending and do-not-send records. Recheck restrictions before sending, since an earlier export cannot reflect a later objection.
Take the next address waiting in your research queue and complete its card. Assign the unresolved action before moving it to outreach.
