When a creator asks you to stop, pause their outreach immediately and record the request in one shared suppression record. Apply it to every list, teammate and sending tool within the request's scope. Check that record again before each send, so an old export or a new campaign cannot restart contact.
An influencer outreach unsubscribe should survive changes in campaign ownership. Deleting a row from one spreadsheet leaves other copies available. The workflow below is an operational recommendation; have a qualified adviser review the applicable jurisdictions, message purposes and retention rules.
Stop the queued messages first
The person who receives the request should pause active sequences and remove scheduled outreach for that creator. Include manual follow-up tasks. Record who did this and when. If your team cannot confirm whether another tool has stopped, hold the affected sends until someone checks.
Don't require a creator to find an unsubscribe link after they have already asked you to stop. In the UK, the ICO says a direct-marketing objection needs no prescribed wording. It can reach any part of the organisation, verbally or in writing.
For US email covered by CAN-SPAM, the FTC requires honoring opt-outs within 10 business days. It also prohibits charging a fee or requiring extra steps beyond a reply email or a visit to a single web page. Use immediate suppression as your team's target. The statutory deadline is no reason to leave a follow-up running.
Stopping one sequence is only part of this work. Modash's sequence announcement describes exit criteria triggered by a reply or relationship-status change. Your team still needs to establish what stops future enrollment, other senders and re-imported contacts.
Record what the request covers
Preserve the creator's wording in a restricted record, or link to the original message. Separate what they said from your team's interpretation.
The ICO distinguishes channel-specific opt-outs from broader direct-marketing objections. Your record should therefore name the channel, purpose and organisation covered. It should also identify the creator separately from an individual email address.
These are illustrative requests and recommended operational responses, not universal legal classifications.
| Illustrative request | Recommended handling |
|---|---|
| "Unsubscribe me from your emails." | Suppress marketing email from the relevant sender across campaigns. Do not invent a campaign-only limit. |
| "Please stop contacting me." | Pause the team's outreach across channels. Record the broad wording and review any uncertainty internally. |
| "This campaign isn't for me." | End that proposal and its follow-ups. Do not record permanent consent or a permanent objection that the message never expressed. |
| "Delete my details and stop emailing." | Stop outreach now and open a separate privacy-request task. Review what minimal suppression record may remain. |
Never treat another visible address or a DM button as a workaround. A channel outside a narrow opt-out still needs its own valid basis for contact. Limit business inquiries to those the creator welcomes and the applicable rules permit. Use the public-contact data review checklist before treating discovered details as usable outreach data.
For agencies, record which represented brand or sender received the request. Escalate wording that may cover the whole agency. Do not silently narrow it to one campaign or assume it authorizes sharing personal data with every client.
Keep a shared suppression record
Use a central record that every outreach owner can check. These are suggested fields, not status names from a particular provider.
| Field | What to record |
|---|---|
| Identity | Internal creator ID and confirmed contact identifiers needed for matching |
| Scope | Sender or brand, channels and marketing purposes covered |
| Request | Received time, receiving channel and restricted evidence reference |
| State | Suppressed, or temporarily held while scope is reviewed |
| Enforcement | Tools, lists and queued messages checked; completion time for each |
| Owner | Person responsible for completing unresolved actions |
| Changes | Reason, evidence and reviewer for any later scope change |
Keep the information needed to prevent repeat contact. Avoid copying the creator's full profile, audience data or entire inbox history into the suppression record. The ICO recommends minimal suppression data so organisations can check new lists without continuing the marketing use the person opposed.
Use confirmed identity links. A creator may have several profiles, while a manager may use one mailbox for several creators. Do not merge everyone who shares an agency address. The contact deduplication guide explains how to keep person, profile and representation records separate. If a shared inbox itself opts out, review that address-level restriction too.
Give senders access to the suppression decision. Restrict the underlying messages and personal details to people who need them. A separate erasure request needs its own owner and decision. Follow the team-export removal workflow to trace copies without losing track of the stop-contact obligation.
Enforce it at import and before sending
Require every incoming list to be checked against suppression before contacts become eligible for outreach. A fresh import must never replace a suppressed state with an ordinary campaign status.
Check again when someone enrolls a creator in a sequence and immediately before a message is released. A list approved yesterday can become stale when a request arrives today. Include teammate mailboxes, agency-operated tools and manual DMs within the recorded scope.
Where tools cannot share updates automatically, assign a named person to reconcile them before the affected campaign runs. Record incomplete updates as unresolved work. A checkbox saying someone was notified does not prove their scheduled messages stopped.
Share suppression information only through an approved compliance process. The FTC restricts transferring opted-out email addresses, with an exception for a company hired to help comply with CAN-SPAM. It also warns that outsourcing email marketing does not remove the marketer's responsibility.
Test the paths that can restart outreach
Use team-owned test contacts in a safe test setup. Do not send test messages to a creator who opted out. The following hypothetical acceptance tests check whether your workflow blocks repeat contact.
| Test | Expected result |
|---|---|
| Re-import an old file containing a suppressed contact | Suppression remains; the contact cannot enter outreach. |
| Have another teammate start a new campaign | The same scope restriction blocks enrollment or sending. |
| Queue a message, then record the opt-out | The queued message is cancelled or blocked before release. |
| Import a confirmed second address for a broadly suppressed creator | Identity matching preserves the broader restriction. |
| Attempt a DM after a broad stop-contact request | The DM task is blocked or held for review. |
| Disconnect a tool from suppression updates | Affected outreach waits until the state can be verified. |
Save the result, responsible owner and any gap for each test. Test again after changing an integration or import process.
Reopening contact needs evidence
Do not expire an opt-out because a campaign ended, a teammate changed or the creator appeared in another list. Under the ICO's guidance, failure to opt out again does not reverse a previous objection. A later specific withdrawal or agreement to marketing can change the position. Record the evidence and approved scope before changing suppression.
Keep necessary existing-relationship administration separate from new pitches. The FTC treats transactional and relationship categories narrowly; an existing partnership alone does not make every email exempt. Have the responsible owner review payment or delivery communications without adding promotional content.
Choose one team-owned test contact now. Suppress it, re-import it from an old list, then ask another teammate to attempt enrollment. Keep the affected outreach paused until both paths respect the recorded restriction.
